Maintenance-to-resident-resolution records across Yardi, AppFolio and Outlook: one joined timeline from request to confirmation

Short answer

A property manager connects maintenance-to-resident-resolution records by following one shared key, usually the work order number, from the resident's request through vendor dispatch and invoice to the resident's own confirmation, which often lives only in email. Yardi or AppFolio holds the work order and vendor steps; Outlook often holds the resident's last word. A referral partner can describe how those links are made, and where they fail, without opening a single record.

Visual briefFull-size diagram
A three-lane timeline for one illustrative work order: the request and work order in the property system, the vendor marking the job complete on day 3, a resident email in Outlook on day 5 saying the leak is back, and a reopened job, with a dashed gap where resident acceptance was never recorded.
Illustrative work order. The vendor's 'complete' and the resident's confirmation are two different events, and only one of them was recorded.

The business task behind the chain

The task is simple to state: a resident reports a problem, the company sends someone to fix it, and the resident agrees it is fixed. Each of those three moments is a decision. A coordinator decides how urgent the request is and which vendor to send. The vendor decides when the work is finished. The resident decides whether it actually is.

Most property systems are built around the middle step, because that is where money moves: dispatch, labor, parts and the vendor invoice. The first and last steps are about people, and they are often recorded in looser places, such as a portal message, a phone note or an email thread. That is why a company can have tidy work orders and still be unable to say, for a given job, whether the resident was satisfied.

For an introducer, this matters because the joined history, from report to accepted resolution, is a record of operational judgment at scale. It shows how a company triages, how vendors perform and how often "done" turns out not to be done. A company that can join those steps holds something more useful than a work order list.

Records held in Yardi, AppFolio and Outlook

Think of the three systems as three witnesses to the same leak. Each saw a different moment, and each writes the job down under its own label.

  • Yardi. The portal request is the opening event. Yardi says its RentCafe Resident Portal stays in sync with Voyager for work orders, so a request typed into the portal and the job it becomes should carry one identity from the start. Requests phoned or emailed to the office do not begin with that identity, so the share of portal requests is the first thing to learn.
  • AppFolio. The vendor's actions are the middle events: accepting the job, adding notes and photos, uploading an invoice, marking the work complete. AppFolio states that vendor actions in its portal are recorded, which makes this the most reliable stretch of the timeline. Its In Progress tab shows at most 100 work orders, a screen limit rather than a history limit.
  • Outlook. The resident's verdict is the closing event, and it usually arrives as a reply. Nothing ties a reply to a job unless staff type the job number into the subject. How far back that correspondence reaches depends on retention and export settings; Microsoft notes that classic Outlook in Cached Exchange Mode exports only cached items, by default the past 12 months, when writing a .pst file.

When a landlord runs two platforms side by side, typically after buying a portfolio, the same timeline exists twice in two dialects. That is worth recording as a fact, without ranking the platforms.

Example linkage table: one request, six events

Here is one illustrative request traced as a single joined timeline. The company, unit and vendor are fictional.

DayEventSystem holding itJoin key to the work orderJoin status
0Resident reports a leak under the kitchen sinkResident portal, then work orderWork order numberSupported by the system
1Vendor assigned and accepts the jobWork order and vendor recordWork order numberSupported by the system
3Vendor marks the work complete, uploads an invoiceVendor portalWork order numberSupported by the system
5Resident emails that the leak is backOutlook mailboxUnit number in the email bodyManual join, not guaranteed
6Manager reopens the job and replies to the residentWork order and OutlookWork order number pasted into the replyManual join, depends on staff habit
14Resident replies "all good now"Outlook mailboxThread continuity onlyUnsupported unless the thread is intact

Illustrative. Join status describes how the link would be made, not a tested export.

Read the right-hand column from top to bottom and the pattern is clear: the joins are strong while the work is inside the property system and weaken as soon as the resident speaks by email. The first three rows would survive almost any export. The last three depend on staff habits that vary by office, by coordinator and by year.

What breaks when a vendor marks the work complete without acceptance

The unresolved case is day 3. The vendor marks the job complete, the invoice is uploaded, and in the system the work order looks finished. Nothing records whether the resident agreed. If the resident never writes back, the record reads as a success. If the resident writes back two days later, as in the example, the complaint lands in a mailbox and the job is reopened by hand.

Three things go wrong in the data when this happens:

  1. The outcome is overstated. Reports built from work order status count the job as resolved on day 3, even though the problem was not fixed until day 14.
  2. The reason for reopening is detached. The resident's email explains what failed, but it carries a unit number, not the work order number, so it may never be joined back.
  3. Vendor performance looks better than it was. The first visit and the return visit can appear as one clean job or as two unrelated ones, depending on whether the coordinator reopened the original order or created a new one.

Ask the company one question to test this: "When a vendor closes a job, how do you know the resident agreed?" If the answer is a structured step, such as a follow-up survey or a required sign-off, the chain probably holds. If the answer is "they would tell us," the acceptance step lives in email and the join depends on people.

The gap does not make the records worthless. A company that can show where acceptance was and was not recorded holds a more honest history than one that assumes every closed job was resolved.

Authorized sponsor and introduction

Two different people matter here. The one who decides is an officer able to let the company explore licensing its own history: a chief executive, chief operating officer or general counsel. The one who knows is usually the maintenance director or the coordinator who lives in the work order queue. Introduce the first and mention the second.

Before you do, check the program's company tests: 50+ full-time employees at peak (contractors excluded), documented operating history, the 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. The full list is on who qualifies, and the landlord-versus-manager ownership question is covered in who owns property management records.

Open questions belong to SourceX's review, not to the partner: what owner agreements permit, how tenant details would be removed, which fields an export would really contain, and how many resident emails can be matched to jobs. Partners never ask for or handle raw records. If the company is mid-consolidation, the PMS migration screen explains why finished jobs often stay behind at cutover, and the CMMS migration guide makes the same point for maintenance software elsewhere. Sector fit is covered under referring a property management company, with more system pages on the systems hub. Partners sign the Channel Partner Agreement before submitting an introduction.

Go deeper on maintenance-to-resident-resolution records

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 you know can follow its jobs from request to resident confirmation, even with gaps it can name, 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

Does SourceX connect directly to Yardi or AppFolio?

This page does not claim a connector for any named tool. How records would be exported and prepared is decided during SourceX's review with the company, after an authorized contact agrees to explore a license.

Can a property manager that ran two property systems still qualify?

Running two systems does not rule a company out. What matters is whether the company holds its own records, has the right to license them, meets the size and operating history tests and has an authorized contact.

Should I ask for a sample work order to show SourceX?

No. Partners stay at metadata level: which systems, which years, roughly how many records and who owns them. SourceX handles any record review under its own agreement with the company.

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