Maintenance-to-resident-resolution metadata packet: a filled sample, field by field

Short answer

A referral partner can describe a property manager's maintenance-to-resident-resolution records with a short packet: which systems hold requests, jobs, contractor steps and tenant replies; which years each covers; rough volumes; who knows how job numbers reach email; whether sign-off is recorded; and what nobody knows yet. Nothing in it requires opening a work order, a vendor invoice or an email, and the company's own operations or IT lead supplies every answer.

Visual briefFull-size diagram
A packet with three columns, System A on Yardi, System B on AppFolio and the shared Outlook mailbox, whose fields fill in row by row (years, record types, volume and sign-off) above a locked vault of work orders, vendor invoices and resident emails that stays closed.
Illustrative packet for a fictional property manager. The vault stays locked; only descriptions leave it.

This template belongs to the maintenance-to-resident-resolution guide, which explains how the chain links. Here the job is the packet itself: a filled sample, what each row means, and how to ask for it.

The filled packet: one column per system

Illustrative: a fictional 540-person housing operator with about 11,000 beds and apartments. System A runs its student communities (Yardi Voyager with the RentCafe portal), System B a 2,200-apartment senior housing book it took over from a third-party manager in 2021 (AppFolio), and the third column is the shared maintenance inbox in Outlook that both teams answer from.

Packet rowSystem A, legacySystem B, acquiredShared mailbox
Portfolio coveredStudent communities, about 8,800 bedsSenior housing, about 2,200 apartmentsBoth books
Years held2015 to now2021 to nowRetention unknown
Record typesTenant requests, jobs, contractor assignments, status changesJobs, contractor acceptances, notes, photos, contractor billsTenant and contractor threads, staff replies
Rough jobs per yearRange stated by the company, peaking at August move-inRange stated by the companyNot applicable; threads not counted
Shared keyJob numberJob numberJob number only when staff paste it
Sign-off recordedNot as a fieldNot as a fieldSometimes, as a reply
Reopened jobsNew number issuedUnknownNot applicable
Closed jobs before migration keptYesUnknown for the previous manager's yearsNot applicable
System ownerProperty systems administratorSenior housing operations directorIT lead

Then three rows that apply to the whole packet:

  • Link owner: the facilities director, who knows whether coordinators type job numbers into inbox subjects and onto contractor bills.
  • Unknown until review: export fields, attachment completeness, how occupant details would be excluded, and what the 2021 takeover contract says about the earlier records.
  • Authorized contact: the CEO, who could approve a licensing discussion.

The sample says "unknown" four times, and that is a strength. SourceX can plan around a marked gap; it cannot plan around a confident guess that turns out wrong.

Row by row: what each field tells SourceX

  • Portfolio covered and years held. These two rows sketch the shape of the history. Two books on two platforms mean the operator holds two variants of one workflow, and a takeover year marks where the second variant begins.
  • Record types. Compare the columns rather than reading each alone. Per AppFolio's help pages, contractors using its vendor portal can take or turn down a job, attach notes, photos and invoices, and flag the work done, with those actions logged; column B may therefore hold more of the contractor's side than column A.
  • Rough jobs per year. A range the operator gives you, with any seasonal peak noted. Never estimate it yourself from bed or apartment counts.
  • Shared key. Yardi describes RentCafe work orders as synchronized with Voyager, so a request submitted through the portal and its job keep one identity in column A. The inbox column is where that identity usually drops away.
  • Sign-off recorded. The most important row; see below.
  • Reopened jobs. When a repeat fault is issued a fresh number, one problem is split across two jobs; the missing-context page walks through exactly that on a single request.
  • Closed jobs before migration kept. In a takeover, finished jobs from the previous manager are easily left in the old system or never handed over.
  • System owner. A job title only. Personal contact details wait until the operator agrees to be introduced.

Questions that turn records into metadata

Ask thisNot thisWhat the answer fills
"Which systems hold maintenance requests, and since when?""Can you send me a work order export?"Years held
"Roughly how many work orders a year, per portfolio?""Can I see the work order report?"Rough volume
"When a resident says a fix did not hold, where does that get written?""Can you forward an example email?"Resident acceptance recorded
"Do staff put the work order number in email subjects?""Can I search the mailbox?"Shared key, mailbox column
"If the same fault comes back, does the job reopen or get a new number?""Show me a reopened job."Reopened jobs
"How long does the maintenance mailbox keep mail?""Can I look at the oldest messages?"Years held, mailbox column

The last question has a technical catch. In Microsoft's instructions for classic Outlook, a .pst export carries mailbox items and their attachments, yet with Cached Exchange Mode on it includes only what is cached locally, a 12-month window unless changed. The honest answer to "how far back" therefore comes from the IT lead, who knows both the retention policy and how any past export was made. The metadata-only Outlook inventory template covers the mailbox side in more detail, and how to prepare a metadata-only inventory gives the general method.

The acceptance row: the field that decides the chain

Three links make the chain: the reported issue, the contractor's work, and the occupant's confirmation. Platforms tend to log the first two. The third is often missing, and the moment that counts most is a contractor closing a job the occupant has not accepted. Capturing that moment is what separates a list of jobs from a history of when repairs genuinely ended.

Pin the acceptance row to one of three answers: a structured field, inbox replies only, or nowhere. "Inbox only, and coordinators usually type the job number in the subject" describes a chain SourceX can evaluate. "Nowhere" describes jobs without outcomes; write it down anyway, because an accurate gap is still useful.

Owner, sponsor and what SourceX reviews

The facilities director or property systems administrator fills in the packet. The sponsor is the CEO, who can let the operator explore licensing its own records. Where the operator manages buildings for others, owner and management agreements may settle who controls the records; read who owns property management records before assuming the manager can license them. A company considering a sale should also see how to sell a property management company.

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. Partners sign the Channel Partner Agreement before submitting introductions; the first valid introduction within the 90-day window is credited when the company submits a verified application. SourceX funds the reward separately, so it never reduces the company's payout, as the rewards page explains. To grade the trail after the packet, use the completeness checklist.

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 the operations lead can fill in every column, unknowns included, and name a sponsor, register as a partner, check the company against who qualifies, and read the program terms before sending the packet with your introduction.

  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

Who should fill in the packet, the partner or the company?

The company's operations or IT lead supplies the answers; the partner writes them down. If a field needs a report run or a record opened to answer, write unknown and name who could find out.

Should resident or vendor counts go in the packet?

Unit counts and rough work order volumes are enough. Resident names, vendor names, addresses and invoice amounts stay out of the packet entirely.

What if the company only runs one property system?

Drop the second column and keep the rest. The mailbox column usually still matters, because resident acceptance often lives in email whichever property system the company uses.

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
  5. refer.sourcex.si/rewards

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