The 8D process is the automotive industry standard for corrective action — and it is routinely done badly. Here is a discipline-by-discipline guide with real examples and the mistakes that get 8Ds rejected.
The 8D (Eight Disciplines) process requires a cross-functional team and a structured report covering D0 (problem preparation) through D8 (team recognition and closure). Automotive customers typically require an initial 8D response with containment within 24 hours, and completed root cause and corrective action within 30 days. The most common 8D rejection reason: D4 (root cause) stops at "operator error" instead of reaching the systemic cause that made the error possible.
8D is a structured problem-solving methodology developed by Ford Motor Company and now the standard corrective action format across the automotive supply chain and many aerospace and defense applications. When a customer issues a SCAR or when an internal nonconformance requires a formal corrective action, 8D is the expected format.
8D is appropriate when: the problem is significant enough to warrant a structured, documented investigation; the root cause is not immediately obvious; the problem has or could have customer impact; or the customer specifically requests an 8D report format. It is not appropriate for every nonconformance — simple, immediately obvious problems are better handled through the NCR process without the overhead of a full 8D.
D0 is not always included in 8D discussions, but it is critical. Before forming a team and beginning the investigation, the problem-solving effort needs to be scoped.
D0 answers: Is this problem significant enough to warrant 8D? Do we have the right people available? What is the timeframe for customer response? What information do we need to gather before the team convenes?
For customer-issued SCARs, D0 also means reading the SCAR thoroughly, understanding exactly what the customer observed, and collecting the nonconforming parts or relevant production records before the first team meeting.
The 8D process requires a team with the knowledge and authority to investigate the problem and implement solutions. A single quality engineer writing an 8D alone is not 8D — it is a corrective action report formatted as an 8D.
The team should include:
Team members should be selected based on what they know, not based on availability or seniority. The most valuable team member for a specific problem might be a setup technician, not a manager.
D2 is the most underinvested discipline in most 8D reports. A well-written problem description is specific, objective, and based on evidence.
The problem description answers: What is the failure? What should have happened? What actually happened? What is the scope and magnitude? When was it first observed? Where in the process or which part numbers are affected?
Use the "Is / Is Not" technique to refine the problem description. For each dimension of the problem — what, where, when, how many — ask what the failure IS and what it IS NOT.
What: The failure IS under-torqued mounting bolts on P/N 4521-A. It IS NOT over-torqued. It IS NOT affecting P/N 4521-B or 4521-C.
Where: The failure IS at Station 3, Assembly Line 2. It IS NOT at Station 3, Assembly Line 1 (same process, different equipment).
When: The failure IS present in parts produced March 14-18. It IS NOT present in parts produced before March 14 or after March 20.
The "Is Not" boundaries are as important as the "Is" boundaries. They constrain the possible root causes and prevent the team from investigating in the wrong direction.
Containment is what you do immediately to protect the customer from the nonconforming condition. Containment is not a permanent fix — it is a temporary measure to stop the bleeding while root cause investigation continues.
Containment actions for a manufacturing problem might include:
Containment actions must be documented with: the specific action taken, the date implemented, the person responsible, and the results (how many parts were inspected, how many were nonconforming, what was done with the nonconforming parts).
The D3 response is typically the first deliverable to the customer — often within 24 to 48 hours of receiving a SCAR. Customers evaluate supplier responsiveness and seriousness based on the speed and thoroughness of D3.
D4 is where most 8D reports fail. "Operator error" is not a root cause. "Insufficient training" is not a root cause. These are symptoms. The root cause is the systemic, underlying reason why those symptoms exist and why the control system did not prevent or detect them.
Use 5-Why analysis or fishbone (Ishikawa) diagrams to drill to systemic causes. For each symptom, ask why five times — or until you reach a cause that, if addressed, would make the failure impossible to recur.
Example:
Root cause: The document control procedure does not require work instruction review when referenced drawings are revised, creating conditions where drawing changes are not reflected in work instructions.
This root cause, if addressed, eliminates the failure mode. An updated document control procedure that requires WI review with every drawing revision prevents the same sequence from recurring.
Corrective actions address the root cause — not the symptom. If the root cause is the document control procedure, the corrective action is updating the document control procedure, not retraining the operator.
For each root cause identified in D4, D5 defines:
Corrective actions should be specific enough that someone can verify they were completed. "Improve training" is not a corrective action. "Update training material for WI-3201 to include torque specification, retrain all Station 3 operators by [date], document training records for each operator" is a corrective action.
D6 verifies that the corrective actions from D5 were actually implemented and that they work.
Implementation validation is simple: can you produce objective evidence that each corrective action was completed? Updated procedure with approval signature and effective date. Training records for named operators. Updated control plan with new revision number.
Effectiveness validation is harder: can you produce objective evidence that the corrective action eliminated the root cause? Monitor the process for a defined period after implementation and document that the failure mode has not recurred. The monitoring period depends on production volume — enough parts to give statistical confidence that the problem is resolved.
D7 extends the corrective action to similar processes, parts, or products where the same root cause could produce the same failure. This step is frequently skipped, which is why the same type of nonconformance recurs at different part numbers or in different areas of the facility.
Ask: Where else in our facility could the same root cause — in this case, the same gap in document control — produce a similar failure? What preventive actions address those potential failures before they occur?
D8 acknowledges the team's effort and formally closes the 8D. It requires sign-off from the team champion — confirmation that all previous disciplines are complete and the problem is resolved.
D8 is also the trigger for closing the associated SCAR, CAPA record, and any related documents. The 8D is not complete, and the SCAR is not closeable, until D8 is signed.
Customers reject 8D reports for predictable reasons:
D2 is vague. "Parts did not meet specification" is not a problem description. Quantify the magnitude, scope, and boundary conditions.
D4 stops at symptoms. "Operator error" or "training issue" as root cause will be rejected by any experienced customer quality engineer.
D5 does not match D4. The corrective action must address the root cause. A corrective action that retrains the operator when the root cause is a documentation gap does not close the loop.
D6 has no effectiveness verification. Closing the 8D immediately after implementing corrective actions, before monitoring data shows the fix worked, gets the report returned.
D7 is blank. Most 8D reports leave D7 empty. Any customer quality engineer will ask what you are doing to prevent similar failures elsewhere.
Coplain Auditor Review helps you identify systemic documentation gaps before they become 8D requirements. Try free at coplain.com.
Coplain turns any work instruction into a print-ready, audit-proof job aid in minutes.
Try Coplain free →AS9100 Rev D Documentation Checklist: 12 Items Auditors Check First
Most audit failures aren't about process gaps. They're about documentation that doesn't reflect reality. Here's the checklist we wish existed before our first Rev D audit.
6 min readCOMPLIANCEFDA 21 CFR Part 820 Documentation Requirements: What Trips Up Manufacturers
Warning letters. 483 observations. Consent decrees. Most FDA enforcement actions have one thing in common: inadequate documentation. Here's what the agency actually looks for.
10 min readCOMPLIANCEISO 9001:2015 Documentation Guide: What You Actually Need vs What You Think
The 2015 revision eliminated the quality manual requirement and six mandatory procedures. What it added is more demanding. Here's what actually changed — and what your registrar looks for during surveillance.
7 min readRelated Tools & Templates
COPLAIN PLATFORM
See every tool that turns complex work instructions into floor-ready documents.