Five Questions to Ask Before Closing a Corrective Action
A due date is not evidence that a corrective action worked. Neither is a revised procedure, a completed training record, or a green status indicator on a corrective-action log.
Those items may show that someone completed an assigned task. They do not necessarily show that the organization understood the failure, removed its cause, or reduced the risk of recurrence.
That distinction matters because a prematurely closed corrective action can make the management system look healthier than it is. The record says the problem is resolved. Operations may already be dealing with the same weakness under a different part number, customer, shift, supplier, or process name.
ISO 9001 and AS9100 require organizations to respond to nonconformities, address causes when corrective action is needed, implement appropriate action, and review effectiveness. They do not prescribe the five-question format below. This is a CDSAQS professional framework for making the closure decision more disciplined. It should be used together with the requirements that apply to the organization, including customer, contractual, certification, and regulatory obligations.
1. What exactly failed, and how far did it reach?
Before reviewing root cause, I would first confirm that the organization defined the problem accurately.
A weak problem statement usually describes a symptom: a dimension was out of tolerance, a record was missing, a shipment was late, or an audit requirement was not met. A useful problem statement establishes what was expected, what actually occurred, where and when it occurred, how it was detected, and what evidence establishes the difference.
The organization also needs to understand the extent of the condition. That inquiry may include other lots, work orders, products, programs, customers, shifts, machines, suppliers, records, or locations that relied on the same control. The appropriate scope depends on the nature and risk of the issue; there is no universal sample size.
Containment and correction belong in this discussion, but they are not the same as corrective action. Segregating affected product, correcting a record, replacing a tool, or reworking an item may address the immediate condition. Those actions do not, by themselves, prevent the condition from returning.
If the organization cannot explain the problem and its potential extent, it is not ready to claim that the cause has been eliminated.
2. Did we verify the cause, or only select a believable explanation?
Many corrective actions become weak at this point. The team finds an explanation that sounds reasonable, records it as the root cause, and moves directly to action.
“Operator error,” “lack of training,” “procedure not followed,” and “supplier issue” may describe where the failure became visible. They do not automatically explain why the management system allowed it to occur and escape detection.
A cause should be supported by evidence. The evidence may come from interviews, records, process data, equipment history, change history, replicated conditions, inspection results, system permissions, workload, environmental conditions, or comparison with conforming activity. The method can be simple or sophisticated, but it should fit the complexity and consequence of the problem.
Five Whys, fishbone diagrams, and similar tools can organize thinking. None of them proves a cause merely because the form is complete. The test is whether the evidence connects the identified cause to the observed failure and whether plausible competing explanations were reasonably considered.
Some events have multiple contributing causes. Forcing every investigation into one neat root-cause sentence can hide the interaction between planning, equipment, competence, supervision, information, supplier control, and verification. A concise answer is useful only when it is also true.
3. Do the actions address the cause and the system that allowed it?
Once the cause is understood, each corrective action should map back to that cause.
Revising a procedure is appropriate when the documented method was missing, inaccurate, unclear, or inconsistent with the required process. If competence or understanding contributed to the failure, a weakness in training may be part of the root cause, but that conclusion requires caution. It also raises another question: why did the existing training and training-effectiveness process fail to establish or verify the required competence and understanding? Simply providing additional training without answering that question may treat the symptom while leaving the systemic weakness intact. Neither a procedure revision nor additional training is automatically effective simply because it is familiar and easy to document.
If the real problem involved an uncontrolled process change, a weak handoff, an incapable measurement method, an unrealistic production assumption, missing supplier controls, or a review step with no defined acceptance criteria, another training session may leave the operating condition unchanged.
The stronger question is not, “Did we assign an action?” It is, “If these actions had been in place earlier, is there a defensible reason to believe the failure would have been prevented or detected before escape?”
Corrective action should also avoid creating a new problem. An added inspection may reduce one escape while increasing cycle time, queue time, handling damage, or dependence on an already constrained resource. The organization should consider those tradeoffs rather than moving risk to another part of the process.
4. Can we prove the actions were implemented as intended?
An approved plan is not implementation. A released document is not implementation. Attendance at training is not proof that the revised method is being used correctly.
Objective implementation evidence should match the action. Depending on the issue, that might include sampled work records, observed process execution, system-configuration evidence, revised acceptance criteria, completed maintenance, updated purchasing controls, supplier acknowledgments, competence demonstration, or records showing that the new review actually occurred.
The reviewer should be able to determine:
- What changed
- Who owns the changed control
- When it became effective
- Where it applies
- Whether affected personnel and systems are using it
- Whether the retained evidence supports the completion claim
This does not require unnecessary paperwork. It requires enough reliable evidence to distinguish an implemented control from an action that exists only in the corrective-action file.
5. What evidence shows the action was effective over meaningful exposure?
Implementation asks whether the organization made the change. Effectiveness asks whether the change achieved the intended result.
“No recurrence” can be useful evidence, but only if the process had a meaningful opportunity to fail again. A problem associated with a quarterly activity cannot be proven effective after one quiet week. A corrective action affecting a low-volume product may need a different verification period than one affecting hundreds of transactions each day.
The effectiveness plan should be proportional to risk and should identify, preferably before closure, what will be reviewed, who will review it, and what result will support the decision. Evidence may include defect or escape data, process-performance results, audit sampling, customer feedback, repeat-event analysis, first-pass yield, supplier performance, or direct observation of the changed control.
The reviewer should also look beyond the original event. Did the same cause produce a different nonconformity elsewhere? Did the action reduce one failure mode while another indicator deteriorated? Were there enough production cycles, transactions, audits, or service events to make the conclusion credible?
Time passing is not an effectiveness check. Exposure plus evidence is.
Separate action completion from corrective-action closure
One practical improvement is to distinguish between “actions implemented” and “effectiveness verified.” That prevents the organization from calling the corrective action closed merely because the task list is complete.
The exact workflow should fit the organization, its risks, and its applicable requirements. The principle is more important than the label: when effectiveness cannot yet be demonstrated, the record should remain visible and controlled until the planned verification can be completed.
I would not close a corrective action simply because every action owner met a date. I would close it when the evidence supports the conclusion that the organization understood the failure, addressed the cause, implemented the change, and demonstrated that the change worked.
That is a management decision, not a clerical one.
Premature closure has an operational cost
Weak closure decisions do more than create repeat audit findings. They allow recurring escapes, rework, added inspection, premium freight, schedule disruption, customer concern, and lost capacity to continue while the management system reports that the problem has been solved.
They also degrade trust in the corrective-action process. Employees learn that completing the form matters more than improving the process. Managers receive clean dashboards that do not reflect operating reality. Customers see repeated failures accompanied by new corrective-action numbers and increasingly familiar explanations.
An effective corrective-action system does not need to be large or bureaucratic. It needs disciplined problem definition, evidence-based cause analysis, actions tied to causes, implementation evidence, and an effectiveness decision based on meaningful exposure.
Before closing the next corrective action, ask the five questions and require the record to support the answers. If the evidence is not there, the paperwork may be complete, but the corrective action is not.