There are two ways to respond to a rejected batch. One is to sort it, ship the good parts, and move on — and see the same defect again next month. The other is to contain it, find why it happened and why nobody caught it, fix both, and change the system so it cannot recur. The second way has a name and a shape: the 8D, eight disciplines that take a problem from "we have rejects" to "it is fixed and it will not come back", ending in a CAPA that makes the whole quality system smarter.
This guide explains 8D and CAPA in plain English for quality engineers and MRs working to IATF 16949 or ISO 9001. It is the "react and prevent" half of the quality loop; for the full picture see the pillar guide, What is quality management software?
8D — Eight Disciplines — is the structured problem-solving process. CAPA — Corrective and Preventive Action — is the set of actions it produces: the permanent fix for the root cause and the systemic change that stops recurrence. A good 8D always ends in a CAPA that changes something real — usually the FMEA and the control plan.
1. What are 8D and CAPA?
The 8D (Eight Disciplines) is a team-based, structured method for solving a problem and preventing its recurrence. It was formalised in the automotive industry and is the format most OEMs and Tier-1s expect when they raise a complaint. It runs as a sequence of disciplines, D1 through D8, each with a defined output, so a customer — or an auditor — can see exactly where the investigation stands.
CAPA (Corrective and Preventive Action) is the action set that comes out of the investigation: the corrective action that removes the root cause, and the preventive action that stops the same mechanism appearing elsewhere. In an IATF 16949 system the CAPA does not live in isolation — it is driven through change management and fed back into the FMEA and control plan.
An 8D is opened from a significant NCR (material or line rejection) or from a customer complaint. The rejection supplies the defect code and the facts; the 8D supplies the discipline to get past the symptom.
2. The 8 disciplines, D1 to D8
Each discipline has a job. Skipping one — the usual temptation is to jump from D3 containment straight to declaring the problem solved — is how a defect returns.
| Step | Discipline | What it delivers |
|---|---|---|
D1 | Build the team | A small cross-functional team with the process knowledge and authority to act, and a champion. |
D2 | Describe the problem | The problem stated in facts — what, where, when, how many — using 5W2H and is / is-not to bound it, not opinions. |
D3 | Interim containment | Immediate action to protect the customer — sort, quarantine, 100% inspection — and verify it works. |
D4 | Root cause & escape point | The verified occurrence cause (why it was made) and the escape point (why it was not detected). |
D5 | Permanent corrective actions | The chosen corrective actions, verified to resolve the root cause without new side effects. |
D6 | Implement & validate | The corrective actions put in place and validated with data that the defect is gone. |
D7 | Prevent recurrence | Systemic changes — update the FMEA, control plan, work instructions, standards and sister parts. |
D8 | Close & recognise | Confirm the problem is closed, capture lessons learned, and recognise the team. |
Many organisations add a D0 before D1 — an initial emergency-response action taken the moment the problem is known, before the team even forms. And two disciplines are quietly the most valuable: D4, because it insists on both an occurrence cause and an escape point, and D7, because it is the one that changes the system so the problem cannot recur.
3. Containment vs corrective vs preventive action
Three kinds of action live inside an 8D, and confusing them is the single most common reason a "closed" problem comes back. They do different jobs at different times.
| Action | What it does | Where in 8D |
|---|---|---|
| Containment | Stops the bleeding now — sort, quarantine, 100% inspect — to protect the customer. Does not fix the cause. | D3 |
| Corrective | Removes the root cause so the problem stops recurring on this issue. | D5–D6 |
| Preventive | Stops the same mechanism happening elsewhere — sister parts, other lines, future programs — by updating FMEA, control plan and standards. | D7 |
A useful mental model: containment buys time, corrective action fixes the problem, and preventive action makes the organisation smarter. Auditors probe exactly here — they will ask to see that a corrective action actually changed the process, not just added an inspection, and that the learning was spread to similar parts. A CAPA that only added a sorting step has contained, not corrected.
4. Root cause: 5-why and fishbone
D4 is where an 8D succeeds or fails, and two tools do most of the work. Neither is magic; both are disciplines for getting past the symptom.
- Ask "why" iteratively — about five times — from symptom to systemic cause
- Run two legs: why-made (occurrence) and why-not-detected (escape)
- Stop when the cause is something you can actually remove or control
- Organise candidate causes under the 6Ms
- Man, Machine, Method, Material, Measurement, Mother-nature
- Explore every branch before settling on a verified cause
The discipline that separates a real root cause from a guess is verification: you should be able to turn the cause on and off. If reintroducing the suspected cause reproduces the defect and removing it makes the defect disappear, you have the root cause — not just a plausible story. And a complete D4 always finds the escape point too: not just why the defect was made, but why the control plan and inspection did not catch it. Fixing only the occurrence leaves the detection gap open.
5. Linking the 8D to the FMEA and control plan
An 8D that closes without changing anything upstream is a report, not an improvement. The whole point of D7 is to feed the learning back:
- Re-score the FMEA. A defect that escaped means the failure mode's occurrence or detection was under-rated. The corrective action lowers occurrence; better detection lowers the detection rating — and the RPN should move. See the FMEA and control plan guide.
- Amend the control plan. A new mistake-proofing step, a tighter frequency, or an added SPC control belongs on the control plan so the line actually does it.
- Route it through change management. The CAPA becomes a change request — impact assessed, documents approved — that amends the FMEA and control plan under version control and, where significant, triggers a PPAP re-submission. See documents & change management.
- Update the defect map. Linking the defect code back to the FMEA failure mode makes the next occurrence traceable and keeps the Pareto honest.
6. A worked example (illustrative)
Here is an illustrative 8D on a plated bracket, condensed to show how the disciplines connect. The numbers and details are illustrative, for teaching only.
D2 problem: customer returned 3 lots of bracket for zinc plating peeling at the bend radius.
D3 containment: 100% sort of 3 suspect lots in stock and in transit; certified-good stock shipped to protect the line.
D4 root cause (why-made): 5-why → poor adhesion → surface not clean → degreasing bath below concentration → bath not titrated on schedule. Escape (why-not-detected): adhesion (bend/tape test) not on the control plan at the right frequency.
D5/D6 corrective: restore bath titration schedule with a log; validate with adhesion tests on 5 consecutive lots.
D7 prevent: add bath concentration as a control-plan check per shift; add a per-lot adhesion test; re-score the PFMEA (occurrence and detection down); update sister-part control plans.
Notice what closing this 8D actually changed: two control-plan lines added, a PFMEA re-scored, and the fix spread to sister parts. That is the difference between an 8D and a sorting exercise — and it is only sustainable when the NCR, the 8D, the FMEA and the control plan live in one system. This is the shape of a real deployment such as Kakade Laser or Shree Engineering.
7. When to open an 8D
Not every non-conformance justifies a full eight-discipline investigation — over-using 8D dilutes it. Use judgment, and let the Pareto guide you.
- The defect is significant, recurring, or a repeat cause on the rejection Pareto
- A customer has complained, returned parts, or issued a formal concern
- There is a safety, regulatory or high-severity FMEA characteristic involved
- A minor, one-off rejection can be reworked and closed
- A bounded, low-risk non-conformance is accepted under an approved deviation (AD)
- The cause is already known and controlled — record it, do not re-investigate it
- Rank defects by frequency and cost, not by whoever shouted loudest
- Attack the biggest recurring cause first — the top of the Pareto
- A repeat defect is a signal that containment was mistaken for correction last time
8. How Fast Quality Software runs 8D and CAPA
Fast Quality Software is the automotive QMS of the Fast Suite, built in Pune by Improsys under the Fast Technology brand and deployed cloud or on-premise. It runs the 8D as the hub of the closed corrective-action loop:
| Capability | How Fast Quality Software does it |
|---|---|
| NCR to 8D | A significant material or line rejection — or a customer complaint — escalates into an 8D report, carrying the defect code and the facts. See NCR, rejection & 8D/CAPA. |
| D1–D8 structure | The 8D captures team, problem description, interim containment, root cause, permanent corrective action, implementation, prevention and close, each as a tracked step. |
| Defect codes & Pareto | Defect masters give a common defect language; the rejection Pareto ranks recurring causes so the right problems become 8Ds. |
| CAPA through change | The CAPA is driven through change management — request, impact, document approval — amending the FMEA and control plan and triggering a re-PPAP where required. See documents & change management. |
| Complaint link | A customer complaint from Fast Complaint escalates natively into an 8D on the shared platform. See complaint to 8D. |
| AI on repeat defects | Dhruv AI clusters defect and 8D remarks into named recurring themes and summarises rejection PPM and repeat defects, so persistent causes surface early. |
Close the loop from rejection to a re-scored FMEA — in one system.
Fast Quality Software makes the 8D the hub of the closed loop: a rejection or complaint escalates into an 8D, the CAPA runs through change management, and the FMEA and control plan are amended — with a PPAP re-submission where required. Because inspection, NCR, 8D, FMEA and change all share one platform, closing an 8D actually changes what the line does next.
9. Frequently asked questions
See an 8D close the loop on your own rejection
A 30-minute demo — a rejection escalated into an 8D, root cause found, CAPA driven through change management, and the FMEA re-scored. Cloud or on-premise.