What Is Root Cause Analysis and the 8D Report?
Also known as: 8D, 8D report, eight disciplines, 5 whys, RCA
Definition
Root cause analysis finds the underlying reason a defect occurred, not just the symptom. The 8D report (eight disciplines) is the structured format automotive and aerospace customers use to document team, containment, root cause, corrective action and prevention.
Root Cause Analysis and the 8D Report Explained
The eight disciplines are: D1 form a team, D2 describe the problem, D3 implement interim containment, D4 identify and verify root causes (including why it escaped detection), D5 choose permanent corrective actions, D6 implement and validate them, D7 prevent recurrence by updating systems, FMEAs and control plans, and D8 recognise the team and close. Some versions add D0 to decide whether an 8D is warranted at all.
Inside D4, teams use tools such as the 5 whys, an Ishikawa (fishbone) diagram, is/is-not analysis, and fault tree analysis. A good root cause statement names a mechanism that is testable. Operator error is not a root cause, it is a stopping point. Asking why the process allowed the error, such as a missing poka-yoke or an ambiguous work instruction, usually reaches a fixable system cause.
Ford originated the format and it became standard through IATF 16949 supply chains, where customers issue 8D requests after returns or line stops with response deadlines, often a 24 hour containment and a 10 to 30 day full report. Aerospace primes use similar corrective action requests under AS9100 clause 10.2.
ERP and QMS tools hold the 8D as a linked record: the originating customer complaint or supplier NCR, the affected items and lots, containment inventory actions and the updated FMEA or control plan references. The ERP matters most for D3, because containment means finding every affected lot in stock, WIP and shipped, which depends on lot genealogy.
Why It Matters
- Customers can put a supplier on controlled shipping or new business hold for late or weak 8D responses.
- Fixing the symptom rather than the cause leads to repeat returns and repeat 8Ds on the same defect.
- D7 forces lessons back into FMEAs, control plans and work instructions so similar parts are protected too.
- Containment speed depends on lot and serial traceability in the ERP, which is why genealogy gaps show up during 8Ds.
In Practice
A customer returns 12 connectors with intermittent opens. D3: the team uses ERP lot genealogy to find 3 sibling lots, quarantines 2,400 pieces in stock and recalls 600 shipped. D4: the 5 whys trace to a crimp height drifting after tool wear, and the escape cause is that the crimp pull test sample was once per shift. D5/D6: add a crimp force monitor and move pull testing to hourly. D7: update the PFMEA and control plan.
Frequently Asked Questions
What are the 8 disciplines in an 8D report?
Team, problem description, interim containment, root cause (and escape point), permanent corrective action, implementation and validation, prevention of recurrence, and team recognition and closure.
What is the difference between 8D and CAPA?
8D is a specific report format with fixed steps, often demanded by customers. CAPA is the broader quality system process. An 8D is commonly the way a CAPA is documented for a customer issue.
How many whys are enough in the 5 whys method?
Five is a guide. Stop when you reach a cause that you can verify and that a system change can remove, usually a process, tooling or control gap rather than a person.
What is the escape point in an 8D?
It is the place the defect should have been caught but was not, such as an inspection step with too small a sample. Fixing it protects you even if other causes remain.
Related Terms
CAPA (Corrective and Preventive Action)
CAPA is a closed-loop quality process: investigate a problem, find its root cause, implement corrective action to remove it and preventive action to stop similar problems, then verify the actions were effective. Required by ISO 13485 and FDA rules, expected under AS9100.
FMEA (Failure Mode and Effects Analysis)
FMEA (Failure Mode and Effects Analysis) is a structured risk assessment that identifies how a product or process can fail, the effects and causes of each failure, and existing controls, then prioritizes actions to prevent the highest-risk failures.
Traceability
Traceability is the ability to follow the history, location, and application of a part or material through the supply chain and production process, both backward to its sources and forward to every product and customer it reached.
IATF 16949
IATF 16949 is the automotive industry quality management system standard, published by the International Automotive Task Force, that supplements ISO 9001 with automotive-specific requirements and must be implemented together with ISO 9001 rather than on its own.
Poka-Yoke
Poka-yoke is a mistake-proofing technique that designs a process or fixture so a human error either cannot occur at all or is detected immediately, before it becomes a defect passed to the next operation.
Go Deeper
How to Manage Corrective Actions (CAPA) in SyteLine
Complete guide to managing CAPA (Corrective and Preventive Actions) in Infor SyteLine. Configure root cause analysis workflows, action tracking, effectiveness verification, and 8D problem-solving integration.
SyteLine Supplier Quality Management
Configure SyteLine supplier quality management for vendor quality scoring, incoming inspection tracking, and supplier corrective actions in CloudSuite Industrial.
Working with Root Cause Analysis and the 8D Report in a live environment? Our engineers do this every day - and our AI agents automate most of it.