Who controls the historical work orders after the transition?
The short answer is that it depends on the contract, and few people check until the old login stops working. A property systems consultant is often the only person in the room who knows where the maintenance history physically lives, which is why this moment is worth one deliberate question: who controls the historical work orders after the transition?
Three parties have a claim on some part of the record:
- The outgoing management company usually runs the maintenance system (a CMMS or the work order module of its property software) under its own license, with its own triage rules, vendor panel and closure standards. Its process knowledge across many buildings is its own operating history.
- The property owner typically has rights to the property's books and records under the management agreement. The IREM Code of Professional Ethics, for example, expects members to keep accurate, auditable records and make them available to the client for inspection, and its duties continue toward former clients when a relationship ends.
- The incoming manager inherits open work orders and asset lists but rarely the closed history, because its own system has a different data model.
That split is the opportunity and the limit at the same time. Licensing needs one company that owns the records it would license and an authorized person who can sign for it. The property management licensing fit page explains which property records tend to qualify, and who owns property management records covers ownership in general; this guide is about the narrow window when control is moving.
Why verified maintenance closure evidence is easy to overlook
Transition checklists focus on what keeps buildings running on day one: open tickets, vendor contracts, keys, warranties, tenant contacts. Closed work orders feel like history, so they get exported as a flat report or left behind.
The valuable part is not the ticket itself but the closure evidence linked to it: who verified the repair, whether a follow-up inspection confirmed it, whether the same asset failed again within weeks, and what the vendor invoice said compared with the work performed. Modern systems store that sequence as timestamped fields. AppFolio's partner API documentation, for instance, lists work order fields such as status and a CompletedOn timestamp recording when a work order changed to completed. A flat export often keeps the dates and loses the links between request, dispatch, invoice and verification.
The evidence asset: one work order's record chain across a transition
Illustrative. A 140-person commercial property manager is handing a 22-building office portfolio to a new manager. Its maintenance system holds nine years of work orders. Here is what a single chiller complaint produced, and who controls each piece after the handover date.
| Step | Record created | Where it lives | Controller after handover | Survives a flat export? |
|---|---|---|---|---|
| Tenant request | Request text, priority, timestamp | Outgoing manager's maintenance system | Depends on the records clause | Usually yes, as text |
| Triage | Category, assigned technician, response target | Outgoing manager's system | Outgoing manager's process data | Often partly |
| Vendor dispatch | Vendor, scope, not-to-exceed amount | System plus vendor portal | Split between manager and owner | Often loses the scope |
| Vendor invoice | Line items, labor hours, parts | Accounting module | Owner's property books | Yes, but unlinked |
| Closure verification | Inspector sign-off, photos, tenant confirmation | Maintenance system attachments | Depends on the records clause | Often no |
| Repeat-failure check | Same asset reopened within 30 days | Derived from asset history | Outgoing manager's process data | No, unless asset IDs carry over |
Read across the last two columns. The rows that carry the most weight in a licensing review, verification and repeat failure, are the ones a transition most often breaks. That is the metadata conversation you are trying to start, without touching a single record yourself.
Which four metadata questions settle who controls the history?
Once the owner has answered the opening question, four follow-ups tell you whether there is anything to introduce. Each one stays at metadata level: what exists, how much, in which system, and who decides. None of them asks to see a work order.
- Which clause decides control? Most management agreements have a books-and-records or termination clause. Ask whether anyone on the controlling side has read it for system data, not just for the property's financial books. "We assume it's ours" is a different answer from "clause 14 gives us our process records."
- Which system holds the closed history, and for how long after handover? Note the system name, whether the license is the manager's or the owner's, and whether a read-only copy will remain. A retention intention is weaker than a written retention policy.
- Are verification records linked to each work order? Sign-offs, inspection photos and tenant confirmations are the closure evidence. If they sit in a shared drive with no work order ID, the chain in the table above is already broken.
- Who can authorize a licensing discussion today? For a management company it is the CEO, often the owner; for a property owner, its CEO, with the asset management lead or general counsel preparing the case. Ask whether that authority changes on the handover date.
If the answers point to the outgoing manager's own portfolio-wide process history, that company is the likely candidate. If they point only to one property's books, the property owner is, and it must meet the eligibility rules on its own.
Does the company qualify, and what stays unknown until SourceX reviews it?
Before you introduce anyone, check the basics on who qualifies. The introduced company needs 50+ full-time employees at peak (contractors excluded), a 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 90% of the data is in English.
What you can reasonably know at metadata level:
- which company controls the work order history and under which clause;
- the system name, approximate record count and years covered;
- whether closure evidence is linked to each work order;
- who can authorize a licensing discussion.
What stays unknown until SourceX reviews it: whether there is dataset demand for these records, the outcome of the rights review (including any owner or tenant restrictions), the scope of de-identification, any offer to the company, and therefore any reward.
Reward disclosure and owner permission
Sign the Channel Partner Agreement before you submit, and introduce only with the decision-maker's agreement. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. The default reward is 25% of the Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Illustrative arithmetic only: if the controlling company were paid $250,000 for a qualifying completed handoff, the reward would be $62,500. 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. The rewards page explains each payment status, and the network opportunity finder helps you spot other clients facing a similar event. More partner playbooks sit under /for, including the real estate operations overview.
A short introduction is enough: name the documented handover date, the system and the approximate span of closed work orders the owner described, say that SourceX licenses approved operating records directly from companies, and disclose that you may receive a referral reward that SourceX pays separately. Send it only to the decision-maker who agreed to it.
Go deeper on management contract transitions
- Management contract transition introduction email: a ready-to-adapt email to the controlling company's decision-maker, with the reward disclosure built in.
- Management contract transition meeting agenda: a timed agenda for the first owner conversation about work order history.
- Management contract transition archive context checklist: a checklist of the retention, export and authority facts to confirm before access ends.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the controlling company has a documented handover date and an owner who wants to talk, register as a partner, confirm the fit on who qualifies, and keep the program terms on hand when you send the introduction.