Correction addresses the identified problem. Root cause analysis explains how it arose, while corrective action addresses the cause to prevent recurrence. A credible response connects all three and provides evidence of implementation and effectiveness appropriate to the issue.
Why does correcting an inaccurate document not always close a non-conformity?
Fixing the effect of a problem is usually only a correction. If the cause remains in the system, the same error may recur at the next delivery, batch or audit. Effective closure should show what was fixed immediately, why the problem arose and what changed to reduce the risk of recurrence.
1. A non-conformity identifies a specific unmet requirement
A well-written audit finding links a requirement to objective evidence. A general statement such as “the documentation is poor” is insufficient. The finding needs to identify what is missing and the basis for that conclusion.
The company should respond to the actual non-conformity rather than what it thinks the auditor meant.
2. Correction addresses the immediate problem
A correction concerns the particular case identified. If a supplier certificate has expired, a correction may involve obtaining the current document and verifying its scope.
If a control record is missing, a correction may involve performing the check and supplying the missing evidence, where this is still possible and credible. This does not explain why the system allowed the error to arise. Missing historical records must not be invented or backdated.
3. Root cause analysis is more than a description of the symptom
Root cause analysis should identify the mechanism that led to the problem. Statements such as “the employee forgot” or “an oversight” usually stop the investigation too early.
Ask why forgetting was possible. Was there no assigned responsibility, reminder, checklist, training, document review or cover during an absence?
4. One non-conformity can have several causes
A missing current supplier certificate may result from a combination of no process owner, no record of expiry dates and no check when suppliers change.
Action focused on only one element may not protect the whole system. The analysis should be proportionate to the risk and scale of the problem.
5. Corrective action changes the system
Corrective action addresses the cause. For expiring certificates, an example is a central register with expiry dates, assigned responsibility, reminders and a purchasing block where verification is not current.
Retraining alone may be insufficient where the process design caused the problem. Training is effective when a lack of knowledge was genuinely a cause.
6. Implementation evidence matters as much as the plan
“We will implement a new procedure” is a plan rather than evidence. Closure may require revised documents, training records, an example of the new form in use, a system screenshot, a repeat check result or other objective evidence.
The required evidence depends on the non-conformity and programme requirements.
7. Check whether the problem extends further
If one batch has an incorrect recycled content figure, check other batches from the same period. If one supplier certificate is invalid, review the supplier register.
This helps establish whether the finding is isolated or indicates a system-wide problem.
8. Example: unidentified material in the warehouse
Correction: identify the unlabelled batch and confirm its status. Cause: no clear rule for creating a new label after material is repacked.
Corrective action: require a label whenever packaging is changed, assign responsibility and introduce sample warehouse checks by the quality function.
9. Example: a material reconciliation discrepancy
Correction: recalculate the relevant period after resolving a unit error. Cause: one system exported kilograms while another report used tonnes without automatic conversion.
Corrective action: standardise units in the template, restrict the input format and require a second-person check before approving the reconciliation.
10. Example: supplier certificate validity is not monitored
Correction: obtain the current certificate and verify its scope. Cause: no owner for the supplier register or renewal dates.
Corrective action: assign responsibility, maintain an expiry calendar, perform periodic reviews and require verification when a supplier changes.
11. Effectiveness should be assessable
A good corrective action has an effectiveness criterion. Examples include no recurrence during a defined period, a satisfactory review of every supplier or three subsequent reconciliations without the same error.
Without a criterion, it is difficult to distinguish actual improvement from simply marking a task as complete.
12. A common mistake: “We corrected the document”
If the company submits only a corrected form, the auditor or reviewer may ask why the incorrect version was previously used and what will prevent recurrence.
This is why correction, cause and corrective action should form a logical chain.
FAQ
Does every non-conformity require a detailed 5 Why analysis?
No. The depth of analysis should be proportionate to the problem. A credible cause and effective action matter more than the method's name.
Can human error be the root cause?
Sometimes, but it is often only the starting point. Check why the system permitted the error and whether its likelihood can be reduced.
Is training always a suitable corrective action?
Only where a lack of knowledge or competence was a cause. Training alone may not resolve a process design problem.
Must other batches or suppliers be checked?
Yes, where the problem may extend further. Evaluating its extent is an important part of a credible response.
Can the auditor write the company's corrective action?
The auditor should not design a solution they will assess. They can explain the requirement and evaluate the actions submitted.