Quality engineers use "8D" and "CAPA" interchangeably every day, and most of the time they get away with it. Until an IATF auditor asks: "Show me your CAPA procedure." The engineer pulls up a stack of 8D reports. The auditor is not satisfied. The finding reads: "No documented CAPA procedure per IATF 16949 Clause 8.7.1."
Understanding the difference is not academic. It affects what your quality system needs to document, what goes in your PPAP, and what customers expect to see when something goes wrong.
What 8D Is
8D (Eight Disciplines) is a problem-solving methodology developed by Ford Motor Company in the 1980s. It structures the investigation of a quality problem into eight distinct disciplines, each with a clear deliverable.
| Discipline | Name | What Gets Done |
|---|---|---|
| D1 | Team Formation | Assemble a cross-functional team with the authority and expertise to solve the problem |
| D2 | Problem Description | Define the problem with quantitative data: what, where, when, how many |
| D3 | Interim Containment Action | Stop the bleeding. Protect the customer now, before the root cause is identified |
| D4 | Root Cause Analysis | Identify the escape point and the root cause using 5-Why, fishbone, or fault tree |
| D5 | Permanent Corrective Actions | Define and select the actions that eliminate the root cause permanently |
| D6 | Implementation and Validation | Execute the actions and verify they eliminate the root cause without creating new problems |
| D7 | Prevent Recurrence | Modify the quality system, control plan, PFMEA, or procedures to prevent the problem from occurring again |
| D8 | Recognize the Team | Document the resolution, close the report, acknowledge contributions |
8D is a structured format. It tells you what to do in what order. It is not a quality system requirement. No standard mandates that you use 8D specifically. You can solve quality problems with A3, PDCA, or any other structured approach and still satisfy your quality system requirements.
What 8D gives you: a disciplined, traceable record of how a problem was investigated and resolved, in a format that most automotive customers recognize and accept.
What CAPA Is
CAPA (Corrective Action and Preventive Action) is a quality system requirement. It defines two types of actions:
Corrective Action: A response to a nonconformance that has already occurred. It eliminates the root cause to prevent recurrence.
Preventive Action: A proactive response to a potential nonconformance that has not yet occurred but could. It addresses risks identified through analysis -- internal audits, trend data, risk assessments.
IATF 16949:2016 Clause 8.7.1 requires a documented corrective action process. The standard specifies that your corrective action process must:
- Review nonconformances and customer complaints
- Determine root causes using appropriate tools
- Evaluate the need for action to ensure nonconformances do not recur
- Determine and implement necessary actions
- Review the effectiveness of the corrective actions taken
- Update risk assessments and quality system documentation as needed
Clause 10.2.1 requires the organization to take corrective action to eliminate the causes of nonconformities. Clause 10.3.1 requires preventive action to eliminate potential causes.
ISO 9001:2015 has equivalent requirements. So do AS9100 (aerospace) and ISO 13485 (medical devices), each with their own specifics.
CAPA is what your quality system must do. It says nothing about the methodology you use to get there.
The Actual Difference
| 8D | CAPA | |
|---|---|---|
| What it is | Problem-solving methodology | Quality system requirement |
| Defined by | AIAG, Ford, customer requirements | IATF 16949, ISO 9001, regulatory standards |
| Mandated? | No -- it is one approach among many | Yes -- the standard requires it |
| Output | A completed 8D report | A documented, effective corrective or preventive action |
| Scope | Reactive: responds to a specific known problem | Both reactive (corrective) and proactive (preventive) |
| Effectiveness measured by | Whether the problem recurs | Whether the root cause and nonconformance are eliminated |
The key insight: 8D can satisfy a CAPA requirement. But a CAPA requirement can be satisfied by many methodologies. Completing an 8D report is not the same as having a CAPA process.
Why Quality Teams Conflate Them
Three reasons this confusion persists:
1. Automotive customers request 8D reports, not CAPAs.
When a Ford or GM plant sends a supplier a corrective action request (CAR) or a SCAR (Supplier Corrective Action Request), they use the 8D format. The form says "8D Report." The supplier fills it out. Over time, "doing our CAPAs" becomes synonymous with "filling out 8D reports."
2. They cover similar ground.
Both 8D and CAPA require root cause analysis, corrective action, and evidence of effectiveness. A completed 8D report that includes D7 (prevent recurrence) does satisfy the substance of a corrective action requirement -- it just needs to exist within a documented CAPA process.
3. Preventive action gets ignored.
Most quality teams do corrective action adequately. Preventive action -- the PA in CAPA -- is where systems break down. CAPA requires looking at trends, audit findings, and process data to act before a nonconformance occurs. 8D only applies after the problem has already happened. If your system has no mechanism for preventive action, you have a gap that 8D reports cannot fill.
When to Use 8D
Use 8D when:
- A customer has issued a CAR or SCAR and their template requires 8D format
- The problem involves a real escape -- product reached the customer
- A cross-functional team investigation is warranted by the severity or scope
- You need a structured timeline showing D3 containment was immediate and D6 validation was thorough
- The problem links to a PFMEA detection failure that needs to be updated (D7 drives the PFMEA update)
8D is most powerful when D3 and D4 are done rigorously. Containment that actually contains the problem, and a root cause that addresses the real failure mode -- not the symptom. A five-why chain that stops at operator error when the real cause is a fixture tolerance variation is not a root cause.
D4 and the PFMEA are tightly connected. When the root cause is a detection failure, D7 should update the PFMEA with a new detection control and revised RPN. That updated PFMEA then drives a control plan update. This is the cascade that makes 8D meaningful beyond just closing the ticket. The PFMEA guide covers how to structure detection controls so D7 updates land in the right place.
When CAPA Requirements Go Beyond 8D
Your CAPA process needs to handle situations 8D was not designed for:
Internal audit findings. When an IATF internal audit identifies a system nonconformance, it generates a corrective action. That corrective action runs through your CAPA process. Audit findings do not get 8D reports -- they go through whatever corrective action procedure is documented in your quality manual.
Customer complaints that are not formal CARs. A customer calls with a concern. No formal rejection, no RMA. Your CAPA process should log it, evaluate whether a corrective or preventive action is warranted, and document the outcome -- even if the outcome is "evaluated, no action required, rationale: isolated occurrence with no systemic root cause."
Preventive actions from risk analysis. IATF Clause 10.3.1 requires preventive action based on risk analysis, trend review, and predictive quality data. None of that maps to an 8D report because there is no specific nonconformance to respond to -- you are acting on a potential problem before it occurs.
Field returns and warranty claims. Warranty data showing a pattern of failures is a corrective action trigger. The 8D format handles the investigation well, but the process that routes warranty data into a corrective action investigation is the CAPA system -- not the 8D form itself.
What IATF 16949 Auditors Actually Check
When an IATF auditor asks for your CAPA process, they want to see:
A documented procedure. The procedure that defines how CAPAs are initiated, investigated, implemented, and verified effective. Not a stack of 8D reports. A procedure with scope, inputs, process steps, responsibilities, and effectiveness criteria.
A log or register. Evidence that all corrective actions are tracked from initiation to closure. Sources should include customer complaints, internal audits, warranty returns, and supplier issues. Each entry should show current status, owner, and due date.
Effectiveness review. Closed CAPAs need evidence that the action worked. Re-occurrence data over a defined window, SPC trend data showing the characteristic remained stable, updated control plan versions, or subsequent audit findings confirming the prior nonconformance has not recurred.
Preventive actions. At least some evidence that the organization initiates preventive actions based on proactive review -- trending data, risk assessment outputs, internal audit themes. If every entry in the CAPA log is a reactive response to an escape, that pattern is a finding in itself.
Document control integration. When a CAPA drives a change to a procedure, work instruction, or control plan, the document update trail should trace back to the CAPA number. Auditors follow the chain from problem to procedure change. If that chain breaks, the corrective action is not considered complete.
The Preventive Action Gap Most Teams Have
ISO 9001:2015 removed the explicit "preventive action" section from the standard, folding it into risk management under Clause 6.1. Some teams read this as "preventive action is no longer required." That interpretation is wrong.
IATF 16949 Clause 10.3.1 explicitly requires preventive action. The methodology for generating preventive action inputs should include:
- Trend analysis of internal and external nonconformances (before they become escapes)
- Warranty analysis showing early signals
- Process performance data from SPC showing drift before spec violations occur
- Outputs from Design FMEAs and Process FMEAs that flag high-RPN characteristics not yet producing defects
- Supplier quality trends that signal risk before a supplier nonconformance reaches your floor
If your quality system only generates corrective actions in response to customer complaints and audit findings, your CAPA process is incomplete. Preventive action requires a separate process input -- somewhere in your quality system, someone has to be looking at data and generating PA initiations before the customer calls.
How the Correct Module Handles Both
QualityEngineer.ai's Correct module manages both 8D investigations and CAPA workflows in one system. When a nonconformance comes in -- customer complaint, internal audit finding, supplier issue, warranty return -- it goes into the Correct module and gets triaged.
For CARs that need 8D format, the module walks through each discipline in sequence, prompts for required content at each stage, and links D7 actions directly to the relevant PFMEA and control plan records. When D7 updates propagate, the PFMEA and control plan update in the same system -- there is no separate document to manually revise and risk losing alignment.
For internal corrective and preventive actions, the module tracks status, assigns owners, sets review dates, and logs effectiveness evidence against each action. The CAPA register is built from these records automatically -- auditors see the log without needing you to compile it from individual files the morning of the audit.
The 8D report outputs to a formatted PDF in the common AIAG template. The CAPA register exports for audit packages or registrar review. Both feed the same underlying data model.
Summary
8D is a structured problem-solving methodology -- organized, disciplined, and widely accepted in the automotive supply chain. CAPA is a quality system requirement under IATF 16949 that covers both corrective and preventive action.
A rigorous 8D investigation satisfies the corrective action side of CAPA. But CAPA also requires preventive action, a documented procedure, a tracked log, and effectiveness evidence. An organization that only does 8D when customers complain is doing corrective action. It is not running a CAPA process.
Know the difference. Document the procedure. Build the preventive action inputs into your quality system before an auditor asks where they are.
QualityEngineer.ai's Correct module manages 8D investigations, CAPA workflows, and preventive action tracking in one system. Start free, no credit card required.
About the Author
Daniel Crouse is the founder of QualityEngineer.ai. 15+ years in supplier quality, PPAP, and manufacturing systems. Built QualityEngineer.ai because quality engineers deserve better tools than Excel. Connect on LinkedIn.
