hello@sterling-grc.com +1 201 263 4443 New York ISO & GRC consulting in 60+ countries
SterlingInternational Consulting Talk to a consultantTalk to us
Clause 8.7ISO/IEC 17025:2017 · Make the management system work

ISO/IEC 17025 clause 8.7: correct causes and prevent repeat problems

Clause 8.7 requires the laboratory to react to nonconformity, control and correct it as applicable, address consequences and evaluate the need to eliminate causes. Appropriate action should prevent recurrence or occurrence elsewhere. Corrective action must fit the effects of the problem and include review of effectiveness.

What clause 8.7 requires in practice

Clause 8.7 applies under Option A and sets out what happens when a nonconformity occurs. The laboratory reacts to it and, as applicable, takes action to control and correct it and deals with its consequences. It then evaluates whether action is needed to remove the causes so the problem does not recur or appear elsewhere. That evaluation involves reviewing and analysing the nonconformity, determining its causes and checking whether similar nonconformities exist or could arise.

Any needed action is carried out, and its effectiveness is reviewed. Where necessary, the laboratory updates the risks and opportunities it identified during planning and changes the management system.

Corrective actions are appropriate to the effects of the nonconformities. The laboratory retains records showing the nature of each nonconformity, its causes, the actions taken and the results of corrective action.

The clause separates fixing the immediate problem from preventing its return, and it expects evidence for both.

Distinguish correction from cause removal

Correction addresses the immediate nonconformity, such as amending a report or replacing an unsuitable instruction. Corrective action addresses why the problem happened and whether it could recur or exist elsewhere. Both may be needed, but one should not be presented as proof of the other.

For technical nonconforming work, clause 7.10 governs immediate work and result decisions. Clause 8.7 provides the wider cause-and-effect process under Option A. Use the processes together rather than opening disconnected records with contradictory conclusions.

ISO/IEC 17025 consulting & certification support

Get clause 8.7 right the first time — with a global leader in ISO/IEC 17025 implementation

A Sterling consultant works the requirement through with your team, links it to the rest of the system and carries it to certification readiness. Expert and experienced consultants, 8,100+ client engagements in 60+ countries.

Why corrective action matters to the business

A laboratory that only corrects individual errors will meet the same errors repeatedly, each time at the cost of rework, delayed reports and customer patience. Finding the cause and checking whether it exists elsewhere is how those costs go down.

Corrective action also shows the character of the system. Assessors and customers pay attention to whether a laboratory explains why something went wrong, rather than blaming a person and moving on. Well-handled corrective action builds confidence after an incident, and its records give management real information about where the system is weak, which feeds improvement, risk review and resource decisions.

Investigate causes with evidence

What counts as evidence

Review and analyse the nonconformity, determine causes and examine whether similar problems exist or could occur elsewhere. Consider the workflow, responsibilities, competence, information and controls. “Human error” may describe what happened without explaining why the system allowed it.

The standard does not mandate a specific technique such as five whys or a fishbone diagram. Use a method that produces a credible explanation supported by evidence. Avoid selecting retraining automatically when the actual cause is an unclear interface, defective calculation or unavailable instruction.

Implement and test the action

Take the necessary action and review its effectiveness. Define what evidence would demonstrate that the cause has been addressed, considering the type and frequency of the activity. The absence of a repeat incident over an irrelevant short period may prove little.

Update risks and opportunities where necessary and change the management system where needed. An effective local fix may need to be applied to related methods, sites or systems if the same cause exists there. Proportionality means matching the response to the effects, not minimising work regardless of risk.

Common nonconformities with clause 8.7

Corrective action records are among the first items an assessor opens, and weaknesses show up quickly.

  • Records describe the correction, such as a reissued report, but never state the cause or whether similar problems exist elsewhere.
  • The recorded cause is simply operator error, and retraining is the sole action, with no look at instructions, tools or workload.
  • Effectiveness is declared in the same entry that closes the action, with no later check that the problem stayed away.
  • Actions in the corrective action log and in nonconforming work records give different conclusions, and risks or the system are never updated.

Two illustrative corrective actions

Illustrative example 1

A testing laboratory repeatedly issues reports with an incorrect unit. Investigation finds an uncontrolled interface mapping rather than a lack of analyst awareness. The laboratory corrects affected work, controls the mapping and verifies the reporting path using appropriate test cases, instead of closing the issue after a reminder email.

Illustrative example 2

A calibration laboratory finds recurrent overdue equipment checks. It examines ownership, scheduling and absence cover, then changes the process and evaluates whether checks are completed reliably. Moving all dates forward would conceal the problem without removing its cause.

Automate™ on Effivity · included in every Sterling engagement

Keep clause 8.7 alive in Effivity

Record what you decided under clause 8.7, link it to the records and controls it affects, and let the review date trigger the next look. Effivity is the ISO & GRC software used in 50+ countries — and part of every Sterling ISO/IEC 17025 programme.

Retain evidence that explains the decision

Clause 8.7.3 requires records of the nonconformity, causes, subsequent actions and corrective-action results. The record should explain why the chosen action fits the cause and how effectiveness was assessed. A particular form or severity scale is optional unless required through another applicable arrangement.

Avoid unsupported root-cause labels, closure based only on training attendance, failure to examine similar work and effectiveness checks performed before the action has operated meaningfully. Corrective action is complete when the evidence supports the conclusion, not simply when a due date arrives.

Frequently asked questions

Is retraining always an acceptable corrective action?

Only if it addresses an established cause and its effectiveness is evaluated. Training attendance alone does not prove that the underlying problem has been removed.

Does ISO/IEC 17025 require one root-cause method?

No. The laboratory must determine causes and relevant similar risks, but it can use a suitable evidence-based technique rather than one prescribed diagram or questionnaire.

Must we check other methods or sites after a problem?

Evaluate whether similar nonconformities exist or could occur elsewhere. The extent should follow the cause and potential effects, not an automatic assumption that the issue is isolated.

Turn this requirement into reliable laboratory practice

Sterling can help review a recurring laboratory issue and strengthen the connection between evidence, causes and effective action. Bring an anonymised example to a free consultation to identify useful process and learning improvements.

Build the team's understanding through Nonconformity 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 · Management-system overview · Nonconforming work · Risks and opportunities · Management review

Source basis and reading note. This is original practical guidance for ISO/IEC 17025:2017. Use an authorised copy for definitive requirements. Illustrative examples describe hypothetical situations, not client results. Implementation methods are distinguished from requirements; independent bodies decide accreditation for a defined laboratory scope outcomes. Issuer standard record: iso.org.
Disclaimer. This guide is provided for general information only. It is not the text of the standard, not legal or professional advice, and not a representation of how any certification body will assess your organisation. Sterling International Consulting accepts no liability for any loss arising from reliance on it. Requirements are applied to each organisation's own context through an engagement; contact us to implement ISO/IEC 17025 in your organisation.