Outcome-linked demonstrations review packet: nine metadata documents a repair company prepares, from task statement to rights notes

Short answer

An outcome-linked demonstrations review packet is nine short documents a repair or service company prepares before SourceX reviews its records: a job class summary, a task statement, a record chain map, the per-job field list, a linkage estimate, an acceptance check fixed in advance, the later-outcome method, volume and migration dates, and customer rights notes. Each describes records; none includes a work order, photo or test sheet before an agreement exists.

Visual briefFull-size diagram
Nine labeled documents wait in a column on the left and slide one by one into an open folder on the right: job class summary, task statement, record chain map, per-job fields, linkage estimate, acceptance check, later-outcome method, volume and migrations, and customer rights notes.
Illustrative packet for a fictional industrial motor repair shop. Each document describes records; none contains them.

The packet belongs to the guide to outcome-linked demonstrations in an ordinary workflow, which follows one repair from the customer's complaint to the inspector's signed release. This page uses a different shop, an industrial motor rewinder, to show that the packet fits any business whose work ends in a recorded test. Partners do not prepare it. It is set out here so an introducer can explain to an owner what readiness looks like, and so the owner can judge the effort before agreeing to talk.

The packet contents, in order

The sequence moves from what kind of job this is, through where each step is recorded and how well the steps join, to how a job is judged and who may license the records.

#DocumentWhat it showsWho prepares it
1Job class summaryThe kind of repair, component families, systems and years coveredQuality manager
2Task statementThe job the technician is meant to complete, in two sentencesDirector of maintenance
3Record chain mapWhich system holds each step and which number joins themMaintenance system administrator
4Per-job field listThe fields that must exist on each job for it to countQuality manager
5Linkage estimateShare of jobs where the inspection carries the job numberMaintenance system administrator
6Acceptance checkThe fixed test a job must pass to count as a verified resultQuality manager and chief inspector
7Later-outcome methodHow repeat removals or returns are matched, and over what periodQuality manager
8Volume, span and migrationsJobs per year by component family, years kept, system changesMaintenance system administrator
9Customer rights notesContracts that limit repair data, personal data presentLegal counsel or the CEO

What goes into each document

1. Job class summary. Illustrative: "Rewind and overhaul of industrial AC motors from 50 to 500 horsepower for water utilities and food plants; shop management system plus scanned test-bay reports; 2016 to present."

2. Task statement. Given a motor's reported symptom and the strip-down findings, choose between rewinding, re-bearing or replacing the rotor, carry out the repair to the nameplate rating, and pass the final electrical and vibration tests on the first attempt.

3. Record chain map. A short table: job card in the shop system, strip-down findings and winding data in the same system, failure codes in a coded field, insulation and surge test printouts scanned and indexed by job number, vibration readings in a separate analyzer database until a stated year. It names the key that joins each pair.

4. Per-job field list. The fields a job needs to count:

  • ☐
    Job number present on every record in the chain: work order, findings, codes, test sheet, inspection.
  • ☐
    Starting complaint or removal reason.
  • ☐
    Ordered actions with sign-offs and the procedure revision used.
  • ☐
    Coded or clearly written cause and remedy.
  • ☐
    Measured test result against a stated limit.
  • ☐
    Final inspection outcome with the approver's role and authorization.
  • ☐
    Later outcome where known: repeat removal, warranty return or none within a stated period.

5. Linkage estimate. One figure per year or per system era: the share of jobs whose inspection record carries the job number. A labeled estimate is fine.

6. Acceptance check. Written out in the next section.

7. Later-outcome method. The follow-up period (for example, 12 months), how a returning unit is matched to its earlier job (serial number, customer reference), and which customers report returns at all.

8. Volume, span and migrations. Jobs per year by component family, years retained, and the date of any move between maintenance systems or from paper to scans.

9. Customer rights notes. Customer contracts that say repair data belongs to the operator, personal data in records (technician names, certificate numbers), and anything a regulator requires the shop to keep confidential. These are questions for review, not legal conclusions.

The acceptance check, applied to two motors (Illustrative)

A job counts as a verified result only if all four conditions hold:

  1. The test result is within the stated limit.
  2. The final inspection was signed by someone other than the technician, and after the test.
  3. The remedy addresses the coded cause.
  4. If a later outcome is claimed, the period and the matching method are stated.

Condition 2 borrows from aviation, where the rule is public: 14 CFR 145.213 requires a repair station to inspect each article before approving it for return to service, and 14 CFR 43.9 requires the approver's signature, certificate number and kind of certificate. A motor shop is not bound by those rules, but the same independence is what makes its pass meaningful. Two fictional jobs from the rewinder:

ConditionMotor A (job 4410, 200 hp)Motor B (job 4468, 150 hp)
Test within limitPass: insulation resistance and surge test within the shop's stated limitsPass: within limits
Independent inspector, after the testPass: test-bay lead signed the next morningFail: the winder who rewound it signed the release, same timestamp as the test
Remedy addresses coded causePass: winding failure coded, full rewind performedPass: same codes
Later outcome method statedPass: 12-month warranty window, matched by nameplate serialPass: same method
ResultCounts as a verified resultDoes not count, though the motor may well run fine

Motor B is the instructive case. The repair was probably good, and a record of final statuses would show it as passed. The check excludes it because the result was not independently confirmed, which is exactly the property that makes an outcome-linked demonstration worth more than a list of completed jobs.

Assembling it without handing over records

Each document can be written from what staff know or can count inside their own systems. The administrator counts linked inspections; nobody exports them. The quality manager describes the follow-up method; nobody sends a returns report. Discovery for partners stays at metadata level: what the records are, how many, how far back, which systems, who owns them. If an owner offers sample work orders, decline and point them to SourceX's process.

What the packet does not settle

The quality manager and director of maintenance usually prepare most documents, 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.

The packet cannot show how many jobs pass the check, how technician and customer details would be de-identified, whether customer contracts allow use, or whether any buyer wants this task type. Owners asking why linked repair records matter can read about cross-system data value, why AI agents fail at multi-step work, and where AI training data comes from; the single-step version of the idea is on task and outcome pairs. Before a packet is worth discussing, rate the company with the outcome-linked demonstrations qualification scorecard and describe weak links with outcome-linked demonstrations evidence gaps.

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 quality manager thinks documents 3 to 8 could be drafted from what the shop already keeps, register as a partner, confirm the basics on who qualifies, and read the terms before you introduce the CEO or director of maintenance.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Who prepares the packet?

The company's own staff, after a conversation with SourceX has started and under SourceX's agreement with the company. The partner does not assemble, review or hold it.

Does the packet need exact counts?

No. Estimates are acceptable if they are labeled and say how they were made, such as a sample of last year's jobs or a report from the maintenance system. Exact counts come out of the review itself.

Why is the later-outcome method a separate document?

Because a claim that a fix held is only as good as the matching behind it. Stating the period and how repeat jobs are matched to the original lets a reviewer judge that claim instead of taking it on trust.

Sources

  1. ecfr.gov/current/title-14/chapter-I/subchapter-C/part…
  2. ecfr.gov/current/title-14/chapter-I/subchapter-H/part…
  3. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment