This system map is part of the maintenance escalation closure guide, which covers what to inventory before a property management transition. Here the job is narrower: for each record, the system that holds it, the field that joins it, and the person who owns it. It is written for property systems consultants who need to describe a client's evidence without handling any of it.
The systems one repeat repair touches
Property management platform. Holds resident requests, units, residents and, at many companies, the work orders themselves. Unit IDs live here, and they can change when communities move to a new platform.
Work order or CMMS tool. Some companies run maintenance in a separate tool with its own status model. Status names are not universal: in Brightly's software, Complete usually means work is done but information is still missing, Closed means everything is documented, and a closed order can be moved back to Complete. Map the status list before reading any history.
Vendor portal. Where contractors accept jobs and mark them done. In AppFolio's Vendor Portal, a Work Done click moves the job to Completed with a status of Under Review, or Needs Invoice if no invoice was added, and completed work orders are removed from the vendor portal. The contractor's own view does not keep the history; the property company's side must.
Accounting. Contractor invoices, approvals and payments. The invoice often carries the clearest description of what was actually done.
Email, chat or a supervisor's log. Where escalation decisions are often written, outside any system of record.
System, record, linking key and owner
| System | Record | Linking key | Usual owner |
|---|---|---|---|
| Property platform | Resident request | Unit ID, request number, date | Community manager |
| Property platform or CMMS | Work order with status history | Work order number, unit ID, asset ID | Maintenance supervisor |
| Property platform or CMMS | Reopen or follow-up order | Parent or related work order reference, or a note citing it | Maintenance supervisor |
| Vendor portal | Contractor job and visit notes | Vendor job number mapped to work order number | Vendor coordinator |
| Accounting | Contractor invoice and approval | Invoice number citing vendor job and work order numbers | Controller |
| Email, chat or log | Escalation decision | Work order number and approver named in the message | Operations director |
| Property platform or CMMS | Completion check | Work order number, inspector, date | Maintenance supervisor |
One fully joined case (Illustrative)
Invented for this page. A fictional 410-person management company runs 44 apartment communities. A resident in unit 3-214 reports no heat three times in one December. The furnace in that unit carries asset tag FUR-3214.
| Step | Record | System | Key that joins it to the next |
|---|---|---|---|
| 1 | Request R-5531: no heat | Property platform | Unit 3-214 |
| 2 | WO-8810: igniter cleaned, heat restored | CMMS | Unit 3-214, asset FUR-3214 |
| 3 | Request R-5602: no heat again, four days later | Property platform | Unit 3-214 |
| 4 | WO-8874: reopen of WO-8810, flame sensor replaced | CMMS | Parent reference WO-8810 |
| 5 | Request R-5690: no heat, third report | Property platform | Unit 3-214 |
| 6 | Escalation email: supervisor asks the operations director to approve an HVAC contractor | Subject cites WO-8874; approval named | |
| 7 | WO-8931 dispatched to HVAC contractor as job HV-2207: cracked heat exchanger, furnace replaced | CMMS and vendor portal | Vendor job HV-2207 |
| 8 | Invoice INV-HV-2207 approved | Accounting | Cites HV-2207 and WO-8931 |
| 9 | Completion check: supervisor visit, resident confirms heat | CMMS | WO-8931 closed after check |
Read down the key column and the case holds together: one unit, one asset, three requests, a reopen with a parent reference, an approved escalation and a verified replacement. A different hard case, a roof leak with four work orders, is told decision by decision in the exception examples.
Where each join tends to break
Unit and asset ID. Breaks when a platform migration renumbers units, or when asset tags were never recorded. Without it, step 3 is a new request, not a repeat.
Parent order reference. Breaks when reopens are recorded only as text such as "see previous ticket", or not at all. Ask whether the reference is a field or a note.
Vendor job to invoice. Breaks when invoices are posted in accounting without the work order number, or when the vendor portal was the only place visit notes lived.
Escalation to approver. Breaks when the decision sits in a mailbox or chat channel that is not retained after a transition. This is the decision record that explains why spend rose, and it is often the first to be lost. The same tier-to-tier pattern in service desks is described on the support escalation process page.
Questions that fill the map
Put these to the operations director or platform administrator. Each asks about a field or a location, never a record.
- Do unit IDs and asset tags survive a platform change, and have units ever been renumbered?
- Are reopens linked by a field, a note, or nothing?
- Are contractor invoices attached to work orders or only posted in accounting, and do they cite the work order number?
- Where are escalations written down, and who signs off contractor spend above a technician's limit?
- Are completion checks recorded as a status, a note or a separate inspection?
- Does a standard export include status history, notes, attachments and links between orders?
Record "unknown" until the administrator confirms each export answer; status history, notes and links are not always included in a standard export. The CMMS migration guide covers what moves when a maintenance system is replaced, and the workflow map template is a general format for this kind of map. When a whole management company is changing hands, how to sell a property management company covers the wider context.
What the map does not settle
The map names systems and owners; it does not decide rights. Many operating records belong to property owners under management agreements, and resident requests name residents and units. Why data rights matter explains why SourceX reviews that first, and the who can license decision tree covers whom to introduce.
The introduced company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English. Partners sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application. Buyer interest, the rights result, the de-identification needed and any offer stay unknown until SourceX reviews the opportunity.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the map shows a client whose repeat repairs still join from request to approved invoice to verified fix, register as a partner, check the company on who qualifies and read the program terms before introducing its operations director.