Traceability in a testing or calibration laboratory means you can follow any result — forwards or backwards — through the entire chain: the sample it came from, the method used, the instrument that produced the measurement, the calibration status of that instrument at the time, and the operator who performed the test. Every link in that chain needs to be documented and connected.
In practice, most labs have partial traceability. The instrument calibration records are somewhere. The test data is somewhere else. The report is in a third system. And linking them together under audit pressure requires manual searching. Here's how to close the gaps.
1. Metrological Traceability: Your Calibration Chain Must Be Unbroken
Under ISO/IEC 17025 Clause 6.4, every measurement result must be traceable to national or international measurement standards through an unbroken chain of calibrations. For most labs, this means:
- Reference standards calibrated by a NATA/NABL-accredited calibration laboratory (not just any supplier)
- Working instruments calibrated against those reference standards at defined intervals
- Calibration certificates that include measurement uncertainty
- Records linking each test result to the specific instrument used and its calibration status at the time
The most common gap: the instrument calibration records exist, but there's no link between a test result and the instrument calibration status on the day of testing. An assessor can ask "was this instrument in calibration when this result was produced?" — and the answer requires manual cross-referencing. A LIMS that records instrument ID alongside test data makes this link automatic and verifiable on demand. See our guide on calibration management best practices for more.
2. Sample traceability: from receipt to result
Every sample that enters your laboratory should have a unique identifier that travels with it from receipt to disposal. Sample traceability means being able to answer: where did this sample come from, when was it received, how was it stored, which tests were performed on it, and what were the results?
The breakdown usually happens when samples are logged manually on paper or in a spreadsheet, then results are entered in a separate system without cross-referencing the sample ID. By the time the report is issued, the link between the physical sample and the test result is held together by memory rather than data. Log every sample in your LIMS at receipt with a system-generated unique ID, and ensure physical sample labels (barcode or QR) match that ID throughout.
3. Method traceability: which version was used?
Test methods and acceptance criteria change. When a result is produced, the report should specify exactly which revision of the test method was followed — not just the method number. This matters for two reasons: it proves compliance at the time of testing, and it ensures the acceptance criteria applied were the correct ones for that revision.
In spreadsheet-based labs, "AS 1170.1" appears on the report, but there's no record of which revision, or whether the technician used the current procedure or one printed six months ago. Link test entries to version-controlled method documents in your LIMS so the method revision is recorded at the point of data entry, not added manually to the report later.
4. Operator traceability: who did what, and when?
ISO/IEC 17025 requires that the laboratory can identify who performed each test and who reviewed and authorised the report. This is the audit trail requirement — and it's one that paper-based labs consistently struggle to produce comprehensively.
Digital systems create this record automatically. Every data entry, every status change, every review action is timestamped and attributed to the logged-in user. The audit trail is built as a by-product of normal operation — not assembled manually before an assessment. Use role-based user accounts and avoid shared logins, which destroy the audit trail entirely.
5. Report traceability: issued, amended, superseded
Once a report is issued, it should be immutable unless formally amended through a documented process. A new version should be issued with a clearly marked amendment reason, and the original version should be archived — not overwritten. Clients who have the original should be notified of the amendment.
This is one of the most common ISO 17025 assessment findings: a report was corrected, the new version was emailed to the client, but there's no record of the amendment reason, no version history, and no evidence the client received the updated report. Implement formal report amendment workflows in your LIMS — version numbering, amendment reason fields, reissue notifications, and archiving of all previous versions.
End-to-End Traceability in Practice
When all five elements are connected in a single system, traceability becomes automatic rather than manual. A NATA or NABL assessor asking "show me the traceability chain for this result" gets an immediate answer — not a thirty-minute exercise in cross-referencing spreadsheets, filing cabinets, and email threads.
That's the practical value of a purpose-built LIMS over a collection of disconnected tools: the connections are built into the system, not dependent on individual discipline.
Build End-to-End Traceability with OMS
OMS LIMS connects sample records, instrument calibration, test data, method versions, and issued reports in a single audit-ready platform. Book a demo to see how it works for your lab.
Book a Free DemoFrequently Asked Questions
- What is end-to-end traceability in a testing laboratory?
- End-to-end traceability means every test result can be followed through the complete chain: the sample it came from, the method and revision used, the instrument that produced the measurement, the calibration status of that instrument at the time of testing, and the operator who performed and authorised the test. Every link must be documented and connected.
- What is the difference between metrological traceability and sample traceability?
- Metrological traceability refers to the chain of calibrations linking a measurement result to national or international measurement standards — ensuring the measurement itself is valid. Sample traceability tracks the physical specimen from receipt to disposal, recording which tests were performed on it, under what conditions, and what results were produced.
- Why do most laboratories have only partial traceability?
- Partial traceability is common because instrument calibration records, test data, and issued reports typically exist in separate systems — spreadsheets, shared drives, or standalone software — with no automatic link between them. Full traceability requires all five elements to be recorded in a single connected system where the links are created automatically as part of normal operation.
- Which ISO/IEC 17025 clauses address traceability requirements?
- Metrological traceability is addressed in Clause 6.4 (Equipment). Sample handling and technical records requirements sit in Clauses 7.4 and 7.5. Operator traceability and audit trail requirements are covered under Clause 7.5 (Technical Records). Report traceability, version control, and amendment records fall under Clause 7.8 (Reporting Results).
- How does a LIMS improve laboratory traceability compared to spreadsheets?
- A purpose-built LIMS creates traceability links automatically as part of normal operation — the instrument used is recorded against the test entry, the method revision is captured at data entry, the operator is identified by login, and reports are version-controlled with complete amendment history. In a spreadsheet environment, these links must be created and maintained manually and are regularly incomplete under audit review.