# Outcome-linked demonstrations fit scorecard | SourceX

Canonical: https://refer.sourcex.si/questions/does-outcome-linked-demonstrations-data-qualify
Last updated: 2026-11-04

Rate a repair or service company in two steps. First, five eligibility checks must all be yes: 50 or more full-time employees at peak, documented history, rights to license (including customer contract limits), an authorized contact, and a covered location (with at least 70% English records outside the U.S., Canada and the EU). Then rate six record rows by the share of jobs that carry each link: closing check, job number on the inspection, coded cause and remedy, procedure revision, independent inspector, and later outcome. Five or six strong rows is a strong fit.

This scorecard is part of the guide to [outcome-linked demonstrations in an ordinary workflow](/guides/concept-outcome-linked-demonstrations), which follows one hydraulic pump from removal reason to signed release under a single work order number. That guide shows what one well-linked job looks like. This page asks how many of a company's jobs look like that, using answers a quality manager can give from memory.

## Why this scorecard rates shares of jobs

Most repair companies have some jobs that are perfectly linked and many that are not. A yes or no question ("do you record inspections?") gets a yes from almost everyone and tells you little. The useful question is what fraction of jobs carry each link, because the fully linked set is what a buyer can use, and every weak row cuts it down.

So each record row is rated by share:

- **Strong:** the link is present on roughly 80% or more of jobs.
- **Borderline:** roughly half to 80%.
- **Weak:** under half, or nobody knows.

The thresholds are a sorting aid, not a buyer requirement. They keep a conversation honest: "we always do that" becomes "about how often does the form actually carry it?"

## The outcome-linked demonstrations scorecard

**Eligibility checks (all must be yes)**

| Check | Yes | No |
|---|---|---|
| Headcount | 50+ full-time employees at peak, contractors excluded | Under 50, or mostly contractors |
| Operating history | Several years of work orders in a known maintenance or service system | A recent start or rebuilt records |
| Rights | The company owns its repair records; customer contracts allow use or are silent | Customers own the repair data under contract |
| Authority | A named CEO or owner can approve a licensing discussion | Nobody can say who decides |
| Location and English share | Based in the U.S., Canada or the EU, or in another covered country with 70%+ of records in English | Not in a covered country, or below 70% English outside the U.S., Canada and the EU |

The location rule in full: 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.

**Record rows (rated by share of jobs)**

| Row | What strong looks like | What weak looks like |
|---|---|---|
| Closing check recorded | A named test, inspection or customer sign-off ends every job | Checks happen but are written down only sometimes |
| Job number on the inspection | The work order number is printed on the inspection record itself | Inspections filed by date or serial number only |
| Cause and remedy coded | Picked codes for problem, cause and remedy | Free-text notes only, or "other" on most jobs |
| Procedure revision noted | The manual or procedure revision is recorded on the job | Nobody records which version was followed |
| Independent inspector | A person other than the technician signs, with role or certificate | "QA passed" with no name |
| Later outcome traced | Repeat repairs, warranty returns or callbacks link back to the original job | No one checks whether the fix held |

**Reading the result.** With all five eligibility checks at yes: five or six strong rows is a strong fit, three or four is borderline (introduce with the weak rows named), two or fewer is weak for now. Any no on eligibility stops the introduction.

## Questions that fill each row

Ask the quality manager, director of maintenance or operations lead. Each question invites an estimate, not a file.

1. **How does a job end?** Listen for a named check recorded every time. Rates the closing check row.
2. **What share of inspection records carry the work order number?** Ask how they know: an audit, a form field, a habit. Rates linkage.
3. **Are cause and remedy picked from codes, or typed as notes?** Coding is not required for strong, but it makes thousands of jobs comparable; IBM describes how Maximo's failure class hierarchy records component, cause and remedy on a work order. Rates coding.
4. **Do technicians record which manual or procedure revision they used?** Rates the revision row.
5. **Who signs the final inspection, and is it ever the same person who did the work?** Rates independence.
6. **When a unit comes back, does the new job point to the old one?** Rates later outcome.
7. **Who owns these records, which customers restrict repair data, and who can approve a licensing discussion?** Settles rights and authority.

The independent-inspector row borrows from aviation, where the rules are public. Under 14 CFR 145.213 a certificated repair station must inspect each article it worked on before approving it for return to service, and 14 CFR 43.9 requires the approver's signature, certificate number and kind of certificate. Outside aviation the requirement is looser, but the same question applies: can the record show that someone other than the technician confirmed the result?

Write down the estimate and the reason given for it. "About 90%, because the form will not close without it" is more useful to SourceX than your rating.

## Three fits, rated (Illustrative)

All three companies are fictional; the ratings illustrate the method, not a forecast.

**Strong: a 230-person industrial gearbox rebuilder.** Every rebuild ends in a load test and a signed release; the maintenance system will not close a job without the inspection attached. Cause and remedy are coded, procedure revisions are recorded, and a separate inspector signs. Repeat repairs are linked back for warranty units but not others. Eligibility all yes; five strong rows and one borderline (later outcome).

**Borderline: a 160-person commercial HVAC service contractor.** Technicians close jobs on tablets with a customer signature, and the tablet forces a cause and remedy code from a short list. About two thirds of callbacks reference the original ticket. Procedure versions are not recorded, and the technician usually signs off their own work. Eligibility yes; three strong rows (closing check, job number, coding), one borderline (later outcome) and two weak. Worth introducing, with the revision and independence gaps stated.

**Weak: a 90-person calibration laboratory.** Records are excellent, but its main customers' contracts say calibration results belong to them. The rights check is no, so the record rows do not matter yet.

## Owners, authority and what the rating cannot settle

The quality manager usually knows how records are kept and which customer contracts restrict data; the director of maintenance or operations owns the systems; 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.

The rating cannot show how many jobs pass a reviewer's acceptance check, how customer and technician details would be de-identified, or whether any buyer wants this task type. Interest in outcome-linked data does not mean every maintenance archive qualifies. Partners stay at metadata level: which system, how many jobs a year, how many years, who owns them. No work orders, photos or test sheets change hands.

Companies with large maintenance histories outside aviation are covered on the [fleet maintenance records](/data-types/fleet-maintenance-records) and [field service histories](/data-types/field-service-histories) pages; single action-and-result records are on [task and outcome pairs](/data-types/task-and-outcome-pairs). Check the basics with the [company qualification checklist](/resources/company-qualification-checklist). Weak rows can be described using [outcome-linked demonstrations evidence gaps](/questions/outcome-linked-demonstrations-evidence-gaps), and after an introduction the company prepares the [outcome-linked demonstrations review packet](/resources/outcome-linked-demonstrations-review-packet). For why linked records are worth more than any one system's export, see [cross-system data value](/guides/cross-system-data-value-ai).

## 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 every eligibility check is yes and at least three record rows rate strong, [register as a partner](/register), confirm the basics on [who qualifies](/who-qualifies), and read the [terms](/terms) before you introduce the CEO or director of maintenance.

## Sources

- https://www.ecfr.gov/current/title-14/chapter-I/subchapter-C/part-43/section-43.9
- https://www.ecfr.gov/current/title-14/chapter-I/subchapter-H/part-145/subpart-E/section-145.213
- https://www.ibm.com/support/pages/create-failure-class-hierarchy-populate-specific-category-component-cause-and-remedy-work-order-0
- https://refer.sourcex.si/terms
