If you are preparing a testing or calibration laboratory for accreditation, one of the first questions is: what do we actually have to write down? ISO/IEC 17025:2017 does not provide a neat list of mandatory documents. It describes requirements for competence, impartiality and consistent operation, and leaves you to decide how much documentation shows that you meet them.
This article breaks the documentation down into practical groups, so you can plan your document set and avoid both gaps and excess paperwork.
How ISO 17025 approaches documentation#
The standard is organised into clauses 4 to 8: general requirements, structural requirements, resource requirements, process requirements and management system requirements. Documentation requirements are spread across all of them. Some say that something must be documented. Others require records that prove an activity took place. Others imply documentation because you cannot demonstrate competence without it.
In practice, a lab's documents fall into four groups:
- Policies and objectives: what the lab commits to.
- Procedures and methods: how work is done consistently.
- Forms, templates and checklists: the tools staff use to carry out the procedures.
- Records: evidence that the work was done and the results are valid.
Your accreditation body may also have its own expectations about scope and documentation, so check these early.
Documents for general and structural requirements (clauses 4 and 5)#
These clauses cover impartiality, confidentiality and the lab's legal and organisational structure. Expect to have:
- Impartiality policy and risk assessment: a commitment from management, plus an ongoing identification of risks to impartiality and how you handle them.
- Confidentiality policy or procedure: how client information is protected, and when and how it may be released.
- Scope of laboratory activities: a clear statement of the tests, calibrations and locations covered.
- Organisation chart and role descriptions: who is responsible for what, including who has authority over technical operations and the management system.
- Legal entity evidence: proof that the lab is, or is part of, an entity that can be held legally responsible.
Documents for resource requirements (clause 6)#
This is where much of the technical credibility is built. Assessors typically look closely at people, equipment and traceability.
Personnel#
- Competence requirements for each function
- Procedure for authorising staff to perform specific activities
- Training plans and training records
- Competence evaluation and monitoring records
Facilities and environment#
- Procedure for controlling environmental conditions that affect results
- Environmental monitoring records where relevant
- Rules for access to and use of areas, and for preventing contamination or interference
Equipment and metrological traceability#
- Equipment register with identification and status
- Procedure for handling, maintenance, calibration and verification
- Calibration plans, certificates and intermediate check records
- Procedure and records showing how measurement results are traceable to the SI or other accepted references
Externally provided products and services#
- Procedure for selecting, evaluating and monitoring suppliers and subcontracted calibration or testing
- Approved supplier list and evaluation records
Documents for process requirements (clause 7)#
This clause covers the work itself, from receiving a request to issuing a report. It is usually the largest part of a lab's document set.
| Process step | Typical documents |
|---|---|
| Requests, tenders and contracts | Contract review procedure, review records, statement of conformity and decision rule where applicable |
| Methods | Method selection procedure, test or calibration methods, verification and validation records |
| Sampling | Sampling plan and method, sampling records, where the lab does sampling |
| Handling test items | Procedure for receipt, identification, storage, protection and disposal of items |
| Technical records | Worksheets, raw data, calculations, with enough detail to repeat the activity |
| Measurement uncertainty | Uncertainty evaluation procedure and uncertainty budgets |
| Validity of results | Quality control plan, proficiency testing or interlaboratory comparison records, trend data |
| Reporting | Report templates, calibration certificate templates, amendment procedure |
| Complaints | Complaints procedure and complaint log |
| Nonconforming work | Procedure for handling it, including when to stop work and recall results |
| Data and information management | Validation records for software and spreadsheets, access controls, backup arrangements |
Two points are often missed. First, spreadsheets and software used to calculate results need to be validated and controlled. Second, technical records must let someone else reproduce the activity, so a bare final result is not enough.
Documents for the management system (clause 8)#
The standard lets you choose between two options for the management system: Option A, where you set up the required elements directly, and Option B, where you operate a management system that already meets ISO 9001 and covers the same intent. Either way, you will need a set of core management system documents:
- Management system policies and objectives: competence, impartiality and consistent operation.
- Document control procedure: approval, review, issue, change control and obsolete documents.
- Records control procedure: identification, storage, protection, retention and disposal.
- Risks and opportunities procedure and a register of actions taken.
- Improvement and corrective action procedure with records of root cause and effectiveness.
- Internal audit programme, procedure, checklists and reports.
- Management review procedure, agenda, minutes and action tracking.
A separate quality manual is not the point. What matters is that the policies, objectives and procedures are documented, available to staff and actually followed.
A practical way to build your document set#
- Run a gap assessment against each clause to see what already exists. Many labs have good technical methods but weak management system documents.
- Define your scope first, because it drives which methods, equipment and competence records you need.
- Write procedures to match real practice. If a procedure describes something staff do not do, assessors will find the difference.
- Keep it proportionate. A small calibration lab does not need the same volume of paperwork as a multi-site testing group.
- Test it internally. Run an internal audit and a management review before the external assessment, so records exist and weaknesses show up early.
Starting from structured templates can save time, as long as you adapt them to your methods and scope. The ISO 17025:2017 Toolkit provides editable policies, procedures, checklists and worked examples, with a gap assessment checklist, so you are not starting from a blank page. If you work in other regulated areas, our guides on ISO 13485:2016 documents follow a similar approach.
Frequently asked questions#
Does ISO 17025:2017 require a quality manual?#
The standard does not require a document with that title. It does require that your policies, objectives and procedures are documented and accessible to the relevant personnel. Many labs still keep a manual as a convenient way to hold or reference them.
How many procedures does a lab need?#
There is no fixed number. The right set depends on your scope, size and risks. Cover each area of the standard that applies to you, and make sure each procedure reflects how work is actually done. Check your accreditation body's guidance for any additional expectations.
What records do assessors usually want to see?#
Typically they sample technical records, equipment calibration and traceability evidence, staff competence and authorisation records, validation of methods, proficiency testing or comparison results, internal audit reports and management review minutes. Be ready to show that these are complete and consistent with each other.
If you want to see how much of this you already have in place, a gap assessment is a sensible first step, and the ISO 17025:2017 Toolkit includes a checklist for exactly that purpose.
