ISO 17025 for small laboratories: a right-sized ISO/IEC 17025 system

What ISO 17025 asks of a laboratory with a handful of staff

Exactly what it asks of everyone else. Clause 1 of ISO/IEC 17025:2017 states that the standard applies to all organisations performing laboratory activities, regardless of the number of personnel, so there is no reduced version and no exemption for being small.

What changes with size is how the requirements are met. Clause 5 assigns responsibilities, not job titles or departments: a legal entity, a defined range of laboratory activities and management with authority and resources. Clause 4's impartiality risks, in a small laboratory, usually mean ownership, a dominant customer and the same few people testing, reviewing and signing.

Clauses 6 and 7 do not get lighter. They work method by method: each test or calibration on your application needs authorised staff, traceable equipment, a verified or validated method, evaluated uncertainty and a way to show results stay valid. That is where a small laboratory's effort goes, so a tight scope saves more than any paperwork cut. ISO/IEC 17025 requirements explained, clause by clause walks through every clause.

What a small laboratory can combine or keep simple

Clause 8 offers two routes. Option A lists what the management system must address at minimum: documentation, document control, records, risks and opportunities, improvement, corrective action, internal audits and management reviews. Option B lets a laboratory already running a management system that meets ISO 9001 rely on it for those items. Small independent laboratories usually take Option A; an in-house laboratory in an ISO 9001 certified company often takes Option B. The right-hand column is common practice, not requirement.

No clause requires a quality manual or a quota of procedures; ISO/IEC 17025 documentation: what you need lists the documents and records in full.

Roles, people and time in a small laboratory

Four roles, often held by fewer people:

• Owner or manager: decides the scope, provides resources, owns impartiality and chairs the management review.
• Technical lead: answers for methods, validation, uncertainty and the technical content of reports.
• Quality lead: keeps the management system, the logs and the audit programme. Often the same person as the technical lead, which works if another person reviews the system.
• Analysts or calibration technicians: perform the methods and keep the technical records. Each needs recorded training, a competence check and a written authorisation per method.

Size shortens the writing, not the calendar. Methods must be verified or validated before records mean anything, proficiency testing runs on the provider's dates, and the body needs time to review, schedule and close findings, so six to twelve months stays typical; ISO/IEC 17025 timeline: how long accreditation takes, stage by stage breaks the stages down.

What the assessment looks like for a narrow scope

The route is the same as for a large laboratory: application and document review, an optional pre-assessment, an on-site assessment with witnessing by a lead assessor and technical assessors, findings closed by the body's deadline, a committee decision, then surveillance and reassessment.

Scope sets the breadth of the visit. Technical assessors are matched to the tests or calibrations applied for, so three methods mean less to witness than thirty. It is not a softer assessment: in a small team one person may face questions on impartiality in the morning and uncertainty in the afternoon, each answered from a record. The ISO/IEC 17025 assessment: document review, on-site assessment and witnessing covers each step, and ISO/IEC 17025 scope of accreditation: fixed, flexible and how to write it explains how to word the scope itself.

Five mistakes small laboratories make

• One authorised person per method. If that analyst leaves, the method cannot run as accredited work. Train and authorise a second person for every method you can, and record it.
• Buying a template manual. A generic pack describes departments and forms you do not have, and assessors test what you wrote. Write short procedures with the people who do the work.
• Applying for everything at once. Each method adds validation, uncertainty, proficiency testing and witnessing. Start with what customers or regulators require.
• The quality lead auditing their own system. Cross-audit with a second trained colleague, or bring in an external auditor for the areas you run.
• Neglecting technical records. Tidy procedures, results in personal notebooks. Assessors rebuild a result from raw data to report, so data control deserves more care than the procedures.

Worked example: a right-sized system for a five-person calibration laboratory

An illustrative case: an owner who also sells, a senior technician, two calibration technicians and an administrator. The laboratory applies for pressure and temperature calibrations at its premises, the disciplines customers ask about, and leaves on-site work for later.

Nobody here has "quality" in a job title. The heavy lifting sits in the method files and traceability; Measurement uncertainty under ISO/IEC 17025: a budget you can defend and Proficiency testing and interlaboratory comparison under ISO/IEC 17025 cover those in depth.

ISO 17025 for small laboratories: questions buyers ask