Short answer
Non-conformity closure time is the time between the date it is detected and the date the corrective action is verified as effective. To shorten it, record one date per phase (detection, containment, root cause, corrective action, implementation, verification and closure), calculate how many days each NC spends in each phase, and tackle the phase where waiting piles up. There is no universal deadline: it depends on your system, your certification body and the type of finding.
Many organisations know how many non-conformities are open, but not how long each one takes to close or which step it gets stuck on. Without that figure, NCs drag on and arrive overdue at the next audit. This guide does not offer third-party statistics: it explains how to measure your own closure time and what to do with what you find.
ISO 9001 requires, in general terms, that the organisation deal with non-conformities, take action to control and correct them, and assess whether corrective action is needed to stop them recurring. How you organise this and what deadlines you set is up to you, and it is what the auditor will review.
1. The cycle phases and how to measure each one
Add one date column per phase to your non-conformity log. The time spent in a phase is the difference between two consecutive dates.
- Detection: the date the finding is identified (audit, complaint, inspection or self-check).
- Containment: when the immediate correction is applied so the problem does not spread (quarantine a batch, stop the line, notify the customer).
- Root cause analysis: when the underlying cause is identified and documented, not just the symptom.
- Corrective action: when the plan is approved, with an owner and a target date.
- Implementation: when the action is carried out on the shop floor or in the office.
- Effectiveness verification: when you check, with evidence, that the problem has not recurred.
- Closure: when the record is formally closed.
After a few months of records you will see which phases accumulate waiting time. Also track how many NCs are reopened or rejected on review, because each rejection restarts part of the cycle. Calculate times by finding type (major, minor, observation) so you do not mix very different cases.
2. Typical bottleneck and how to tackle it
These are common bottlenecks in practice. Check which ones show up in your own log before acting.
| Phase | Typical bottleneck | How to tackle it |
|---|---|---|
| Detection to containment | Nobody is assigned the NC when it is opened | Assign an owner at the moment of logging and set a containment deadline |
| Root cause | Stops at the surface cause ("human error") and the analysis has to be redone | Use a structured method (5 whys, cause diagram) and require the cause to explain why the system allowed it |
| Plan approval | The plan waits for the signature of an overloaded person | Define who approves and a maximum time; name deputies |
| Implementation | The action depends on investment, a supplier or training that was not planned | Split the action into dated steps and review progress in a short regular meeting |
| Effectiveness verification | Forgotten, or closed without evidence | Set the verification date when approving the plan and define what evidence will prove it |
| Certification body review | The plan is rejected for lacking root cause or evidence | Review the plan internally against the same criteria before sending it |
3. How to write the non-conformity so it closes first time
A poorly written NC causes back-and-forth. A clear one contains three elements:
- The fact: what was observed, where and when, without judgements or generalities.
- The requirement not met: what the standard, internal procedure or customer requirement demanded, quoted as it appears in your documentation.
- The evidence: the record, sample or specific observation that shows the fact (document reference, batch, date).
Illustrative example with assumed figures
An NC is detected on day 1, contained on day 2, the root cause analysis is approved on day 10, the plan on day 18, it is implemented on day 30 and verified on day 60. Total: 60 days, 30 of which pass between implementation and verification. In this made-up case, the most profitable improvement would be adjusting the verification date. These figures do not come from any study: replace them with those from your own log.
4. How to start this week
Take the NCs open today, add the phase dates you can reconstruct and calculate the time in each. Prepare the ground with an internal audit checklist and assess your starting point with the ISO 9001 readiness self-assessment. To see why certification audits fail, read ISO 9001 vs IATF 16949 and the guide on why companies fail the audit (in Spanish).
Frequently asked questions
What is the deadline to close a non-conformity?
There is no single deadline valid for everyone. Your procedure defines it and, in certification, you agree it with your certification body according to the finding type. Check its instructions.
Is closing the NC the same as correcting it?
No. Correcting removes the detected problem; the corrective action removes the cause so it does not recur. Closure requires verifying that the action was effective.
What if the root cause is unclear?
Document what you know, apply containment and set a review date. A well-investigated cause that takes a little longer beats a superficial one that forces the NC to be reopened.
How do I avoid reopened NCs?
Write the fact, requirement and evidence precisely, demand a root cause that explains the system failure, and verify effectiveness with evidence, not opinion.
Manage your non-conformities with traceability
If you want to centralise quality documents, records and deadlines in a plant, discover IgeraIndustria.