This page belongs to the maintenance-to-resident-resolution guide. It reads one Illustrative request twice: first as the work order export tells it, then with the vendor record and mailbox beside it.
Before: the request as the work order export tells it
Illustrative: a 310-person property manager with about 6,000 units. Its legacy portfolio runs on Yardi Voyager with the RentCafe resident portal, a 1,400-unit portfolio it acquired still runs on AppFolio, and a shared maintenance mailbox sits in Outlook. None of this describes a real company or a real export format.
A tenant in the legacy portfolio reports a heating fault in January. Exported from the property system alone, the record reads:
| Day | Work order | Status | Category and description |
|---|---|---|---|
| 0 | WO 58812 | Opened, vendor assigned | HVAC: no heat |
| 2 | WO 58812 | Completed, closed | HVAC: no heat |
| 4 | WO 58907 | Opened, vendor assigned | HVAC: no heat |
| 8 | WO 58907 | Completed, closed | HVAC: heater not working |
A reader sees two quick, separate jobs in the same unit, both closed within days. Yardi describes its RentCafe portal as staying in sync with the core system for work orders, so the portal request and the job share an identity. What the export does not say is whether the two jobs are one problem, or whether anyone asked the resident.
After: the same request with the vendor record and the mailbox
| Day | Source | What the connected history adds |
|---|---|---|
| 2 | Vendor notes | First visit: thermostat reset, system running on departure |
| 3 | Outlook mailbox | Resident writes that the heat stopped again overnight; unit number in the body, no work order number |
| 4 | Outlook mailbox | Property manager replies and says a technician is booked; a new work order is opened instead of reopening the first |
| 8 | Vendor notes | Second visit: igniter replaced |
| 9 | Outlook mailbox | Resident replies that the heat has worked since the second visit |
| 9 | Outlook mailbox | Property manager closes the thread with a thank-you |
The story is now one fault, misdiagnosed on the first visit and fixed on the second, with the resident confirming the fix a day after the second work order closed. The vendor's "completed" on day 2 was not the end of the job. The resident's acceptance on day 9 is the only record that it actually ended, and it lives in email.
What is lost, and where that context lives
| Lost context | Where it lives | How it joins the work order | Join strength |
|---|---|---|---|
| What the vendor actually did | Vendor notes and photos, where the vendor portal kept them | Work order number | Strong, recorded by the system |
| That the fault returned | Resident email | Unit number in the body | Weak, manual matching |
| That two work orders are one problem | Staff reply and the second work order | Nothing, unless the first number is cited | Missing |
| Whether the resident accepted the fix | Resident email reply | Thread continuity only | Weak, depends on the thread surviving |
| Who decided it was resolved | Property manager's closing reply | Thread continuity only | Weak |
| How long the resident was really without heat | Combining the first report with the confirmation | Requires all of the above | Derived, not recorded |
The last row is the reason the context matters for AI training and evaluation. A model trained on the before view learns that heating faults close in two days. A model trained on the after view learns when a repair is actually finished, and that a vendor's "complete" is a claim to check, not an outcome. The general point about operating context is covered in maintenance data for AI training.
Two portfolios, two shapes of the before view
The acquired AppFolio portfolio produces a different before view of the same task. AppFolio says its vendor portal lets vendors accept or decline jobs, add notes and photos, upload invoices and mark work complete, and that vendor actions are recorded. So the vendor side there may be richer than in the legacy portfolio, while resident acceptance can still sit outside the work order.
The mailbox has its own limits. Microsoft's documentation says classic Outlook exports mailbox items, with attachments, to a .pst file, and that in Cached Exchange Mode only cached items, by default the past 12 months, are exported. A property manager asked "how far back does the maintenance mailbox go?" should check retention and export settings before answering. For a company still consolidating the two platforms, the PMS acquisition integration screen covers what usually gets left behind at cutover.
Describing the gap in an introduction
The partner describes which systems hold which part of the story. Useful notes: whether resident acceptance is recorded anywhere structured, whether reopened jobs reuse the original work order number, whether staff paste work order numbers into email replies, and how long the maintenance mailbox keeps mail. Never ask to see a work order, a vendor note or a resident email.
The maintenance director or property systems administrator can answer those questions. The CEO authorizes a licensing discussion, often with the COO or general counsel advising, and owner and management agreements may decide who controls the records in the first place; see who owns property management records. The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license the records 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 70% of the data is in English.
How resident personal data would be excluded or de-identified, which export fields exist and whether the mailbox can be tied to work orders at scale stay unknown until SourceX reviews them with the company. To write the systems down in a short form, use the maintenance-to-resident-resolution metadata packet; to grade the trail, use the completeness checklist. The property management industry page covers the sector more broadly.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a property manager can say where resident confirmations live and whether they tie back to work orders, register as a partner, check the company against who qualifies, and read the program terms before you introduce its sponsor.