Building Maintenance Company System

Every request enters as a card in “Request”, from the client or from the preventive maintenance schedule, documenting the location, description, and priority. The requests coordinator assigns the right technician and the card moves to “Diagnosis”, where the technician inspects the fault and determines the parts and the estimated cost, then “Repair” after the client's approval if the repair falls outside the contract, then “Client Confirmation” for the client to verify the fault is gone and comment on the card, and finally “Close & Invoice” by issuing the invoice or deducting the visit from the periodic contract.

Chat coordinates the technicians' movement: the coordinator passes an address or asks a technician about a part in their van, and the technician uploads before-and-after photos from the site. Announcements carries the preventive maintenance schedule to clients: upcoming periodic visit dates for each facility, published in advance so clients can prepare their sites, plus any official circular about contract price changes or working hours in seasons and holidays.

Dues records technicians' pay and spare parts for each request, so the company knows the profit of every maintenance contract individually — a contract that drains parts and visits gets repriced at renewal on documented numbers. The requests coordinator watches the “Request” and “Diagnosis” cards hourly because response time is the satisfaction benchmark in the contracts, and any emergency request jumps the queue with a clear priority flag everyone can see.