# Maintenance work order referral: a context card | SourceX

Canonical: https://refer.sourcex.si/guides/maintenance-work-orders-questions-before-referring-the-company
Last updated: 2026-11-04

Refer a company for its maintenance work orders when they describe its own equipment, worked on by its own technicians, in a system it runs, and its CEO wants the conversation. Before that, answer five context questions on one card: whose asset, whose hands, whose method, whose system and who else keeps a copy. A work order that points elsewhere on one question is not ruled out. That part gets described separately, and SourceX's rights review decides what it can include.

This page is for people who know maintenance from the inside but do not own the client's records: reliability consultants, CMMS and asset management implementers, planners who now advise, facilities services operators and repair station managers. A site walk usually tells you whether a company's work orders are rich or empty. The harder question before a referral is what those work orders are records of, and for whom.

## What a work order records, and why context outranks content

A work order is the paper trail of one job. Someone reports a fault or a schedule calls for a task, a planner sets the priority, a technician investigates and does the work, parts and hours are booked, and a supervisor closes the order or reopens it when the fix does not hold. Corrective jobs, where someone had to work out what was wrong, carry most of the reasoning; preventive tasks mostly record that a checklist was done. The [CMMS work order overview](/data-types/maintenance-data-ai-training) walks through the fields, and SourceX's comparison of [work orders and sensor data](https://sourcex.si/insights/maintenance-work-orders-vs-sensor-data-which-do-ai-developers-want) explains that work orders carry the human diagnosis and the outcome while sensors carry the physical signal.

The same sentence in a technician's note can mean different things for rights. "Replaced seized bearing, realigned coupling", written by the company's own technician about the company's own conveyor, is the company's operating history. Written by a contractor's technician about a client's chiller, inside the client's system, it is a record of a service provided to someone else. Reading the note cannot tell the two apart. Asking about its context can.

## The maintenance-context referral card

Five questions fit on one card. Answer each in a conversation with the maintenance or operations lead, at metadata level, and write down the date and who answered.

| Context question | Points to the company | Points elsewhere | What to do when it points elsewhere |
|---|---|---|---|
| Asset: whose equipment or building is it? | The company's own plant, fleet or facility | A client's building, a customer's machine, a leased asset | Describe those orders separately; service contracts decide |
| Hands: who did the work? | The company's own technicians | A contractor, an equipment maker's field engineer, a temporary crew | Note whose report it is; outside reports go to rights review |
| Method: whose procedure was followed? | The company's own procedures and checklists | An equipment maker's manual or bulletin pasted into notes | Flag pasted vendor text; a reference by document number is cleaner |
| System: where is the order recorded? | A system the company licenses and administers | A client's CMMS, an equipment maker's portal, a contractor's app | Orders in someone else's system are usually out unless contracts say otherwise |
| Copies: who else must keep this record? | Nobody outside the company | An asset owner or another holder keeps its own copy by rule or contract | A second holder does not settle rights; counsel and SourceX do |

When all five answers point to the company, the history is its own operating record and the introduction can go ahead if the CEO wants it. One or two answers pointing elsewhere usually mean a narrower description, not a stop. If the asset or system answer is "nobody knows", wait until the company finds out.

The copies question looks odd outside aviation, but aviation shows why it belongs on the card. Under 14 CFR 91.417 the registered owner or operator of an aircraft must keep maintenance records that describe the work and give the date it was completed, and certain status records go with the aircraft when it is sold. Under 14 CFR 145.219 a repair station keeps its own records of the work for at least two years from the date the article is approved for return to service, and gives the owner or operator a copy of the maintenance release. Two organizations keep a record of the same job because the rules require both to. Neither rule says who may license it. Facilities contractors, fleet maintainers and field service firms meet the same pattern through contracts instead of regulation, and the difference between holding a record and owning it is laid out in [data owner versus data custodian](/compare/data-owner-vs-data-custodian).

## Three work-order histories on the card (Illustrative)

Illustrative. Generic businesses with made-up details, and no result implied.

| Context question | A. Food plant | B. Facilities contractor | C. Aircraft repair station |
|---|---|---|---|
| Asset | Its own production lines | Clients' buildings | Customers' aircraft and components |
| Hands | Its own crew of 24 technicians | Its own technicians | Its own certificated mechanics |
| Method | Its own procedures; manuals cited by number | Equipment makers' bulletins pasted into notes | Manufacturers' maintenance data, as the rules require |
| System | Its own CMMS since 2015 | Half in its own app, half in clients' CMMS | Its own work order system |
| Copies | None outside the company | Clients keep their own | Each aircraft owner keeps one by rule |
| Next move | Introduce | Describe only its own app's orders; counsel reads the service contracts | Introduce with the open question written down, if the CEO wants to |

**A. Original work.** A 310-person food manufacturer runs six production lines with its own maintenance crew. Since 2015 every corrective job has gone into its CMMS with a failure code, a technician narrative, the parts used and the downtime. Manuals are cited by document number rather than pasted in. All five answers point to the company, and the CEO is the person introduced.

**B. Mixed third-party content.** A 220-person facilities services contractor maintains heating, cooling and electrical systems in office buildings it does not own. About half its work orders sit in its own field-service app; the rest were typed straight into clients' maintenance systems under the clients' accounts. Technicians often paste equipment makers' service bulletins into their notes. The orders in clients' systems stay out of the description unless the service contracts say otherwise. The orders in its own app are its technicians' work about clients' equipment, so counsel reads the service contracts before SourceX's rights review weighs them.

**C. An uncertain ownership case.** A 130-person repair station maintains regional aircraft and overhauls components for airline and charter customers. Its mechanics write detailed narratives in the station's own system. The narratives are its staff's work, but they describe customers' aircraft, each owner keeps its own record of the same jobs, and customer agreements may say how the station may use them. A conversation cannot settle that. If the CEO wants to explore it, the introduction goes ahead with the open question stated plainly, and SourceX's rights review and the station's counsel answer it. Which of a station's own working records are usually candidates, and which belong with the aircraft, is sorted record by record in [who owns aircraft maintenance records](/questions/who-owns-aircraft-maintenance-records).

## Finding the owner and the origin of a maintenance history

The maintenance manager or reliability lead knows which systems hold work orders, how far back each goes, which jobs contractors did and where client or equipment-maker documents sit. The planner or CMMS administrator can confirm fields and dates but answers no rights question. Counsel reads service contracts, equipment-maker terms and customer agreements. The CEO decides whether the company talks about licensing its records and signs for it.

Origin questions for that conversation: Which system came before the current one, and was its history migrated or archived? Which sites or years relied on contractors? Do technicians write in their own words, or paste vendor text? Do technician names, badge numbers or customer site addresses appear in free text? SourceX's comparison page notes that work orders raise privacy questions about technicians, so those details belong in the description even though they are dealt with later, in preparation.

The fit test sits in front of all of it: a peak of 50 or more full-time employees, counting the company's own staff and not contractors, a documented operating history, rights to license and a CEO who agrees to talk. 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.

## Questions before referring, none of which needs an export

1. Which maintenance system holds the work orders, and since which year?
2. Roughly how many corrective work orders close in a year, and how many carry a written diagnosis?
3. Whose assets are they: the company's own, clients', or both?
4. Who performs the work: employees, contractors or equipment makers' engineers?
5. Are orders ever entered into a client's or vendor's system instead of the company's own?
6. Does anyone outside the company keep its own record of the same jobs?
7. Have these records been licensed for AI training before?

Question 7 is a stop, not a review item: SourceX's suppliers confirm their data has never been licensed for AI training. If the maintenance manager offers an export to show how detailed the notes are, decline it and ask for a description instead. The company describes its records, and the partner never holds them.

## Signs the card is pointing the wrong way

- **Thin narratives.** Orders closed with "done" or "fixed" say little, whatever their context.
- **Preventive-only history.** Scheduled checklists record compliance more than judgment.
- **Someone else's system.** History that lives mainly in clients' or equipment makers' systems is rarely the company's to describe.
- **A lost predecessor.** A retired CMMS cancelled without an export leaves nothing to discuss; the [CMMS migration guide](/guides/cmms-migration) covers that moment.
- **Unknown demand.** A clean card says nothing about whether a current SourceX program wants maintenance history from that industry.
- **No published outcomes.** SourceX has not published how often maintenance histories lead to introductions or licenses. Logging each card, its five answers and the CEO's reply would start that measurement; those figures are not yet published.

## 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 card shows work orders about the company's own assets, written by its own people in its own system, and the CEO wants to talk, [sign up for a partner account](/register), test the company against [who qualifies](/who-qualifies) and read the [program terms](/terms), which call for a signed Channel Partner Agreement before your first submission. Trucking and service fleets are covered in [fleet maintenance records](/data-types/fleet-maintenance-records), service businesses in [field service work orders](/datasets/operations-and-workflows/field-service-work-orders), and further specialist guides sit in the [guides hub](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://www.ecfr.gov/current/title-14/chapter-I/subchapter-F/part-91/subpart-E/section-91.417
- https://www.ecfr.gov/current/title-14/chapter-I/subchapter-H/part-145/subpart-E/section-145.219
- https://sourcex.si/insights/maintenance-work-orders-vs-sensor-data-which-do-ai-developers-want
- https://sourcex.si/how-it-works
