This scorecard is part of the component-to-defect-disposition records guide. Use it after you know which systems the plant runs and before you tell anyone the history is worth reviewing.
How to run the scorecard in one conversation
Book thirty minutes with the plant quality manager and ask for the warehouse lead to join for the last ten. You need descriptions, not screens. Every answer goes into one of three marks:
- Pass (2 points): a named person says the condition holds for the whole period they describe.
- Partial (1 point): it holds for some years, some product lines or some sites, and they can say which.
- Fail (0 points): it does not hold, or nobody present knows. Write "unknown" next to the zero rather than skipping it.
Seven checks give a maximum of 14 points. The total is less important than the pattern: a plant with strong forward linkage and a weak warehouse step tells a different story from one with good batch data and dispositions decided in email.
Keep the scorecard in your own notes, shared only with the people who answered. It describes systems, years and habits. No part numbers, supplier names, drawing numbers, customer names or defect descriptions belong on it.
The seven checks, with pass, partial and fail lines
| Check | Metadata question to ask | Pass | Partial | Fail |
|---|---|---|---|---|
| 1. Coverage overlap | "Which years does each system cover: warehouse, MES, QMS?" | Five or more years held in all three systems at once | Overlap exists but under five years, or one site missing | One system replaced with no history carried over |
| 2. Supplier lot capture | "Is the supplier lot stored on the receiving batch in the system?" | Stored as a field on every receipt | Stored for some materials or from a later year | Only on paper certificates |
| 3. Relabel lineage | "When stock is repacked or relabeled, does the new batch point to the old one?" | Parent batch recorded on every repack | Recorded for some flows, such as kitting only | New batch created with no parent |
| 4. Consumption timestamp | "Is component consumption scanned at the line or posted when the order closes?" | Scanned at the line, per batch | Mixed: scanned on some lines, backflushed on others | Backflushed at order close for all lines |
| 5. Specification version | "Does each nonconformance record the drawing or specification revision it was judged against?" | Revision stored on every report | Stored for some product families | Only the current revision exists |
| 6. Disposition outcome | "Is use as is, rework, scrap or return to supplier recorded with an approver and a date?" | All four outcomes recorded with approver and date | Outcome recorded, approver or date missing in some years | Decided in email, closed as "done" |
| 7. Corrective action evidence | "When a corrective action closes, is there a recorded check that it worked?" | Effectiveness check stored with the action | Check exists for major actions only | Closed on a date with no check |
Two notes on scoring. Checks 2 and 3 can only be answered by the warehouse lead in most plants, which is why they join late. Check 5 matters more in regulated plants: medical device makers have run under FDA's Quality Management System Regulation since February 2, 2026, which amends 21 CFR Part 820 to incorporate ISO 13485:2016 by reference, so their revision control is often stronger than a general manufacturer's. Do not assume it; ask.
The relabel check: why it is the easiest to fail
Check 3 is easy to lose because a batch identity can be born in several places. According to SAP's EWM documentation, a batch number may arrive from a connected system such as SAP ERP, may be keyed directly in EWM, and may be generated by EWM for an inbound delivery. So when a pallet is broken down into kanban trays or assembly kits, the warehouse can mint an identity that the shop floor never ties back to what the supplier shipped.
Nor does the standard tracing report close the gap. SAP builds its batch where-used list from inventory postings and their reversals in Materials Management, and states that batches picked at order release are left out. A split that leaves behind only a fresh printed label, with no posting naming its source, gives that report nothing to walk. Quality can follow the failed order as far as the tray or kit, and no further.
To score it, ask: "When a pallet is split into trays or kits with their own labels, can quality still get from a failed cabinet back to the supplier's shipment?" Listen for one of three replies:
- "Yes, the split transaction carries the source batch." Pass; ask which year that started.
- "Yes, from the kitting log." Partial; the link lives in a log or spreadsheet the system does not read.
- "No, we would phone the supplier." Fail; note which material flows are split.
An Illustrative completed scorecard
Illustrative. A fictional 340-person maker of low-voltage switchgear cabinets, one plant and an off-site kitting warehouse, answered the seven checks in a single meeting.
| Check | Mark | Points | What they said |
|---|---|---|---|
| 1. Coverage overlap | Pass | 2 | Warehouse system since 2017, MES since 2012, QMS since 2010 |
| 2. Supplier lot capture | Partial | 1 | Lot field on breaker and busbar receipts from 2021; mill certificates only for sheet steel |
| 3. Relabel lineage | Fail | 0 | Kits built off-site get a kit label and no source batch |
| 4. Consumption timestamp | Partial | 1 | Scanned at final wiring; backflushed in the sheet-metal shop |
| 5. Specification version | Pass | 2 | Wiring-diagram revision on every report since 2015 |
| 6. Disposition outcome | Pass | 2 | All four outcomes with approver and date since 2016 |
| 7. Corrective action evidence | Partial | 1 | Effectiveness checks only for actions raised by customers |
| Total | 9 of 14 | 9 | Cabinet-to-disposition link strong; supplier link ends at the kit |
Played back to the quality manager, it fits in one sentence: every failed cabinet reaches a recorded decision, but tracing a faulty breaker to its supplier shipment works only for parts that skipped the kitting warehouse. That is a sound description for an introduction. It promises nothing about value; it tells a reviewer where to look first. The warranty claims data page shows how field failures can extend the same trail after shipment, and the record linkage guide maps the identifiers behind checks 2 to 4.
Who answers each check, and what the score cannot tell you
The quality manager can answer checks 1 and 5 to 7. The warehouse lead answers 2 and 3, and the manufacturing systems lead answers 4. None of them can authorize a licensing discussion: production and quality records cross the whole plant, so the CEO, usually the owner in an owner-run company, authorizes it, often with the general manager or COO as sponsor. The quality inspection introduction checklist covers how to reach that person, and quality assurance workflows describes the wider data type.
Before you introduce, confirm the company baseline: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license the records, 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. Sign the Channel Partner Agreement before submitting.
The score cannot tell you whether customer quality agreements limit reuse of part-specific records, whether the reports can be de-identified to a buyer's standard, or whether any buyer wants this history. Those stay unknown until SourceX reviews the company under its own agreement. You never see, request or forward a batch record or a nonconformance report. Other record locations sit under systems.
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 a plant you work with can score all seven checks honestly, fails included, and its CEO will take a call, register as a partner, check the company against who qualifies, and read the program terms before you submit.