This scorecard supports the maintenance-to-resident-resolution guide. Run it with the maintenance director before you describe the opportunity to anyone.
Pass, partial or fail: the marking rule
Every check gets one mark. A pass means the record exists, carries a date and covers most of the years the company would discuss. A partial means it exists only for one portfolio, only after a certain year, or only when a particular coordinator was on shift. A fail means it is missing, or nobody in the room can say.
Write down who answered and how they know. "The vendor portal records it" is a product feature; "we have used the vendor portal for every job since 2020" is an answer. Mark the second, not the first.
The finished scorecard is a page of yes, no, years and owners. It never holds resident names, unit numbers, photos or email text.
The six repair-trail checks
| Check | What it tests | How to ask it at metadata level | Pass | Partial | Fail |
|---|---|---|---|---|---|
| 1. Work order key | The job number travels with the job | Does the work order number appear on vendor invoices and in the subject of resident emails? | On invoices and in most email subjects | On invoices only | Emails refer to "the leak in 4B" and nothing else |
| 2. Status dates | Each stage of the job is dated | Are opened, assigned, vendor complete and closed each stored with a date, or only the close? | All four dated | Some stages dated | Only the closed date survives |
| 3. Resident acceptance | The resident's verdict is its own event | Does any system record that the resident confirmed the fix, separate from vendor completion? | A survey, sign-off or status for acceptance | Recorded in one portfolio or for some job types | Vendor completion closes the job |
| 4. Reopen links | Repeat failures stay attached to the first job | When a fix fails, is the same order reopened or a new one linked to it? | Reopened or linked as a rule | Depends on the coordinator | New order, no reference to the first |
| 5. Mailbox span | Resident replies are retained | How far back does the shared maintenance mailbox go, and has anyone exported it? | Full history kept on the server | Full on the server, but exports hold only recent months | Older mail deleted |
| 6. Migration seam | History survives a system change | After any move between Yardi and AppFolio, were closed jobs carried across? | Closed jobs migrated or kept readable | Kept in the old system, not linked | Left behind at cutover |
Two rows rest on documented product behavior. Yardi says its RentCafe resident portal keeps work orders in sync with Voyager, so a portal request and its job start with one identity; phoned-in requests do not, which is why check 1 asks about email subjects. AppFolio states that vendor actions in its vendor portal are recorded, including accepting a job, adding notes and photos and marking work complete. That makes check 2 easy to pass on the vendor side and says nothing about check 3.
Check 3 up close: vendor complete is not resident confirmed
In many setups the vendor's completion is the last structured event a job ever gets. If the resident disagrees, the disagreement arrives by phone or email, and the work order may never change. A record like that teaches anyone reading it, person or model, that "vendor complete" means "resolved," which is the shortcut a good coordinator does not take.
Ask two questions and mark the answers:
- Does any system store resident acceptance as its own event? A follow-up survey tied to the work order, a required sign-off in the resident portal, or a separate status all count.
- If not, where does a disputed completion show up? "In the mailbox, if staff kept the thread" is a partial at best and usually a fail.
A fail here is a finding to state, not a reason to drop the company. The missing-context comparison shows what one job looks like when this event is absent, and the metadata packet has a row for recording it.
Check 5 up close: the twelve-month export trap
A company that says it "has the mailbox" may hold a year of it in an export and the rest only on the server. Microsoft's guidance is that classic Outlook in Cached Exchange Mode exports only the items in the local cache to a .pst file, by default the past 12 months, unless that mode is turned off. Ask whether past exports were made that way. If the server copy is intact, the history still exists; if someone deleted server mail after exporting, it does not.
A filled scorecard (Illustrative)
A fictional 260-person multifamily manager: most buildings on Yardi Voyager with RentCafe, one acquired portfolio still on AppFolio, and a shared maintenance mailbox in Outlook. Answered by the maintenance director and the IT manager in one call.
| Check | Mark | Note from the call |
|---|---|---|
| 1. Work order key | Pass | Job number on every invoice; coordinators paste it into replies |
| 2. Status dates | Pass | Four stages dated in both portfolios |
| 3. Resident acceptance | Fail | Vendor completion closes the job; disputes arrive by email |
| 4. Reopen links | Partial | Yardi buildings reopen; the AppFolio team creates new orders |
| 5. Mailbox span | Partial | Server history since 2019; the one export holds a year |
| 6. Migration seam | Pass | No migration yet; both systems still readable; integration planned for next year |
Three passes, two partials and one fail. That describes the trail accurately: strong operational records, a known gap where the resident's verdict should be, and a reopen habit that differs by portfolio. The planned integration is a real date to mention, because closed jobs are often left behind at cutover; the property management acquisition integration guide explains why.
Who answers, who decides, and what stays unknown
The maintenance director can answer every check. The person who can authorize a licensing discussion is the CEO, often with the COO or general counsel advising. Owner agreements matter too, because a fee manager may not own every record it holds; ask, and leave the answer to counsel.
Check the company tests before you introduce: 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 70% of the data is in English.
Unknown until SourceX reviews it: what owner agreements allow, how resident details would be removed, which fields an export really contains, and what share of resident emails can be matched to jobs. Partners never ask for or handle raw records. SourceX funds any reward separately and never deducts it from the company's payout; see rewards. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, and partners sign the Channel Partner Agreement first. If the owner is weighing a sale instead, selling a property management company covers that path; maintenance data for AI training and the systems hub give wider context.
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 scorecard shows a repair trail you can describe honestly, including the acceptance gap, register as a partner, confirm the company against who qualifies and read the terms before you introduce its sponsor.