# Who can license maintenance records? | SourceX

Canonical: https://refer.sourcex.si/questions/who-can-license-maintenance-escalation-closure-records
Last updated: 2026-10-19

Start with the operations director, because they run maintenance and know where escalations are written down. The person who can authorize a licensing discussion is the CEO of the management company (often its owner), with counsel reviewing management agreements. Platform administrator rights are not authority. If the company manages for third-party owners, control of some records may sit with those owners, and what is licensable stays unknown until SourceX's rights review.

This decision tree belongs to the [maintenance escalation closure guide](/guides/workflow-maintenance-escalation-closure). It answers one question for property systems consultants: inside a management company, who can say yes to a conversation about its maintenance escalation history?

## Who touches the records

Maintenance history is spread across a property management company, and a consultant who implemented a platform probably knows several of these people:

- **Operations director.** Knows the systems, volumes and escalation practice. Sponsors the conversation, rarely signs.
- **Maintenance supervisors.** Know the real reopen rate and where escalation notes actually live. Useful later for scoping, never the first contact.
- **Controller.** Knows how contractor invoices are stored and whether they cite work order numbers.
- **Platform administrator.** Can run exports and configure fields. That is technical access.
- **CEO (often the owner).** Decides whether the company will discuss licensing its operating records.
- **Counsel.** Reads the management agreements' records clauses and any tenant privacy obligations.

Contractors are outside the tree. Their portal is not a record store for the management company: in AppFolio's Vendor Portal, for example, completed work orders are removed from the vendor's view once the job is marked Work Done. The history that matters is on the management company's side.

## The tree: five questions in order

Read the graphic from left to right. The same path in words:

1. **Will the operations director convene?** If your contact is a supervisor or the platform administrator, ask who runs maintenance end to end, then ask that person whether they would sponsor an internal conversation. If no, stop.
2. **Whose records are they?** Separate the company's own process records (escalation rules, contractor scorecards, internal reviews, supervisor logs) from operating records kept for property owners (requests, work orders, invoices charged to the property). The [record ownership explainer](/questions/who-owns-property-management-records) covers the usual split.
3. **For owner-controlled records, what do the management agreements say?** Records clauses often decide who controls work orders during and after the contract. Counsel reads them; if agreements give owners control, those owners may need to consent.
4. **Is any property HUD-insured or assisted?** For those properties the answer may already be written down. In HUD's management agent certification (form HUD-9839-B), the agent agrees that all records related to the operation of the project, regardless of where they are housed, are the property of the project, and that the project's records go to the owner when the management agreement ends. A manager's work orders for such a property are, on that wording, the project's records. Flag it; let counsel interpret it.
5. **Who approves?** The CEO, with counsel reviewing any owner agreements or tenant data involved.

## Roles side by side

| Question | Operations director | Supervisors | Controller | Platform admin | Counsel | CEO |
|---|---|---|---|---|---|---|
| Where do requests, orders and escalations live? | Knows | Knows | Partly | Knows | No | Rarely |
| How are reopens linked? | Partly | Knows | No | Knows | No | No |
| How are contractor invoices stored? | Partly | No | Knows | Partly | No | No |
| What do management agreements say about records? | Partly | No | No | No | Knows | Partly |
| Can convene the discussion? | Yes | No | No | No | No | Yes |
| Can approve a licensing discussion? | No | No | No | No | Reviews terms | Yes |

The convener and the approver are usually different people, and both belong in the introduction. An introduction to the platform administrator alone tends to go nowhere, however helpful they are.

## Three portfolios, three routes (Illustrative)

Fictional companies invented for this page; not real cases.

| Step | 300-person owner-operator | 520-person fee manager for third-party owners | 180-person manager with HUD-assisted sites |
|---|---|---|---|
| First contact | Platform administrator | Maintenance supervisor | Operations director |
| Convener | Operations director | Operations director | Operations director |
| Whose records | Mostly the company's own | Largely owner-controlled under agreements | Assisted sites' operating records belong to each project |
| Review gate | Counsel on tenant data | Counsel on each owner agreement; owner consent may be needed | Counsel on the HUD certifications and owner agreements |
| Approver | CEO | CEO, plus consenting owners | Owner, as CEO |

The owner-operator has the shortest route because it owns the buildings and the records. The fee manager's route depends on its agreements, which changes scope and timing, not eligibility. The narrower question of who controls work orders when a single contract moves is covered in the [management contract transition guide](/guides/moment-management-contract-transition-property-systems-consultants).

## What stays open until rights review

Which records and years are the company's to license; which require owner consent; how tenant names, units and contact details are excluded or de-identified; whether buyers want maintenance escalation histories at all; and whether an offer follows. [Why data rights matter](/proof/why-data-rights-matter) explains why that review happens early. If the company is closing rather than transitioning, [preserving company records before shutting down](/guides/preserve-company-records-before-shutting-down) covers the records side.

A partner asks for roles, record classes and systems only. Never request work orders, photos, invoices or tenant details, and never treat an administrator's offer to export as approval. The [system map](/guides/maintenance-escalation-closure-records-across-systems) gives the convener the vocabulary to describe the records, and the [referral brief template](/resources/maintenance-escalation-closure-referral-brief-template) puts the answers on one page.

The introduced company needs 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 90% of the data is in English. Partners sign the Channel Partner Agreement before submitting; one partner is credited per company. Management companies that tend to fit are described on the [property management licensing page](/industries/refer-property-management-company-data-licensing).

## 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.

Once the operations director has agreed to convene and the CEO is named as approver, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you make the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://www.appfolio.com/help/vendor-portal
- https://www.hud.gov/sites/dfiles/documents/9839-b.pdf