Maintenance-to-resident-resolution completeness scorecard: six checks on work orders, vendor completion and resident acceptance

Short answer

A maintenance-to-resident-resolution trail breaks wherever a later event cannot be tied back to the work order, and the most damaging break is a vendor marking a job complete with no record that the resident accepted the repair. Six checks show whether a property manager's records are complete enough to discuss: work order key, status dates, resident acceptance, reopen links, mailbox span and migration seam. Each is answered at metadata level, from what the company knows about its own systems.

Visual briefFull-size diagram
Six check cards for a repair trail tick in turn, work order key, status dates, resident acceptance, reopen links, mailbox span and migration seam, while a horizontal meter fills to three passes, two partials and one fail.
Illustrative score for a fictional multifamily manager: three passes, two partials, one fail on resident acceptance.

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

CheckWhat it testsHow to ask it at metadata levelPassPartialFail
1. Work order keyThe job number travels with the jobDoes the work order number appear on vendor invoices and in the subject of resident emails?On invoices and in most email subjectsOn invoices onlyEmails refer to "the leak in 4B" and nothing else
2. Status datesEach stage of the job is datedAre opened, assigned, vendor complete and closed each stored with a date, or only the close?All four datedSome stages datedOnly the closed date survives
3. Resident acceptanceThe resident's verdict is its own eventDoes any system record that the resident confirmed the fix, separate from vendor completion?A survey, sign-off or status for acceptanceRecorded in one portfolio or for some job typesVendor completion closes the job
4. Reopen linksRepeat failures stay attached to the first jobWhen a fix fails, is the same order reopened or a new one linked to it?Reopened or linked as a ruleDepends on the coordinatorNew order, no reference to the first
5. Mailbox spanResident replies are retainedHow far back does the shared maintenance mailbox go, and has anyone exported it?Full history kept on the serverFull on the server, but exports hold only recent monthsOlder mail deleted
6. Migration seamHistory survives a system changeAfter any move between Yardi and AppFolio, were closed jobs carried across?Closed jobs migrated or kept readableKept in the old system, not linkedLeft 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:

  1. 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.
  2. 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.

CheckMarkNote from the call
1. Work order keyPassJob number on every invoice; coordinators paste it into replies
2. Status datesPassFour stages dated in both portfolios
3. Resident acceptanceFailVendor completion closes the job; disputes arrive by email
4. Reopen linksPartialYardi buildings reopen; the AppFolio team creates new orders
5. Mailbox spanPartialServer history since 2019; the one export holds a year
6. Migration seamPassNo 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.

  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

Can a property manager fail the acceptance check and still be introduced?

Yes. A fail on acceptance means the structured record cannot say whether a repair held, which is an honest finding to state. State it in the introduction; SourceX decides scope during its own review.

Who should answer the six checks?

The maintenance director or lead coordinator for work orders and vendors, and the IT or office manager for the shared mailbox and any migration. Each answers from admin views and memory, not from resident records.

Does the scorecard need unit counts or work order volumes?

Rough figures help, such as units under management and work orders a year by portfolio, but they belong in the metadata packet. The scorecard only records whether each part of the trail exists, for which years, and who said so.

Sources

  1. appfolio.com/help/vendor-portal
  2. yardi.com/product/rentcafe-living-resident
  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