ISO 17025 documentation: the documents and records an ISO/IEC 17025 laboratory needs

What ISO 17025 documentation covers

Put simply, ISO/IEC 17025:2017 expects a laboratory to write down how it works where that matters for valid results, and to keep records proving that each reported result was produced competently. That splits into the management system (policies, procedures, control of documents and records, risks, corrective action, internal audit, management review) and the technical evidence: competence and authorisation of staff, equipment and calibration, traceability, method verification or validation, measurement uncertainty, quality control, proficiency testing and the reports themselves.

The requirement behind each item is explained in ISO/IEC 17025 requirements explained; this page stays with the documents and records.

Documents and records in a laboratory

A document tells people what to do and changes when the practice changes: the scope of laboratory activities, a test method, a calibration procedure, a sampling plan, the decision rule agreed with a customer. Superseded versions are withdrawn from use, and a copy is usually kept so that old results can still be explained.

A record shows what happened and must not change afterwards: a balance check on a given morning, the raw readings of a test, a staff authorisation, a proficiency testing score and the action taken on it. The standard gives these two kinds of documented information separate clause titles in its Option A list, "Control of management system documents" and "Control of records", and adds a separate clause, "Technical records", for the evidence behind each test or calibration.

An assessor reads your documents to see what you intend, then samples records to see whether the laboratory works that way.

What ISO/IEC 17025 requires, area by area

Clause titles below are the standard's own; the entries are typical laboratory practice, so read the exact wording of each requirement in the standard itself.

Option B changes the last row only. A laboratory that runs a management system meeting ISO 9001 and able to support clauses 4 to 7 is treated as meeting at least the intent of the clause 8 items, so its existing procedures for documents, records, audits and reviews can stay. Every row above clause 8 still applies in full.

Technical records: the evidence behind every result

"Technical records" is the clause most laboratories underestimate. The test the assessor applies is simple: take one issued report and follow it back. Who did the work, and were they authorised for that method? Which instrument was used, and was it in calibration? What were the raw observations, calculations and conditions? If a link is missing, the result cannot be reconstructed.

Four habits help:

• Record at the time. Observations go down when made, not transcribed later.
• Correct visibly. A change to a record keeps the original readable and shows who changed it, when and why; in software, the audit trail does this.
• Identify everything. Each record links to the item, the method version, the equipment and the person, so a single report can be traced in minutes.
• Control the spreadsheets. A calculation sheet in use should be checked, protected and version-controlled like any other tool.

For the three largest evidence files, see Method verification and validation under ISO/IEC 17025, Measurement uncertainty under ISO/IEC 17025 and Proficiency testing and interlaboratory comparison under ISO/IEC 17025.

A minimal document set for a small laboratory

A single-site laboratory with a few methods and staff rarely needs more than this:

• A short management system document: the scope of laboratory activities, the organisation and responsibilities, the impartiality and confidentiality commitments, and which management system option applies.
• Procedures for contract review, handling of items, control of documents and records, complaints, nonconforming work, corrective action, internal audit and management review; several can share one document.
• A method file for each test or calibration in scope, holding the method or its reference, the verification or validation, the uncertainty evaluation and the quality control arrangements.
• Registers kept current: equipment and calibration, staff competence and authorisations, approved suppliers, and the proficiency testing plan.
• Report templates carrying every element the reporting clause requires for test reports or calibration certificates.

What a small laboratory cannot shrink is the evidence per method. Two people can share every procedure; they cannot share one uncertainty budget across unrelated methods. The ISO/IEC 17025 for small laboratories guide covers the wider question of staffing and effort.

What to avoid

Procedures nobody follows

A procedure describing an ideal the analysts never practise is worse than none: the first record sampled will contradict it. Write it from the bench, with the people who do the work.

Copied manuals and template packs

A purchased manual arrives with another laboratory's methods, roles and equipment, and makes commitments your laboratory then fails to keep.

A thick management system and thin technical files

Laboratories moving from ISO 9001 often polish the policies and neglect the method files, yet technical assessors witness tests or calibrations and then ask for the evidence behind them.

How Effivity holds ISO/IEC 17025 documentation

Effivity is management system software. For a laboratory it holds controlled documents, competence and training records, the equipment and calibration register, supplier evaluations, risks, complaints, nonconforming work, corrective actions, internal audits and management reviews.

Measurement data stays where it is generated, in your instruments, laboratory information system or controlled worksheets; Effivity links to those technical records or holds them as attachments. The Effivity for ISO/IEC 17025 guide shows how the modules map to the standard.

ISO 17025 documentation: questions buyers ask