Result-to-approved-correction completeness scorecard: eight lab record checks with pass, partial and fail marks

Short answer

A result-to-approved-correction trail breaks in four places: a quality event record that does not name the exact sample and report, a correction that overwrites the original value, a corrected report reissued without a new version marker, and copies outside the controlled system that nobody updates. The scorecard below turns those breaks into eight checks a partner can mark pass, partial or fail in one conversation with the quality lead, without seeing a single test value, investigation file or certificate.

Visual briefFull-size diagram
Eight correction-trail checks, from result coverage to downstream copies, tick pass, partial or fail one by one while a horizontal meter fills to 11 of 16 points.
Illustrative scoring for a fictional contract testing lab. The score describes the trail; it does not predict acceptance.

This scorecard is part of the result-to-approved-correction records guide, which covers the metadata packet for the same chain. If you want the identifiers behind each check first, read the related page on result-to-approved-correction record linkage.

How to score a correction trail without seeing a result

Book 30 minutes with the quality lead and, if possible, the person who administers the laboratory information system and whoever controls issued documents. Read each check's question aloud and mark it from the answer you hear. If nobody knows, write "unknown" and score it as fail until someone confirms otherwise.

Each mark carries points: pass 2, partial 1, fail 0. Eight checks give a maximum of 16. The total summarizes the trail for your own notes; the sentence you write from it matters more than the number.

Three rules keep the scoring honest:

  1. Score the system, not the best case. A lab that links its quality events to specimens "on the big investigations" scores partial, not pass.
  2. Score what exists now. A planned platform replacement does not raise today's mark. Note the date instead, because migrations are when audit trails and old revisions most often get left behind.
  3. Do not ask for examples. If anyone offers to show you a case file, decline politely. The scorecard works from structure and counts.

The eight checks, grouped by what they test

The checks fall into five groups: coverage, linkage, timestamps, outcomes and gaps. Each row says how to check it at metadata level and what earns each mark.

#GroupCheckHow to check it at metadata levelPassPartialFail
1CoverageResult historySince which year are results and their audit trail held electronically?Ten or more years, or a documented migrationElectronic, but older years only as printoutsUnder three years, or unknown
2CoverageQuality event historySince which year are quality events held electronically, and can wrong-unit or keying errors be counted?Electronic with a countable error typeElectronic, error type in free textPaper only, or not counted
3LinkageEvent to specimen and certificateDoes each quality event name the specimen ID and the certificate number?Both, as fieldsBatch or client onlyNeither
4LinkageOriginal value keptWhen a result is corrected, does the audit trail keep the first entry beside the new one?Kept, with a reason that cites the event numberKept, reason in free textOverwritten, or corrected before entry
5TimestampsDated stepsAre value entry, event opened, approval and reissue each recorded with a system timestamp?All four dated in systemsApproval only on a signed PDFOnly the reissue date survives
6OutcomesReport versionDoes a corrected report carry a new revision and reference the one it replaces?New revision that names its predecessorNew revision, no referenceSame number regenerated
7OutcomesInvestigation scopeDoes the investigation record which other specimens or lots were checked?Recorded on every wrong-unit or keying eventRecorded for major deviations onlyNot recorded
8GapsDownstream copiesAfter a reissue, can the lab show where every earlier copy went and whether it was withdrawn?Distribution list with each copy's statusPortal copies tracked, emailed PDFs notNot tracked

Checks 4 and 7 are where regulated labs usually score well, because the rules ask for exactly those records. For electronic records in closed systems, 21 CFR 11.10 requires secure, computer-generated, time-stamped audit trails and says record changes shall not obscure previously recorded information. For drug manufacturers and the labs testing for them, 21 CFR 211.192 requires any unexplained discrepancy to be thoroughly investigated, extended to other batches that may be associated, and written up with conclusions and follow-up. FDA's 2022 guidance on out-of-specification results describes when an investigation must expand outside the laboratory.

Why the downstream-copies check often scores lowest

Both rules govern records inside the quality system. Neither tracks a PDF after it leaves. That is why check 8 is the one to ask about carefully.

Take a unit error: a result reported in mg/kg when the method specifies µg/kg. The lab corrects the LIMS record with the original kept in the audit trail, closes a deviation with an approved root cause and issues a revised report. Inside the lab, checks 3 to 7 can all pass. But the first report was already emailed as a certificate of analysis and pasted into a client's trend spreadsheet, and nothing in the lab's systems records those copies.

Ask the question in plain words: "When you reissue a report, what happens to the copies already sent?" Answers tend to fall into three groups:

  • "We keep a distribution list and confirm each withdrawal." Pass. Note since when.
  • "The portal copy is replaced automatically; we email clients to tell them." Partial. The lab can show the notice, not the outcome.
  • "We send the new one and assume they use it." Fail, and an honest answer.

A lab whose history shows the correction and its reach is describing a different record from one whose history shows only the correction. Both can be worth an introduction; the mark tells SourceX which one it is.

A scored example: a contract testing lab (Illustrative)

A fictional 310-person contract lab testing raw materials and finished products for food and supplement manufacturers. All answers are invented to show the level of detail.

#CheckAnswer heardMarkPoints
1Result historyLIMS since 2012; migration documentedPass2
2Quality event historyQuality system since 2017; unit error is a picklist typePass2
3Event to specimen and certificateSpecimen ID field; certificate number in free textPartial1
4Original value keptAudit trail keeps both; reason field cites the event since 2019Pass2
5Dated stepsApproval recorded as a signed PDF onlyPartial1
6Report versionRevision suffix that names the replaced reportPass2
7Investigation scopeRecorded for major events onlyPartial1
8Downstream copiesEmailed certificates not trackedFail0
AllTotalEight checks scoredSum11 of 16

How a partner would summarize it: "Electronic corrections with preserved originals since 2019, versioned reports, deviations countable by type from 2017; approvals on signed PDFs; no tracking of emailed copies." That sentence tells SourceX where the joined history starts and where it stops. For a broader view of how buyers judge record quality, see data quality due diligence; for why correction records draw interest at all, see how to assess human review records and correction workflows.

Who answers each check, and who can authorize the conversation

The scorecard points to the owners. The LIMS administrator answers checks 1 and 4, the QA manager checks 2, 3, 5 and 7, and the document control lead checks 6 and 8. None of them usually has authority to license records. That sits with the lab director, a general manager or the owner.

Before you introduce, confirm the basics: 50+ 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.

What stays unknown until SourceX reviews it: which records are the lab's own to license (client results often need client consent, as the testing lab licensing page explains), how client and regulatory confidentiality would be handled, which years a buyer would want and what the lab would be paid. Partners never ask for or handle raw results, deviations or reports. If the lab sits in an investor's portfolio, the portfolio review handoff checklist helps time the conversation. To see how one correction reads with and without its surrounding records, use the sibling missing-context walkthrough.

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.

When the QA manager can score all eight checks and say plainly where the trail stops, register as a partner, confirm the lab on who qualifies and read the program terms before you introduce the director.

  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

What total score means a lab is worth introducing?

There is no threshold. The scorecard helps you describe the trail honestly; it does not predict whether SourceX or a buyer will want it. A lab that scores 7 of 16 and can explain each fail is a better introduction than one that claims 16 without evidence.

Who in the lab should answer the eight checks?

The QA manager can answer most of them. The LIMS administrator helps with the audit trail and coverage checks, and the document control lead with versions and distribution. None of them needs to open a result or a report to answer.

Does a fail on distribution mean the records are unusable?

No. Many labs cannot show where every emailed copy went. A fail marks the edge of what the records prove, which SourceX needs to know when it scopes a review.

Sources

  1. refer.sourcex.si/terms
  2. ecfr.gov/current/title-21/chapter-I/subchapter-C/part…
  3. ecfr.gov/current/title-21/chapter-I/subchapter-A/part…
  4. fda.gov/media/158416/download

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