# Maintenance history before a PM transition | SourceX

Canonical: https://refer.sourcex.si/guides/workflow-maintenance-escalation-closure
Last updated: 2026-10-19

Before a property management transition, inventory the records that show whether a maintenance job was actually fixed: resident reports, work orders with their full status history, contractor visit notes and invoices, escalations, and the completion checks that verified the repair. Note the years covered, the system holding each record, who controls it under the management agreements and the date access ends. A property systems consultant gathers only that metadata and introduces the operations director, plus whoever can authorize a licensing discussion.

## Three kinds of transition, three different deadlines

"Transition" covers several events, and each ends access in a different way. Name the event first, because it decides which date matters.

| Transition | What usually ends | Where the date comes from |
|---|---|---|
| Management contract moves to another firm | The outgoing firm's access to owner-controlled records | The management agreement's termination and records clauses |
| Portfolio or property sale | The seller's operating platform for the sold properties | The purchase agreement and the transition services plan |
| Platform change within the same company | Logins to the old property platform and its vendor portal | The software contract and the vendor's read-only terms |

A company can face all three in one year. The consultant's job is to get each date in writing, not to estimate it. The [management contract transition guide](/guides/moment-management-contract-transition-property-systems-consultants) covers the first case in more depth, and the [CMMS migration guide](/guides/cmms-migration) the third.

## Why a closed status is not the history

A work order's final status says little about whether the problem was solved. Systems define "complete" and "closed" differently. Brightly's documentation, for example, says Complete usually means the work has been done but information still needs to be added, while Closed is used once everything on the order is documented, and a closed order can be moved back to Complete. In AppFolio's Vendor Portal, marking a job Work Done moves it to Completed and sets a status of Under Review or Needs Invoice, and completed work orders are removed from the vendor portal.

What tells the real story is the sequence: the resident's first report, each visit, each reopen, the escalation, and the check that confirmed the repair held. A job closed before its root cause was fixed shows up only as a chain of linked orders, which is exactly what a flat export at transition tends to break. For regulated housing, the stakes are higher: HUD's NSPIRE terms require proof of mitigation within 24 hours for life-threatening deficiencies in public and multifamily housing, so completion evidence is itself a compliance record.

## Inventory checklist for the operations director

Every answer is metadata, never the records themselves.

- **Resident reports.** Which channels (portal, phone, email, text) and since when? Are they stored with the work order or separately?
- **Work order history.** How many years? Does the system keep every status change with a timestamp, or only the current status?
- **Reopen links.** When a job comes back, is a new order linked to the old one, or opened fresh with no reference?
- **Contractor records.** Visit notes, photos, quotes and invoices: attached to the order, in a vendor portal, or in accounting?
- **Escalations.** Is there a written escalation rule, and where is each escalation recorded? The [support escalation process page](/data-types/support-escalation-process) shows the same pattern in service desks.
- **Completion checks.** Are inspections after repair, resident confirmations or follow-up calls recorded, and where?
- **Volumes.** Roughly how many work orders a month, and what share are reopened? Estimates are fine; mark them unverified.
- **Deadline.** The date the current platform login, vendor portal access or management contract ends, in writing.

## Who controls which records

Control decides who can authorize anything later. Under typical management agreements, many operating records belong to the property owners, while the management company's own process records (escalation rules, contractor scorecards, internal reviews) are more often its own. The [record ownership explainer](/questions/who-owns-property-management-records) covers the usual split, and [why data rights matter](/proof/why-data-rights-matter) explains what SourceX checks.

Do not recommend copying or keeping records the company has no authority or policy basis to retain. That decision belongs to its leadership, counsel and IT. If the company is winding down an office or region, the [office closure checklist](/resources/office-closure-checklist) gives a broader list.

## Does the company qualify?

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. Firms that tend to fit are described under [property management data licensing](/industries/refer-property-management-company-data-licensing) and the [industries hub](/industries).

Unknown until SourceX reviews the opportunity: buyer interest in maintenance histories, the rights review result for owner-controlled and resident data, the de-identification needed, and whether an offer follows. Partners sign the Channel Partner Agreement before submitting introductions.

## Go deeper on maintenance escalation closure

- [Maintenance escalation closure referral brief template](/resources/maintenance-escalation-closure-referral-brief-template): a metadata-only brief for portfolio size, platforms, years and owners, with one completed Illustrative example.
- [Maintenance escalation exception examples](/guides/maintenance-escalation-closure-exception-examples): a repeat-repair case worked through step by step, with the record each decision left behind.
- [Maintenance records across systems](/guides/maintenance-escalation-closure-records-across-systems): a system map of the property platform, work order tool and accounting, and the keys that join one job.
- [Who can license maintenance escalation records](/questions/who-can-license-maintenance-escalation-closure-records): a decision tree separating owner-controlled records from the company's own, and who can say yes.

## 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 a client's maintenance history still links reopened jobs to the fix that finally held, and the transition date is known, [register as a partner](/register), check [who qualifies](/who-qualifies) and read [the terms](/terms) and [reward rules](/rewards) before that date arrives.

## Sources

- https://help.brightlysoftware.com/Content/Documentation/Maintenance/Work%20Order/Daily%20Functions/Completing%20and%20Closing%20a%20Work%20Order.htm
- https://www.appfolio.com/help/vendor-portal
- https://www.hud.gov/reac/nspire-terms
- https://refer.sourcex.si/terms