Maintenance
Turning service requests into a trackable repair history
A maintenance request should become more than a message thread. It should leave a record the next repair can build on.
How to capture photos, access windows, vendor notes, and cost history without burying work in text messages.
Capture the right details at intake
Good repair history starts before a vendor is called. The tenant should be asked for the affected room, a short description, photos, urgency, and the best access window. That is enough to route the request without a long back-and-forth.
The goal is not to turn tenants into inspectors. It is to collect enough context so the landlord knows whether the issue is a leak, an appliance failure, a habitability concern, or routine upkeep.
Separate status from conversation
Text messages are useful for quick coordination, but they are a poor system of record. A request needs a visible status: received, assigned, scheduled, waiting on parts, completed, or closed.
When status is separate from conversation, everyone can tell what is happening without reading an entire thread. Tenants see progress. Owners see open liability. Vendors know what is expected next.
Keep the repair tied to the unit
The most useful maintenance data is not generic. It belongs to a property, a unit, and often a specific fixture or appliance. If the same dishwasher needs attention three times in a year, the next decision is not another routine call. It may be replacement.
A repair history helps landlords spot patterns: repeat leaks, seasonal HVAC calls, aging appliances, slow vendors, and units where small issues keep returning.