ISO/IEC 17025 clause 7.5: make laboratory technical records traceable
Clause 7.5 requires technical records that explain laboratory activities and preserve the history of changes. The record should support understanding of the result and its uncertainty and, where possible, repetition under conditions close to the original. A final report alone rarely contains all that evidence.
What clause 7.5 requires in practice
Clause 7.5 asks that for every laboratory activity there is a technical record that lets a competent person understand what was done and reach, as far as possible, the same result again. The record includes the results and the report, together with enough information to identify factors that influenced the result and its uncertainty. It names who carried out each activity and who checked the data and results, with dates. Original observations, data and calculations are recorded when they are made and tied to the specific task.
The second part concerns change. Amendments to technical records must be traceable back to earlier versions or the original observations; both original and amended data are retained with the date, the aspects that changed and the person responsible. Taken together, the clause expects a trustworthy history, not only a tidy final worksheet.
Connect the task, observations and result
Clause 7.5.1 requires results, the report and sufficient supporting information for the activity. Include dates and the identity of personnel responsible for the activity and for checking data and results. Record original observations, data and calculations when they are made and identify them with the specific task.
Think of a reviewer following one job from its assigned method through raw observations and calculations to release. They should be able to understand relevant influences without asking an analyst to reconstruct the work from memory. The level of detail depends on the activity; the standard does not prescribe one universal worksheet.
Preserve what changes and why the history matters
Clause 7.5.2 requires amendments to be traceable to previous versions or original observations. Both original and amended data and files must be retained, together with the date, the changed aspects and the person responsible. Correcting an error is legitimate; silently replacing the evidence is not.
Distinguish changes to technical records from amendments to an issued report. Both may be needed after an error, but clause 7.8.8 separately controls what happens to the customer's report. Updating the internal calculation does not automatically update or recall an issued result.
Design the record around the method
Identify the information needed to understand the work, including relevant item identity, method version, equipment, conditions and calculations. These details may be linked across controlled systems rather than copied into every form. The links need to remain usable for the retention period.
For electronic records, coordinate with clause 7.11 on functionality, data transfers and protection. For paper records, preserve legibility and traceability when corrections are made. The medium does not change the need for reliable original evidence.
How to implement clause 7.5
Design the record from the point of view of a reviewer who was not there.
- For each method, list what a stranger would need to reconstruct the job: item identity, method version, equipment, conditions, raw observations and calculation.
- Decide where each piece lives, whether on a worksheet, an instrument file or a controlled system, and how they link to the job number.
- Set a rule that entries are made at the time of work, with a practical way to do that at the bench or on site.
- Define how corrections are made on paper and electronically so the original stays visible and the change is attributable.
- Assign individual log-ins for systems that hold technical records and review shared accounts.
- Test the design by asking a colleague to reconstruct a finished job using only its records, and note every question they had to ask.
- Feed the findings back into worksheets, templates and training.
Two illustrative record trails
A calibration laboratory retains the observations, reference information, environmental conditions, calculation version and review identity associated with a certificate. A later reviewer can follow how the result was obtained rather than relying only on the reported value and uncertainty.
A testing laboratory corrects a transcription error before report release. It retains the original entry and records the correction, date and responsible person. If the error had already reached a report, the laboratory would also evaluate the report-amendment and nonconforming-work implications.
Common weaknesses and practical evidence
The technical records themselves are required evidence. A record map or index may help organise them but is not a prescribed ISO format. Check whether raw data are lost when an instrument overwrites memory, whether shared accounts obscure who made a change, and whether calculations refer to files that are later replaced.
Avoid treating retention as a storage-only problem. A folder full of files is of limited value if the task, version and responsible person cannot be identified. Record control under clause 8.4 supports preservation and retrieval; it does not replace the technical content requirements of clause 7.5.
Explore each numbered part
7.5.1 · capture original observations as work happens
Record original observations, data and calculations at the time of the activity and connect them to the specific task. This focused guide explains the detail needed to understand results and uncertainty, identify responsible personnel and support repeatability, with practical examples for instrument exports, worksheets and laboratory calculations.
7.5.2 · preserve the history of record changes
Correct technical records without losing the original evidence or the identity of the person making the change. This guide explains amendment traceability, retention of original and revised data, and the distinction between internal corrections and issued-report amendments. Examples cover paper worksheets and electronic calculations without prescribing one mandatory software system.
Frequently asked questions
Is the final test report enough as a technical record?
Usually it is only part of the record. The laboratory also needs sufficient supporting information, original observations and relevant calculations to explain the activity and result.
Can records be distributed across several systems?
Yes, if the connections remain clear, reliable and retrievable. The laboratory must preserve the evidence and its relationship to the specific task and versions used.
Does correcting a worksheet automatically correct an issued report?
No. Evaluate the effect on the issued result and apply the separate reporting and nonconforming-work controls where relevant, while preserving the technical amendment history.
Turn this requirement into reliable laboratory practice
Sterling can help trace a completed laboratory job through the records and identify gaps before assessment. Bring an anonymised example to a free consultation to focus documentation improvements on technical evidence that matters.
Build the team's understanding through Documented Information Management. Discuss the relevant scope, employee learning and agreed access to Effivity ISO & GRC automation software with Sterling; laboratory technical decisions remain with competent, authorised personnel.
ISO/IEC 17025 requirements hub · Technical process overview · Capture original technical evidence · Preserve record amendments · Retain and protect records