The technical side of most maintenance problems is simple: a leak is a leak. The hard part is everything around it: who heard about it first, whether anyone wrote it down, who was free, what the technician found, and whether anyone will remember it in six months.
The disconnected version
A tenant messages the property manager, who calls the supervisor, who calls a technician. The technician fixes it and moves on. If anyone asks, the manager says it was handled. Nothing is attached to the unit, the asset or the lease.
Six months later the same unit leaks again. Nobody can say whether it is the same fault, the same part or the same contractor.
The connected version
- The tenant reports the issue through the portal or by email. It becomes a request linked to Unit 1204 and the AC asset in that unit.
- The request is classified with a priority and a trade. A supervisor confirms the suggestion or changes it.
- A technician is assigned based on skills and availability. The tenant sees the appointment.
- The technician records what was found and what was done, with photos, from a phone.
- The work order closes, a new entry appears in the asset's history, and the lease record shows the request and its outcome.
What changes
- The question 'what is happening with my request?' has an answer the tenant can see.
- The second leak is diagnosed with the first one in view.
- Monthly reporting becomes a filter on records that already exist, so nobody has to reconstruct the month.
- The property manager stops being the messenger between tenant and technician.
Unit 1204 and the timings in this example are illustrative and are not drawn from a customer system.
Related reading: