Few things cause as much confusion in a Quality Management System as non-conformities. The good news is that, properly understood, they're the exact opposite of a failure: they're the tool that proves the system works.
What a non-conformity is
A non-conformity is the failure to meet a requirement — it can be a requirement of ISO 9001 itself, a legal requirement, an internal requirement your company has set for itself, or something the customer expected and didn't get. Clause 10.2 of the standard (Nonconformity and corrective action) governs how it must be managed.
Major, minor, and observation: not the same thing
- Major non-conformity: a complete failure to meet a requirement, or a repeated/systemic problem. It can block certification until it's fixed.
- Minor non-conformity: a partial or one-off failure that doesn't compromise the system's overall effectiveness. Certification can proceed with a deadline to fix it.
- Observation: not a failure as such, but a sign that something could turn into a non-conformity if left unattended — a preventive flag, not a penalty.
The steps to manage a non-conformity properly
- React and fix the immediate issue. First you contain and correct the specific problem — this "correction" is not yet the corrective action.
- Analyze the root cause. This is the step most often skipped, and the most important one. It's not enough to ask "what happened?" — you have to ask why it happened, and why that happened, until you reach the underlying cause (tools like "5 whys" help a lot here).
- Check for similar cases. If this non-conformity could happen here, could it also be happening in another process or site that hasn't been detected yet?
- Define the corrective action. An action aimed at the root cause, not just the symptom — different from the one-off correction in step 1.
- Verify that the action worked. After a reasonable amount of time, check whether the problem has recurred. If it isn't verified, the non-conformity isn't really closed.
- Document everything. The standard requires keeping evidence of the correction, the analysis, and the corrective action — not as red tape, but as proof the cycle genuinely closed.
Most common mistakes
- Confusing correction with corrective action. Fixing the specific problem isn't the same as preventing it from happening again.
- Rushing the cause analysis. "Human error" is almost never a real root cause — there's usually a poorly designed process, lack of training, or lack of resources behind it.
- Not verifying effectiveness. Closing the non-conformity without later checking whether it genuinely stopped happening.
- Treating them as something to hide. A system with zero non-conformities after years in operation usually raises more doubts with an auditor than one with non-conformities that are well managed and closed.
Analyze the root cause with AI's help
In EcoNiora's Non-Conformities module you can describe the problem in your own words and ask the AI to propose a root-cause analysis and a corrective action — always based on what you describe, never inventing facts.
Request access →