What it is about
Clause 10.2 describes what happens after a nonconformity. A nonconformity is any requirement that is not met: from the standard, from the customer, from the law or from your own rules. It can come from an audit, a complaint, an incident, a measurement or an observation in the operation.
The procedure has two parts. First you react: control the nonconformity, fix the error and deal with the consequences. That is the correction. Then you decide whether the cause has to be eliminated so that it does not happen again, including elsewhere: review the nonconformity, determine the cause, check whether similar cases exist or could occur. That is the corrective action. It is proportionate to the effects of the nonconformity; not every small error needs a big analysis.
After implementation you check whether the action worked and, where necessary, adapt the system: a rule, a process, a training course, and with ISO 9001 also the assessment of risks and opportunities. The nature of the nonconformity, the actions taken and the result of the corrective action are recorded.
In the audit, 10.2 is the test of whether a system learns from mistakes. There is no longer a separate requirement for preventive action; prevention is part of addressing risks and opportunities. The state of nonconformities feeds into the management review, and effective corrective actions count towards continual improvement.
What the auditor checks
“Show me a corrective action with a root cause analysis.”
Whether the cause was actually investigated or whether the first explanation is already treated as the cause. A good analysis ends at something that can be eliminated: a rule, a process, a tool, not at “employee was not paying attention”.
“What did you do immediately, and what did you do so that it does not happen again?”
The difference between correction and corrective action. The correction fixes the error and its consequences, the corrective action eliminates the cause. If both say the same thing, the second step is missing.
“Could the same cause be at work somewhere else?”
Whether it was checked if similar nonconformities exist or could occur: on the neighbouring machine, at the other site, with the same supplier, in a similar process.
“How did you notice that the action worked?”
Whether effectiveness was assessed after an appropriate time and against a criterion set in advance: no recurrence in six months, a rate below the target value, a sample without findings. “Action implemented” says nothing yet about the effect.
“Where do your nonconformities come from?”
Whether only audit findings are in the system or also complaints, internal errors, supplier problems, incidents and observations from the operation. If the register only knows audits, nonconformities from daily work are evidently dealt with elsewhere, or not at all.
“What became of the nonconformities from the last external audit?”
Whether they were dealt with on time and demonstrably and the cause has been eliminated. A nonconformity that reappears unchanged in the follow-up audit weighs considerably more than the first time.
Which evidence convinces
A register of all nonconformities with source, date and status
From audits, complaints, incidents, inspections and your own observations. It shows that nonconformities from all sources go through the same procedure and nothing gets lost.
The documented correction and the root cause analysis
What happened immediately and why it occurred, with the method chosen, for example five times “Why?” or a cause and effect diagram. This shows whether the action addresses the cause.
Corrective actions with responsible persons, deadline and status
This makes it possible to follow in the audit whether what was decided has been implemented.
The effectiveness review with date, criterion and result
It closes the case. Even “not effective, new analysis” is convincing evidence, because it shows that someone looked.
The consequences for the system
Changed rules, processes or training and an updated risk assessment where the cause required it. They show that the cause was not only eliminated in the individual case.
Typical nonconformities
Correction without cause
The error has been fixed, the parts have been reworked, the nonconformity has been closed. Nobody asked about the cause. A very common finding, because the pressure eases as soon as the error is out of the way.
The cause ends with a person
“Human error” as the cause and “employee instructed” as the action. Why the error was possible and why nobody noticed it remains open.
Effectiveness never checked
Actions have been implemented and ticked off, an assessment of their effect is missing. If this affects individual cases, it is usually a minor nonconformity. If it is missing throughout, the procedure does not work at this point, and it can be a major nonconformity.
The same nonconformity keeps coming back
A nonconformity reappears unchanged in the next audit or the next complaint. The corrective action has not worked, the cause has not been eliminated. If a minor nonconformity from the last certification audit recurs, it often becomes a major one, because the system visibly does not work at this point.
Nonconformities are left lying
Open nonconformities without a deadline or overdue for months, without anyone stepping in. Or errors in daily work are not recorded at all, but settled verbally and can no longer be traced afterwards.
Differences by standard
ISO 9001ISO 9001
Under ISO 9001, corrective action also includes updating the risks and opportunities from planning where necessary. Defective products themselves are dealt with in 8.7: there it is about the affected part or service, here about the cause. Customer complaints are one of the most important sources. The number 10.2 stays the same in the 2026 edition; continual improvement has moved from 10.3 to 10.1.
ISO 14001ISO 14001
ISO 14001 explicitly requires that a nonconformity also includes mitigating adverse environmental impacts, and the corrective action is proportionate to the significance of the effects, including those on the environment. Nonconformities here often come from the evaluation of compliance, from measurements of emissions or waste water and from incidents to which emergency preparedness responded.
ISO 27001ISO/IEC 27001
In ISO/IEC 27001:2022, 10.2 comes after continual improvement in 10.1. Nonconformities here also come from information security incidents, vulnerabilities and technical checks. An information security incident is not automatically a nonconformity of the management system; it becomes one if a requirement or a defined control was not met. The handling of incidents itself belongs to the Annex A controls.
How IMScollect covers it
In IMScollect major and minor nonconformities from the internal audit appear automatically under corrective actions, with standard, clause and responsible person. You create all others with their source: external audit, customer complaint, authority, supplier, information security incident or your own observation.
Every nonconformity goes through the same five stages: recording, immediate action, root cause analysis, corrective action and effectiveness check. You analyse the cause with five times “Why?” or an Ishikawa diagram, corrective actions become tasks with responsible person and deadline, and for effectiveness you record how it can be recognised. If an action is not effective, the nonconformity returns to root cause analysis. If you wish, an 8D report across all stages is produced as a PDF, and the state of nonconformities feeds into the management review.
Frequently asked questions
What is the difference between correction and corrective action?▾
The correction fixes the error and its consequences, for example blocking and reworking goods. The corrective action eliminates the cause so that the error does not recur, for example a changed inspection rule or a fixture that rules out a mix-up.
Does every nonconformity need a root cause analysis?▾
The standards require you to evaluate the need for action to eliminate the cause, and the action should be proportionate to the effects of the nonconformity. For a one-off, minor error a short, reasoned assessment can be enough. For audit nonconformities, recurring errors and complaints, auditors expect a real analysis.
Which root cause analysis method is the right one?▾
The standards do not prescribe one. Five times “Why?” is enough in many cases, a cause and effect diagram (Ishikawa) helps when there are several possible causes, and the 8D report is widespread for customer complaints in industry. What matters is that the analysis ends at a cause that can be eliminated.
When is a corrective action effective?▾
When the cause has been eliminated and the nonconformity does not recur. How this is measured and after what time is best decided when planning the action, for example “no recurrence in the next 50 deliveries”. Without a criterion set in advance, the assessment easily becomes a formality.
Is there still preventive action?▾
Not as a separate requirement, since the 2015 editions of ISO 9001 and ISO 14001 and since 2013 for ISO/IEC 27001. Prevention today is part of addressing risks and opportunities under 6.1 and of asking whether the same cause could be at work elsewhere.
