ISO/IEC 17025 clause 5: define laboratory responsibility and scope
Clause 5 establishes who is responsible for the laboratory, what work it claims to perform in conformity with ISO/IEC 17025, and how responsibilities operate. Its numbered paragraphs, 5.1–5.7, should be read together. An organisation chart helps explain the structure, but it does not by itself demonstrate that people have the authority and resources to protect valid results.
What clause 5 requires in practice
Clause 5 has seven short provisions that together answer who the laboratory is, who runs it, what it claims and how its structure holds up in practice. The laboratory must be a legal entity in its own right, or a clearly bounded part of one (5.1). Management with overall responsibility is identified (5.2). The range of activities for which conformity is claimed is defined and documented, and claims stay within it; activities supplied externally on a continuing basis fall outside that range (5.3).
Work is carried out so that it meets the standard and the needs of customers, regulators and recognising organisations, wherever it takes place, including temporary, mobile and customer premises (5.4). The structure and relationships are defined, responsibilities of people affecting results are specified, and procedures are documented as far as needed (5.5). Personnel hold the authority and resources to run and improve the system and to act on deviations (5.6). Management ensures communication and protects system integrity during change (5.7).
Outputs are a defined entity, named accountable management, a documented range, and responsibilities that work in real jobs.
5.1–5.3: identify accountability and the claimed activities
The laboratory must be a legal entity or a defined part of one, with legal responsibility for its laboratory work. It must identify the management carrying overall responsibility and document the range of activities for which it claims conformity. This requires precision about the laboratory, not simply the parent group's brand.
The claimed range excludes laboratory activities that are externally provided on an ongoing basis. External services can still have a legitimate place in operations, but their use needs appropriate control and communication. Do not describe an external provider's continuing work as though it were the laboratory's own demonstrated capability.
5.4–5.5: make the structure work wherever activities occur
The laboratory's responsibilities extend to relevant permanent, temporary, mobile and customer-site activities. Customer and applicable regulatory or recognition requirements need to be considered alongside the standard. Moving the work off-site does not remove the need to control it.
Define the laboratory's position within its parent organisation where relevant, the relationship between technical and support functions, and the responsibilities of people who manage, perform or verify work affecting results. Document procedures to the extent needed for consistent application and valid outcomes. A complicated hierarchy is not the objective; clear operational responsibility is.
Sterling's suggested implementation approach
Compare three descriptions of the laboratory: what the business advertises, what its proposed accreditation scope says and what technical staff can demonstrate. Resolve differences early. A website might describe broad testing capabilities while the initial scope covers only selected methods. These statements need to coexist without misleading customers.
Then follow a job through decision points. Identify who accepts unusual work, approves method changes, stops unsuitable activity, releases reports and resumes work after a problem. Check deputies and escalation arrangements. Where one person holds several roles, examine whether the combination remains workable and protects impartiality.
Finally, review dependencies on parent-company functions. Procurement, IT, finance and HR can affect the laboratory's results even when their managers sit outside its reporting line. Agree how technical acceptance, competence needs and information controls are respected. These are recommended implementation checks, not required document titles.
Why laboratory structure matters to the business
Structure is where trust is either built or lost before any technical work starts. Customers and accreditation bodies want to know who is answerable, what exactly is on offer and whether the arrangement still works at the customer's site, in a second city or when a manager is away.
A vague structure produces expensive surprises: advertising that outruns the recognised range, staff who cannot stop a doubtful job, a branch that works on borrowed authority, or a change in software that nobody evaluated. Settling these questions early also shortens preparation for assessment, because later clauses on resources, methods and reporting have a clear owner to attach to.
How to implement clause 5
Treat clause 5 as a working picture of the laboratory that the people inside it would recognise. Build it from real jobs rather than from an organisation chart alone.
- Confirm the legal entity and write down how trading names and group brands relate to it.
- Name the management with overall responsibility and the deputies for absence.
- Compare three descriptions of the work: marketing wording, the proposed accreditation range and what technical staff can demonstrate, then resolve differences.
- Follow one job through every site and facility, noting who decides on unusual work, stops it, releases the report and restarts after a problem.
- Check dependencies on parent-company functions such as purchasing, IT and HR, and agree how technical needs are respected.
- Test authority with realistic scenarios, then plan how changes to people, sites or systems will be communicated and controlled.
- Keep the picture current by naming an owner and by checking it after any acquisition, move, reorganisation or change in recognition conditions.
Illustrative example: a second laboratory location
A calibration business opens a branch closer to customers. The parent company assumes the branch can use the same approval list as the original site. The branch manager, however, has no documented authority to stop work when the required reference equipment is unavailable.
A useful response is to define the branch activities and responsibilities, verify the supporting resources and agree how technical concerns reach accountable management. The reporting relationship should support a real decision, such as delaying a job or approving a suitable alternative, rather than leave staff responsible for outcomes they cannot control. This is an invented teaching example, not a claim about a client.
Evidence to review before assessment
Relevant evidence includes the responsible entity, documented activity range, management assignments, responsibilities, necessary procedures and records showing that concerns reach people with authority to act. Assessors may compare the stated structure with staff explanations and work performed at different locations.
Watch for a mismatch between assigned duties and actual permissions. Someone may be named as responsible for quality but lack access to records, a route to management or authority to raise a deviation. Conversely, commercial staff may be authorising technical commitments that the documented structure reserves for qualified personnel.
Explore each numbered part
5.1 · legal responsibility for laboratory work
Identify the legal entity responsible for laboratory activities, including laboratories within manufacturing groups, universities or other parent organisations. This guide explains what clause 5.1 establishes, how to connect trading names and operational responsibilities, and why legal identity alone does not demonstrate technical competence or an accredited scope.
5.2 · identify accountable laboratory management
Make overall responsibility for the laboratory clear without relying on an impressive job title or an ambiguous organisation chart. This guide explains clause 5.2, its relationship with delegated technical authority, and practical ways to establish accountable management in small laboratories, manufacturing groups and organisations with several locations.
5.3 · define and control the laboratory scope
Define the laboratory activities for which your organisation claims conformity, and distinguish that range from its commercial service catalogue and accredited scope. This guide explains ongoing external provision, useful scope boundaries and practical checks that prevent unsupported claims when methods, locations, customers or services change over time.
5.4 · control laboratory work at every location
Apply laboratory requirements consistently at permanent premises, temporary or mobile facilities and customer sites. This guide connects ISO/IEC 17025 clause 5.4 with customer, regulatory and recognition requirements, using practical examples to show why an approved head-office procedure alone does not control the conditions where work actually occurs.
5.5 · connect laboratory roles and procedures
Clarify how laboratory management, technical operations and support functions work together. This guide explains the three parts of clause 5.5: organisational relationships, responsibilities affecting results and sufficient documented procedures. Examples show how to prevent gaps at handovers without creating a document for every minor task or unnecessary layers of approval.
5.6 · give staff authority to address deviations
Ensure the people maintaining the laboratory system have authority and resources to act when work departs from requirements. This guide explains the duties in clause 5.6, including identifying deviations, initiating action, reporting system performance and supporting effective activities, with examples that distinguish practical authority from a title on paper.
5.7 · communicate and protect planned changes
Keep laboratory personnel informed about system effectiveness and the importance of meeting requirements, while protecting the system when changes are planned and introduced. This guide explains both parts of clause 5.7 with examples involving laboratory relocation and reporting software, and shows how to avoid communication that stops at sending an email.
Common nonconformities with clause 5
Assessors usually find clause 5 weaknesses by comparing what is written with what people say and do.
- Marketing material claims accreditation for services outside the documented range.
- Overall responsibility is described in several places with different names.
- A site away from the main laboratory works without defined responsibilities or controlled instructions.
- The person named for system maintenance has no access to records or no route to management.
- A change of premises or software went live without any evaluation of its effect on the system.
Frequently asked questions
Does a small laboratory need many separate management positions?
The standard does not prescribe a large departmental structure. Responsibilities still need to be defined, resourced and effective. Combining roles should not conceal conflicts, unavailable deputies or decisions that nobody is empowered to make.
Can an internal laboratory belong to a manufacturing company?
Yes, a laboratory may be a defined part of a legal entity. Its responsibilities and impartiality safeguards need to work within that setting. Ownership alone does not demonstrate or disprove competence.
Can we claim accreditation for everything in our brochure?
Only make accreditation claims consistent with the scope granted by the accreditation body. The laboratory's capability description, conformity range and accredited scope need clear distinctions.
Define a scope your laboratory can demonstrate
For ISO/IEC 17025 accreditation support, Sterling can help connect proposed scope, responsibilities and implementation priorities. Discuss your laboratory structure and locations with a consultant. The Academy awareness course can give managers and staff a common starting point for that work.
All ISO/IEC 17025 clauses · Previous clause · Next clause
For an agreed consulting and documentation work programme, Effivity ISO & GRC automation software can help organise responsibilities, evidence and follow-up alongside employee learning. Sterling coordinates the work with your laboratory team across relevant locations; software and training support the system without replacing competent technical decisions.