TLDR
Corrective action is the process of identifying the root cause of a nonconformance and implementing changes to prevent it from recurring. In manufacturing, it is a formal requirement of every major quality management system standard, including ISO 9001 and IATF 16949.
This guide covers the definition of corrective action, how it differs from correction and preventive action, the corrective action cycle, its connection to the 8D process, documentation requirements, and how to close out audit findings properly.
Fixing Problems Is Not Enough
When a quality problem occurs, there is always pressure to fix it fast and move on. Replace the defective parts. Sort the suspect lot. Get the line running again. That urgency is understandable. But fixing the immediate problem without addressing why it happened guarantees one thing: it will happen again.
Corrective action is the structured process that goes beyond the fix. It identifies the root cause, implements changes to eliminate it, and verifies that the changes actually worked. It is the difference between putting out fires and preventing them.
Defining the Terms
Three related terms cause frequent confusion. Understanding the distinctions matters for both practice and audits.
Correction: The immediate action taken to eliminate a detected nonconformance. Sorting defective parts, reworking a batch, or replacing a rejected component are all corrections. They address the symptom, not the cause.
Corrective action: Action taken to eliminate the root cause of a detected nonconformance to prevent its recurrence. Corrective action is reactive (it responds to a problem that has already occurred) but forward-looking (it changes the system to prevent repetition).
Preventive action: Action taken to eliminate the cause of a potential nonconformance before it occurs. Preventive action is proactive. Under ISO 9001:2015, the concept of preventive action has been absorbed into the broader framework of risk-based thinking, but the principle remains the same.
The Corrective Action Cycle
Corrective action follows a structured cycle. Whether you call it a Corrective Action Request (CAR), a Corrective and Preventive Action (CAPA), or use the 8D methodology, the core steps are the same.
1. Identify the Problem
Define the nonconformance clearly and specifically. “Parts are bad” is not a problem statement. “Bore diameter on part number 12345 exceeded USL by 0.05 mm on 47 parts produced between 6:00 AM and 10:00 AM on March 15” is a problem statement. The more precise the description, the easier the investigation.
2. Contain the Issue
Before investigating the root cause, protect the customer. Sort suspect inventory. Quarantine affected lots. Implement interim controls at the point of detection. Containment buys you time to investigate without shipping nonconforming product.
3. Investigate the Root Cause
Use structured root cause analysis tools. The 5 Whys, fishbone diagrams, fault tree analysis, and other methods help you dig below the surface symptom to find the systemic cause. A good root cause analysis answers: “What condition in the system allowed this failure to happen?”
4. Implement Corrective Action
Define and implement changes that address the root cause. This could involve modifying a process parameter, updating a work instruction, adding a poka-yoke device, changing a material specification, or revising a training program. The corrective action must be specific, measurable, and documented.
5. Verify Effectiveness
After the corrective action is in place, verify that it works. This step is where many organizations fall short. Verification means collecting objective evidence that the root cause has been eliminated and the nonconformance has not recurred. Define the verification method, the timeframe, and the acceptance criteria before implementation.
6. Standardize and Close
Update all affected documents: control plans, work instructions, PFMEAs, training records, and inspection procedures. Ensure the change is embedded in the management system so it persists. Only then should the corrective action be closed.
The 8D Connection
The 8D (Eight Disciplines) problem-solving process is the most widely used corrective action methodology in the automotive industry. Originally developed by Ford Motor Company, it follows a structured eight-step approach that maps directly to the corrective action cycle.
D0: Plan. D1: Establish the team. D2: Define the problem. D3: Develop interim containment. D4: Identify root cause. D5: Choose permanent corrective action. D6: Implement and validate. D7: Prevent recurrence. D8: Recognize the team.
When a customer sends you a Supplier Corrective Action Request (SCAR), they are almost always expecting an 8D response or equivalent. The 8D format provides a common language and structure that both parties can follow.
Documentation Requirements
Quality management system standards require that corrective actions be documented. At a minimum, your records should include the following.
The nonconformance description: What happened, when, where, and the extent of the problem.
Containment actions taken: How suspect product was identified, segregated, and dispositioned.
Root cause analysis: The method used and the root cause(s) identified. Include the evidence and reasoning, not just the conclusion.
Corrective action implemented: Specific changes made, who is responsible, and the implementation date.
Effectiveness verification: The method, timeframe, results, and conclusion. Was the action effective?
Documents updated: List of control plans, work instructions, FMEAs, or other documents revised as a result.
Closing Out Audit Findings
Audit findings, whether from internal audits, customer audits, or third-party certification body audits, require corrective action. The process for closing them follows the same cycle but with some additional expectations.
Respond within the required timeframe. Most auditors specify a deadline for the initial corrective action response. Missing it reflects poorly on your organization and can escalate the finding.
Address the finding as written. Do not reinterpret or minimize the finding. If the auditor identified a gap in your process, your corrective action must address that specific gap. Auditors will reject responses that sidestep the issue.
Provide objective evidence. The auditor needs proof, not promises. Include before-and-after documentation, revised procedures, photographs, data, training records, or other evidence that demonstrates the corrective action was implemented and verified.
Address systemic implications. If the finding could apply to other processes, products, or sites, extend the corrective action accordingly. Auditors will ask whether you considered the broader impact, and failure to do so often generates a follow-up finding.
Do not close prematurely. Some organizations rush to close audit findings by implementing the action without waiting for verification. This creates a false sense of completion. The finding should remain open until effectiveness has been confirmed with objective evidence.
Why Corrective Actions Fail
The root cause analysis stopped too early. “Operator error” is not a root cause. Why did the operator make the error? Was the work instruction unclear? Was the training inadequate? Was the process design vulnerable to human error?
The corrective action addressed the symptom, not the cause. Adding inspection does not prevent defects. It detects them. If your corrective action is “add 100% inspection,” you have implemented a correction, not a corrective action.
Verification was skipped or superficial. Checking a box that says “verified effective” without data to support it is meaningless. Define how you will measure success before you implement the change.
Documents were not updated. The corrective action exists in practice but not in the system. The next person to follow the work instruction or control plan will repeat the original error because the documentation was never revised.
Frequently Asked Questions
Correction addresses the immediate nonconformance (sorting, reworking, or replacing defective parts). Corrective action identifies and eliminates the root cause to prevent the nonconformance from recurring. Both are needed, but corrective action is the one that creates lasting improvement.
Containment should happen immediately. Root cause analysis and corrective action implementation depend on the complexity of the problem but are typically expected within 30 to 60 days. Effectiveness verification may extend beyond that based on the monitoring period needed.
A Supplier Corrective Action Request (SCAR) is a formal request from a customer to a supplier to investigate a quality issue and provide a corrective action response. It typically requires an 8D or equivalent format and has a defined response deadline.
Yes. ISO 9001:2015 Clause 10.2 requires organizations to react to nonconformities, evaluate the need for corrective action, implement actions to address root causes, review effectiveness, and update risks and opportunities if necessary.
Corrective action addresses a nonconformance that has already occurred. Preventive action addresses a potential nonconformance before it happens. In ISO 9001:2015, the concept of preventive action is addressed through risk-based thinking rather than a separate preventive action requirement.
Collect objective evidence that the nonconformance has not recurred after the corrective action was implemented. This may include inspection data, process monitoring results, audit results, or the absence of repeat customer complaints over a defined period. Define the verification criteria before implementation.
Adding inspection is a detection measure, not a corrective action. It catches defects but does not prevent them. True corrective action modifies the process to eliminate the root cause. If additional inspection is needed as interim containment, pair it with a systemic corrective action that addresses the underlying cause.
Stay Current on Automotive Quality
PPAP updates, GD&T guidance, and practical quality resources delivered to your inbox. No spam, just what quality professionals need to know.
Subscribe
Leave a Comment