ISO/IEC 17025 clause 5.5: connect laboratory roles and procedures
Clause 5.5 requires a defined laboratory structure, clear responsibilities and relationships for people whose work affects results, and procedures documented sufficiently to support consistent activities and valid results. An organisation chart is useful only if it explains the decisions and interfaces that matter in practice.
What clause 5.5 requires in practice
Clause 5.5 contains three requirements, labelled a, b and c. The first asks the laboratory to define its organisation and management structure, its place within any parent organisation, and the relationships among management, technical operations and support services.
The second asks it to specify the responsibility, authority and interrelationship of everyone who manages, performs or verifies work that affects results. The third asks it to document procedures as far as necessary for consistent laboratory activities and valid results.
The key words are as far as necessary. The standard does not ask for a written procedure for every action and does not prescribe a chart or matrix. It asks that structure and responsibilities be clear enough for people to act correctly and that written instructions exist where a lack of them would allow inconsistency.
The outputs are a defined structure, clear responsibilities including interfaces with support functions, and procedures proportionate to risk and complexity.
Map management, technical work and support
Identify the laboratory's place within any parent organisation and the relationship between management, technical operations and support services. Include functions such as purchasing, IT and maintenance where they can affect the work. Their personnel may sit outside the laboratory's reporting line while still influencing equipment suitability, data integrity or supplier selection.
Clarify who manages, performs and verifies work affecting results. Distinguish responsibility for a task from authority to make a decision. For example, receiving an instrument, accepting its calibration evidence and authorising its use may involve different responsibilities. The arrangement should prevent both gaps and contradictory instructions.
Document what consistency requires
Clause 5.5 does not require a separate procedure for every movement or administrative action. Determine the documentation necessary for consistent laboratory activity and valid results. Existing methods, controlled work instructions and defined interfaces can contribute, provided people can access and apply them.
Pay attention to handovers that staff otherwise manage from memory. Examples include the transfer from sample receipt to testing, the release of repaired equipment and the review of a changed calculation. Document enough to make responsibilities and decision criteria clear; avoid replacing technical judgement with a long checklist that nobody understands.
Why defined roles and procedures matters to the business
Most laboratory errors do not happen inside a single person's task. They happen at the handover: between receiving a sample and testing it, between repairing an instrument and using it, or between changing a calculation and issuing a report. A structure that makes those handovers explicit removes the gaps where mistakes hide.
Proportionate documentation matters commercially. A laboratory that writes too much loses time and gets staff who ignore procedures; one that writes too little struggles to train people or defend its decisions. Getting the balance right makes onboarding faster and assessments smoother.
How to implement clause 5.5
Pick one complete job and use it to test the structure. The picture that emerges is usually more useful than a theoretical chart.
- Draw the structure showing the laboratory, any parent organisation and the support functions that influence work, such as purchasing, IT and maintenance.
- For each step of the chosen job, name who performs it, who verifies it and who has authority to decide when something is not routine.
- Highlight each handover and ask whether the receiving person has what they need to proceed.
- Decide which activities need written instructions by looking at complexity, risk and competence, rather than copying a template.
- Check that documents are accessible to those who use them and that they match what people actually do.
- Walk through the job with the people involved and correct any differences between description and practice.
- Review the structure and key procedures whenever a method, supplier or reporting route changes, since interfaces often move without anybody noticing.
Two illustrative interfaces
A manufacturer's central purchasing team selects a cheaper calibration supplier. The laboratory defines who specifies the required range, uncertainty and recognition, who evaluates the supplier and who accepts the delivered evidence. Purchasing authority does not automatically include technical authority to judge suitability.
A testing laboratory uses external IT support for its reporting system. It establishes who proposes changes, who checks technical calculations and who authorises release. The IT provider's successful installation is not treated as laboratory acceptance of the changed result-processing function.
Evidence and useful review questions
The required structure and responsibilities can be expressed through role descriptions, process descriptions and other controlled records. Procedures need to be documented to the necessary extent. A responsibility matrix is an optional tool, not a compulsory ISO form.
Walk one job through the system with the people involved. Ask who acts when information is incomplete, a method changes or equipment is unavailable. Compare their answers with documented arrangements. Differences often reveal a more important weakness than the visual quality of the organisation chart.
Avoid assigning all quality matters to one coordinator while leaving technical managers unaware of their responsibilities. Also avoid excessive approval layers that delay action without adding competent review. The goal is reliable decisions and valid results, with clear accountability for the work.
Common nonconformities with clause 5.5
Clause 5.5 problems often show up when assessors follow a job through several hands.
- Support functions such as purchasing or IT influence results but have no defined responsibilities for the laboratory.
- Documented responsibilities do not match what staff say they do.
- Procedures exist for administrative steps but key technical handovers rely on memory.
- Several approvals are required for routine actions without adding any technical review.
- All quality responsibility is assigned to a single coordinator and technical managers are unaware of their duties.
Frequently asked questions
Does ISO/IEC 17025 require a specific organisation-chart format?
No. The laboratory must define its structure and relevant relationships. Choose a clear form that staff and assessors can connect to actual operations.
Must every task have a separate written procedure?
No. Procedures are documented to the extent necessary for consistent activities and valid results. Consider complexity, risk, competence and the need for reliable handovers.
Do support functions outside the laboratory need defined responsibilities?
Yes, where their work affects laboratory results or relevant activities. A different reporting line does not remove the need to control the interface.
Turn this requirement into reliable laboratory practice
Sterling can help map one complete laboratory job and identify unclear decisions between technical and support teams. Bring an actual workflow to a free consultation so documentation work improves the handovers that matter.
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 · Structural requirements · Personnel competence · Validate laboratory software changes