Before and after: what a standalone work order export loses about whether a repair held

Short answer

A single-system maintenance export usually loses the resident's side of the story. A work order export from the property system shows that a request was opened, assigned to a vendor and marked completed. It can lose whether the resident agreed the problem was fixed, whether the same fault came back under a new work order number, and who finally decided the job was resolved. Those facts often sit in vendor notes and in a shared Outlook mailbox, joined to the work order only when staff paste its number into a reply.

Visual briefFull-size diagram
A work order ticket whose lower half is blank, with context pieces sliding up from below to fill it: the resident's day 3 email, the second visit under a new work order number, and the resident's day 9 confirmation.
Illustrative work order. The export says completed on day 2; the mailbox shows the resident confirming the fix on day 9.

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:

DayWork orderStatusCategory and description
0WO 58812Opened, vendor assignedHVAC: no heat
2WO 58812Completed, closedHVAC: no heat
4WO 58907Opened, vendor assignedHVAC: no heat
8WO 58907Completed, closedHVAC: 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

DaySourceWhat the connected history adds
2Vendor notesFirst visit: thermostat reset, system running on departure
3Outlook mailboxResident writes that the heat stopped again overnight; unit number in the body, no work order number
4Outlook mailboxProperty manager replies and says a technician is booked; a new work order is opened instead of reopening the first
8Vendor notesSecond visit: igniter replaced
9Outlook mailboxResident replies that the heat has worked since the second visit
9Outlook mailboxProperty 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 contextWhere it livesHow it joins the work orderJoin strength
What the vendor actually didVendor notes and photos, where the vendor portal kept themWork order numberStrong, recorded by the system
That the fault returnedResident emailUnit number in the bodyWeak, manual matching
That two work orders are one problemStaff reply and the second work orderNothing, unless the first number is citedMissing
Whether the resident accepted the fixResident email replyThread continuity onlyWeak, depends on the thread surviving
Who decided it was resolvedProperty manager's closing replyThread continuity onlyWeak
How long the resident was really without heatCombining the first report with the confirmationRequires all of the aboveDerived, 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is a work order export without resident confirmation still useful?

It shows the operational side, which is real: what was reported, who was sent and when the job was marked done. Describe it as that, and say plainly that whether the fix held is not in it.

Can a partner ask the property manager to forward a resident email as an example?

No. Resident emails contain personal data, and partners stay at metadata level. Ask whether staff paste work order numbers into replies and how long the mailbox keeps mail; that answers the question without any content.

Does the same gap appear in the AppFolio portfolio?

Usually, in a different shape. AppFolio's vendor portal records vendor notes, photos and completion, so the vendor side may be richer, but resident acceptance can still sit in email rather than in the work order.

Sources

  1. yardi.com/product/rentcafe-living-resident
  2. appfolio.com/help/vendor-portal
  3. support.microsoft.com/en-us/outlook/export-emails-contacts-and-cal…
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment