ISO/IEC 17025 clause 7.7: monitor whether laboratory results remain valid
Clause 7.7 requires planned and reviewed monitoring of result validity and laboratory performance. It combines internal monitoring under clause 7.7.1, comparison with other laboratories where available and appropriate under clause 7.7.2, and analysis and action under clause 7.7.3. Data collection is only the beginning of the control.
What clause 7.7 requires in practice
Clause 7.7 expects the laboratory to keep watching its own results, not just produce them. It has three working parts. Internal monitoring requires a procedure, planned and reviewed, with data recorded so trends can be seen and statistical review used where practicable. Monitoring against other laboratories, where available and appropriate, requires planned and reviewed participation in proficiency testing, other interlaboratory comparisons, or both. Finally, the data are analysed and used to control and, where relevant, improve the work.
If results fall outside criteria set in advance, the laboratory takes suitable action to prevent incorrect results from being reported. The outputs are a monitoring plan, the recorded data, review records and evidence of action taken. The standard lists many possible techniques but leaves the selection to the laboratory, according to its methods and risks.
Design monitoring around what can go wrong
Identify significant sources of variation or error in the activities. Select checks that can reveal those problems, such as suitable control materials, repeated measurements, equipment checks, review of results or other appropriate techniques. The standard lists examples but does not require every technique for every method.
Plan who performs and reviews the monitoring, what criteria apply and how trends will be detected. Use statistical techniques where practicable. A chart that is never examined does not demonstrate effective monitoring, even if every data point has been entered correctly.
Add an external performance perspective
Where available and appropriate, monitor performance by comparison with other laboratories, including proficiency testing or other interlaboratory comparisons. Plan and review this work as part of the laboratory's programme. Check relevant accreditation-body participation policies as well as the standard.
External comparisons and internal controls provide different evidence. A successful proficiency-testing result at one point does not prove that every later job is valid, while good internal repeatability can fail to reveal a shared bias. Choose a combination that fits the scope and technical risks.
Why clause 7.7 matters to the laboratory
Calibrated instruments and validated methods can still drift, and people can still make slips between audits. Monitoring is the early-warning system that finds those changes while there is still time to stop a bad result leaving the building. It also gives a laboratory objective evidence for its own confidence and for customers who want to know how its results compare with peers. Used well, the data show which methods are stable and which need attention, supporting decisions about training, equipment replacement and scope. Used badly, as a folder of charts nobody reads, it gives false comfort and is quickly exposed by any assessor who asks what was done about a trend.
How to implement clause 7.7
Build a monitoring plan around risk, then make sure someone acts on it. Involve technical staff in choosing the checks, because they know where results have gone wrong before.
- Review the methods and equipment and rank them by how much a hidden problem would harm customers.
- For each high-ranking area, choose checks that could actually reveal a fault, mixing internal controls and external comparisons.
- Set criteria in advance for when a value is acceptable, when it needs investigation and when work must stop.
- Assign owners for performing, recording and reviewing each check, and set review meetings where results are discussed.
- Record data in a way that shows trends over time, not isolated pass or fail marks.
- Define the response to out-of-criteria results, including looking back at work done since the last good check.
- Review the whole plan when methods, staff or scope change, and retire checks that no longer address a real risk.
Analyse and act on the evidence
Clause 7.7.3 requires the monitoring data to be analysed and used to control and, where applicable, improve activities. When results fall outside predefined criteria, take appropriate action to prevent incorrect results being reported. Consider significance, affected work and the need for nonconforming-work or corrective-action processes.
Do not redefine acceptance criteria after an unfavourable result simply to avoid action. Equally, investigate technically rather than assuming every warning means all previous results are invalid. The response should follow the evidence and the established risk-based work controls.
Two illustrative monitoring programmes
A materials laboratory combines control-material checks with review of reported results and suitable external comparison. A developing trend prompts investigation before the check breaches a final rejection limit. The programme is used to understand performance, not merely to produce an assessment folder.
A calibration laboratory obtains an unsatisfactory external comparison outcome. It examines the measurement process, uncertainty and relevant historical work, takes justified action and evaluates effectiveness. Repeating the comparison without addressing the possible cause would not demonstrate meaningful control.
Evidence and common mistakes
Retain the required monitoring procedure and recorded data in a form that supports trend detection. Keep the plan, reviews and actions understandable. A particular chart type or software package is not mandated; the arrangement must suit the technical activity.
Avoid monitoring only convenient methods, treating provider certificates as proof of laboratory-wide competence, ignoring adverse trends that remain within a broad limit, and failing to connect monitoring failures with report-release controls. The programme should evolve when scope, methods or performance information changes.
Explore each numbered part
7.7.1 · design useful internal validity checks
Choose internal checks that reveal meaningful changes in laboratory performance and record the data so trends can be detected. This guide explains appropriate monitoring techniques, planning, review and response, with examples showing why repeated numbers or a completed control chart do not prove validity unless the checks address the activity's actual risks.
7.7.2 · use proficiency testing and comparisons
Plan and review external comparisons that provide meaningful evidence of laboratory performance. This guide distinguishes proficiency testing from other interlaboratory comparisons, explains the available-and-appropriate condition and connects outcomes with investigation and improvement. Examples help laboratories evaluate relevant scope coverage rather than treating participation certificates as proof that every activity is competent.
Frequently asked questions
Must we use every monitoring technique listed in clause 7.7?
No. Select appropriate techniques for the activities, while meeting the requirement for effective planned and reviewed monitoring. The list is not a universal identical checklist.
Does successful proficiency testing replace internal monitoring?
No. External comparison and internal validity monitoring address complementary questions. The laboratory needs a suitable overall programme and must analyse and act on the resulting data.
What should happen when a monitoring result is outside criteria?
Take appropriate action to prevent incorrect results being reported, evaluate the technical significance and apply relevant nonconforming-work or corrective-action controls where needed.
Turn this requirement into reliable laboratory practice
Sterling can help map your monitoring programme to laboratory scope and result risks. Bring the current checks and an example of a difficult outcome to a free consultation to identify useful improvements in planning, review and response.
Build the team's understanding through Method Validation and Verification (ISO/IEC 17025:2017). 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 · Technical process requirements · Internal validity monitoring · External comparisons · Control unsuitable work