A maintenance ticket identifies a request. A repair-history collection can show dispatch, contractor visits, follow-up, completion and cost. The key is keeping the work-order identity separate from the property or unit identity. A property may have many unrelated repairs, including several open at the same time.
One repair, several related records
Fictional request R-63 concerns a leak at property P-8, unit U-3. Work order W-92 is assigned to a contractor, visit V-14 records an attempted repair and follow-up V-15 confirms completion. Bill B-40 refers to W-92. A property-level folder does not by itself establish all those links.
Record the request and work order separately if the system gives them different IDs. That makes it easier to explain a request split across contractors or several requests combined into one visit.
| Record | Own identity | Relationship to inspect |
|---|---|---|
| Request | R-63 | P-8/U-3 and work-order reference |
| Work order | W-92 | R-63 and assigned contractor |
| Visit | V-14/V-15 | W-92 and visit date |
| Completion | Completion note | W-92 and result |
| Cost | Bill B-40 | W-92 or supporting reference |
Separate recurring problems from duplicate tickets
Two requests about a leak may describe duplicate reports, a reopened issue or a new incident. Do not merge them on address alone. Look for explicit related-request, reopening or work-order references and preserve separate event dates.
A contractor bill may cover several units or work orders. Keep the bill identity and inspect any allocation or line reference before attaching the full amount to one repair. This prevents the inventory from implying a cost relationship that the records do not establish.
Treat completion evidence as its own group
A closed status, contractor note, inspection and resident confirmation can describe different aspects of completion. Inventory whichever are actually present. If photos exist, record whether they are tied to a work order or merely stored in a property folder. Their presence does not prove that every repair has visual evidence.
Check the repair timeline
Choose a repair with a follow-up visit. Trace request time, dispatch, visit, completion and billing. If the available activity history begins later than the request table, describe the shared period separately.
- Request and work-order IDs
- Property and unit identifiers kept distinct
- Contractor assignment and visit records
- Recorded reason for reopening or follow-up
- Completion note or inspection reference
- Bill allocation and attachment availability
Distinguish reporting from responsibility
The resident who reports an issue, the person who authorizes work and the contractor who performs it occupy different roles in the record. Keep those relationships as documented. A contact appearing on a ticket should not automatically be labelled the approver or the person responsible for completion.
Ask about the collection, not just the sector
The provider matrix separates property-industry mentions from specifically named records. Ask whether a linked maintenance collection is relevant instead of treating a real-estate heading as an exact work-order match. The AppFolio guide can help you separate the system’s documented features from the records in your account.
Questions about this comparison
Can address alone connect all repair records?
It gives property context but may identify many repairs. A request or work-order reference is more specific.
Is a contractor bill proof that the repair was completed?
It is a billing record. Completion needs its own recorded evidence.
Should resident messages be a separate group?
Yes when they are part of the proposed collection. Record their relationship to the request and their observed history.