This gap analysis belongs to the guide to outcome-linked demonstrations in an ordinary workflow, where one pump repair under work order WO-7731 runs cleanly from removal reason to signed release. Real archives are rarely that tidy. This page sets out what a review expects to link, what companies typically keep, and how to describe the difference honestly when you introduce one.
What a review expects to link for each job
A job counts as an outcome-linked demonstration only if a reviewer can join the work to an independent, verified result. For a repair, a review looks for five links on every job:
- Work order with action notes. The starting complaint and what was done, in order.
- Fault classification. What failed and why, picked from a list rather than typed as free text.
- Final inspection linked by job number. The check that confirms the result, carrying the same work order number.
- Approver identity and authority. Who signed, and on what authorization.
- Later field outcome. Whether the unit came back for the same fault within a stated period.
Links 1 to 3 make a basic demonstration; 4 makes it trustworthy; 5 shows whether the result lasted.
How an archive shrinks link by link (Illustrative)
A simple way to measure an archive is to start with every job in a year and count how many still carry each link. The counts below are invented to show the method. Real figures for any company are not published and can only come from its own records.
| Link in the chain | Work orders remaining | What drops jobs out at this stage |
|---|---|---|
| Work order with action notes | 1,000 | Starting point: every job has some notes |
| Failure codes recorded | 820 | Codes skipped on rush jobs or entered as "other" |
| Final inspection linked by work order number | 610 | Inspections signed on paper without the number, or filed by serial number only |
| Later field outcome known | 240 | No repeat-removal check; customers do not report back |
The pattern is common even though the numbers are not real: each link costs some share of the archive, and the share lost at the inspection link is often the surprise. Quality managers know inspections happen on every job; fewer know how many inspection records carry the job number that ties them back.
Expected, typically held and usually missing
| Evidence | Expected by a review | Typically held | Usually missing |
|---|---|---|---|
| Action notes | Ordered steps with sign-offs | Present on almost every job | Step order on older paper jobs |
| Cause and remedy | Coded per job | Coded on most jobs | Codes on rush work; "other" used as a catch-all |
| Final inspection | Linked by work order number | Inspection exists for every job | The number on the inspection itself |
| Procedure revision | Recorded per job | Known to the shop | Written on the job record |
| Approver authority | Name plus role or certificate | A signature or initials | Which authorization the signer held |
| Field outcome | Traced for a stated period | Warranty returns for some customers | Any follow-up for non-warranty units |
| Customer data rights | Known per contract | Known to the quality manager | Written down in one place |
Maintenance software can support the classification row: IBM describes how a failure class hierarchy in Maximo records component, cause and remedy on a work order. Whether staff actually fill it in on rush jobs is a separate question.
Four gaps that decide whether a surviving job is usable
Procedure version not recorded. A repair done to an older manual revision is still valid, but only if the revision is written down. Without it, a reviewer cannot tell an outdated method from a mistake.
Inspector authority unclear. The record must show who approved the work and on what authorization, not just that "QA" passed it. Aviation sets the public benchmark: 14 CFR 145.213 requires a repair station to inspect each article before approving its return to service, and 14 CFR 43.9 requires the approver's signature, certificate number and kind of certificate. An unnamed pass breaks the independence that makes the result worth linking to.
Outcome contradicted later. A pump that passed inspection but came back in a month is still useful, as a failure example, but only if the second work order points to the first. Linked, it teaches what a passing inspection missed. Unlinked, it is noise.
Customer-owned records. Some operators require that repair data about their fleet stays theirs. That can limit what the repair station can license, regardless of how good the links are. The quality manager usually knows which contracts say this.
How to describe the gaps in an introduction
A good introduction note states each gap with a rough size and a source. Illustrative wording, all fictional:
| Gap | Note that helps | Note that misleads |
|---|---|---|
| Inspection linkage | "Quality manager estimates 60% of inspection forms carry the WO number; paper before 2020" | "Every job is inspected" |
| Coding | "Codes on most jobs; 'other' common on rush work" | "Failures are fully coded" |
| Field outcome | "Repeat removals traced only for two warranty customers" | "We track quality" |
| Customer rights | "Two large operators own their repair data by contract" | "The records are ours" |
An estimate with its source is enough at this stage. Exact counts come from SourceX's review, not from the introducer.
What stays for SourceX's review
The real counts at each link, whether records survived a maintenance system migration, how customer and technician details would be de-identified, which customer contracts restrict use, and whether any buyer wants this task type are all settled in SourceX's review under an agreement with the company. Partners stay at metadata level and never handle work orders, test sheets or photos.
The quality manager and the director of maintenance usually hold the answers, and the CEO or owner authorizes a licensing discussion. The company needs 50 or more 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 70% of the data is in English.
Single action-and-result records are covered on task and outcome pairs. Why fully linked records are scarce, and therefore valuable, is the subject of proprietary data as a moat and cross-system data value; where AI developers get such material today is in where AI training data comes from. Rate the company first with the outcome-linked demonstrations qualification scorecard; after an introduction it prepares the outcome-linked demonstrations review packet.
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 most jobs survive at least the inspection link and the gaps are ones you can name, register as a partner, confirm the basics on who qualifies, and read the terms before you introduce the CEO or director of maintenance with your notes attached.