Maintenance communication for property managers
A tenant reports a leak. The manager speaks with the owner, a contractor asks for access, and the tenant sends another message about the repair. The work has one history, but the conversations often arrive in several places.
Provenience could organize that communication around the maintenance job so a business administrator can find what was reported, discussed, and expected.
Make the maintenance job the project
Start with a bounded repair or turnover job rather than one permanent project for everything that ever happens at an address. Register its participants: the tenant, owner, management staff, and contractors involved. The management business's shared Site contact captures the job's communication; a dedicated job contact is optional.
The planned Phase 1 project shape is uniform. This use case does not require or promise a property-specific workflow engine.
Bring in
- Tenant reports reaching the business's Site call, text, and email contact, or an optional job contact.
- Owner and contractor discussions of scope, estimates, timing, and access arrangements.
- Follow-up communication about whether the reported problem was addressed.
- Photos, quotes, and repair documents as cataloged files. For SMS/MMS, qualifying photos and short PDFs can be considered with their message; they are not a substitute for reviewing a quote or repair document.
A property-management system could supply job status or financial reference rows through a read-only connector, with project identifiers mapped during setup.
Ask
- What did the tenant originally report, and when?
- What timing did the contractor discuss?
- Where did the owner discuss the proposed work or expense?
- What did the tenant say after the repair?
Cited records could support an internal maintenance briefing. They describe what people communicated; a message saying work is complete does not prove a repair was effective or that a formal approval exists.
Why the history matters
In a fictional repair job, the contractor texts that the leak is fixed. The next morning the tenant emails that water is still appearing under the sink. Keeping both statements and their sources makes the follow-up visible without rewriting the earlier completion claim.
At close-out, a business administrator reviews the proposed expectations and outcomes. Provenience does not maintain a live chain or silently resolve contradictory reports during the job.
Build around it
A maintenance-history interface could help a business administrator prepare a handoff or investigate a recurring complaint. History across separate jobs would need an explicit link to the property and customer records; that broader reference-data model is not fully specified yet.
A new tenant is a new participant, not someone automatically entitled to an earlier tenant's conversations. Phase 1 query access is limited to the business's administrators. Tenant and owner portals, staff-scoped access, automated dispatch, rent collection, and write-back into property software are deferred or outside the initial scope.
See the project workflow, read about governed access, or discuss an early pilot.