ISO/IEC 17025 clause 5.4: control laboratory work at every location
Clause 5.4 requires laboratory activities to meet ISO/IEC 17025 and the relevant requirements of customers, regulators and organisations providing recognition. That responsibility extends beyond the main laboratory building to work at other sites, temporary or mobile facilities and customer premises.
What clause 5.4 requires in practice
Clause 5.4 sets two linked expectations. Laboratory activities must be carried out in a way that meets the standard itself, the customers' requirements, the requirements of regulators and the requirements of organisations that provide recognition. And that applies everywhere the work happens: permanent facilities, sites away from them, associated temporary or mobile facilities and customer premises.
The clause does not say a laboratory must write a separate management system for each address. It says the requirements must be met wherever work is done. A shared system is fine if it deals properly with what differs at each place, such as conditions, utilities, access, transport and data handling.
Where customer, regulatory and recognition requirements pull in different directions, the laboratory has to resolve the difference through contract review and work control. The output is controlled work at every location, backed by technical records that show it.
Carry the requirements to the work
Begin with where and how each activity is performed. A customer-site calibration may use the same method as work in a permanent laboratory, but transport, environmental conditions, utilities, access and data transfer can differ. Identify those differences before assuming that existing controls remain adequate.
The standard does not prescribe a separate management system for every location. Shared arrangements may be useful if local conditions are genuinely addressed. Equally, a single corporate manual cannot demonstrate that every activity is controlled. Connect the common process with location-specific responsibilities and evidence.
Reconcile different sources of requirements
Contract review should establish the customer's needs and any applicable specifications. Identify regulatory and recognition conditions relevant to the activity and jurisdiction. Where requirements conflict or a requested method is unsuitable, resolve the issue before accepting or continuing the work. Do not assume that a customer's preference overrides technical validity or a regulatory obligation.
For international operations, use a common approach to competence, records and review while checking local obligations and accreditation arrangements. The point is consistent control, not an unsupported claim that one approval automatically covers every country or address.
Why control at every location matters to the business
The moment a laboratory leaves its own premises, many of its usual protections disappear. Temperature may be unstable, power may be poor, security may be weaker and the customer may be standing nearby. If reports from such visits are given the same weight as reports from the main laboratory, any weakness becomes a risk to the customer's decisions.
For businesses that sell mobile or on-site services, this clause is also a selling point when done properly. It shows a prospective client that the quality of work does not depend on the address. Clear control of sites also helps when entering new regions, where local regulations and expectations may differ.
How to implement clause 5.4
Think of the process as a rehearsal of each type of location before the first real job is done there.
- List the types of location where work occurs and the activities performed at each.
- For each type, note what differs from the permanent laboratory: environment, utilities, access, security, transport of equipment and data transfer.
- Check contract review so that customer, regulatory and recognition requirements are identified before a visit is accepted.
- Prepare a short pre-visit review that asks whether staff have current instructions, suitable equipment and a way to escalate unexpected conditions.
- Agree what happens when conditions are unsuitable, including declining the work or recording a limitation, and tell the customer.
- Review technical records from recent off-site work to see whether the controls operated as planned.
- Capture lessons after each unusual location or customer, and feed them back into the pre-visit review so the next visit starts better prepared. Where a visit reveals a new risk, update the procedure and tell the staff who will perform similar work next.
Two illustrative location decisions
A calibration team visits a factory whose production area has vibration and unstable temperature. Before beginning, it checks whether the conditions allow the required measurement performance and uncertainty. If they do not, it agrees an appropriate alternative rather than recording a result simply because the visit was booked.
A construction laboratory opens a temporary project facility. It defines responsibility for equipment, sample storage, environmental monitoring and report authorisation there. It confirms how the facility fits its scope and recognition instead of relying on the permanent laboratory's address and procedures alone.
Evidence and practical checks
Useful evidence connects the requirement to the location: accepted contracts, applicable methods, facility checks, authorised personnel, equipment status and technical records. Clause 5.4 does not create one mandatory “site compliance certificate”. The specific evidence duties arise through the relevant clauses, including facilities, equipment and technical processes.
A pre-deployment review can be helpful. Ask whether staff can access current instructions, preserve records securely and escalate unexpected conditions. Check what happens if a borrowed instrument fails or a customer prevents access to a necessary area. These are suggested controls based on the work, not a substitute for method-specific judgement.
Common nonconformities with clause 5.4
Findings in this area tend to appear when work moves away from the main laboratory.
- Site visits are performed with the permanent laboratory's procedures but no consideration of local conditions.
- Equipment is taken to a customer's premises without checks that it still performs correctly after transport.
- A customer's request to proceed in unsuitable conditions was accepted without technical evaluation.
- Staff on a temporary project facility did not have access to current instructions.
- Records from mobile work do not show who was authorised or what conditions were present.
Frequently asked questions
Can mobile laboratory activities be covered by ISO/IEC 17025?
Yes. The standard expressly addresses activities outside permanent facilities. The laboratory must control the relevant conditions and confirm the scope of any accreditation claim.
Does every site need a different manual?
No. A shared system can work where it addresses the actual activities, responsibilities and local conditions. Separate manuals are not a clause 5.4 requirement.
What if a customer asks us to ignore an unsuitable site condition?
Customer preference does not remove the need for valid work. Evaluate the technical effect, explain the limitation and resolve the issue through the applicable contract and work-control processes.
Turn this requirement into reliable laboratory practice
Planning on-site or cross-border laboratory services? Ask Sterling to review the delivery model, technical interfaces and recognition questions in a free consultation. The preparation can then address the conditions your teams will actually face.
Build the team's understanding through ISO/IEC 17025 Awareness. 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 · Facilities and environmental conditions · Equipment controls