8D Report8D Report Builder

What an 8D has to prove

A customer asking for an 8D wants three things a 5 Whys cannot give them. That you contained the problem before you understood it. That you found both why it happened and why it escaped. And that you proved the fix worked before you dropped the containment. The nine disciplines are the order that argument has to be made in, which is why the dates matter as much as the words.

The reader is usually a supplier quality engineer with a stack of these on their desk. They check D0 and D3 first, because those show whether you protected them while you investigated. If your containment does not account for the parts already in transit and sitting on their line, the submission comes back before anyone reads your root cause.

Two root causes, not one

Most rejected 8D reports investigate only how the defect was made. D4 needs two answers: the occurrence cause — why the process produced it — and the escape cause — why inspection did not catch it before shipping. This builder puts the two chains side by side, because teams that write them together notice how different they are. The occurrence cause usually ends at a process or design decision. The escape cause usually ends at a control plan nobody updated.

A why-chain that ends at operator error will fail review. That names a person, not the part of the system that let the error reach the customer. Keep asking until you reach something you can change, then record how you verified it — ideally by turning the cause on and off and watching the defect follow.

The section everyone forgets

D7 read-across is the check for the same cause everywhere else it can live: other parts, other lines, other plants running the same fixture design or the same standard. It is the most commonly omitted section of an 8D and one of the most common reasons a report is sent back. A cause that was systemic enough to reach a customer once is rarely confined to the one line that shipped it.

Frequently asked questions

What is an 8D report?

An 8D report is a structured corrective action report used when a defect has escaped to a customer or a problem keeps coming back. It works through eight disciplines — D1 team, D2 problem description, D3 interim containment, D4 root cause, D5 permanent corrective action, D6 implement and validate, D7 prevent recurrence, D8 close and recognise — plus D0, the emergency response recorded before the team is even formed. The format originated with Ford and is used across AIAG member companies, so most automotive and many industrial customers request it by name.

Why are there nine disciplines if it is called 8D?

The original method had eight. D0 was added later to hold the symptom as the customer reported it and the immediate protective action taken before an investigation begins. The name stayed. In practice you fill nine sections, and a customer checking your report will look at D0 and D3 first because those show whether you protected them while you worked.

What are the two root causes in D4?

The occurrence root cause explains why the process produced the defect. The escape root cause explains why it was not detected before shipping. Most rejected 8D reports investigate only the first. Both matter, because fixing how the part is made without fixing how it is checked leaves the next defect free to escape by the same route. This builder gives each cause its own why-chain, its own verification and its own contribution, and every corrective action in D5 is tagged to one of them.

What is the difference between containment and corrective action?

Containment (D3) is temporary and protects the customer immediately — sorting, extra inspection, quarantining stock. Permanent corrective action (D5) removes the root cause so containment is no longer needed. The dates matter: containment must be in place and verified before corrective action starts, and it is removed in D6 only once the exit criteria you set in D3 are met. A report showing both on the same date reads as a fix written after the fact.

What is read-across in an 8D?

Read-across, sometimes called horizontal deployment, is the check for the same cause everywhere else it can live — other parts, other lines, other plants running the same process or the same fixture design. It is the most commonly omitted section of an 8D and a common reason a customer sends the report back, because a cause that was systemic on one line is rarely confined to it.

When should you use an 8D instead of a 5 Whys?

Use an 8D when a defect escaped to a customer or the field, when the problem is recurring or high risk, or when a customer or your own leadership requires documented corrective action. For a single-cause problem inside your own four walls that nobody is auditing, a 5 Whys is enough and much faster. The D0 gate in this builder asks the question directly so the choice is recorded.

Is this 8D tool free?

Yes. The builder runs in your browser with no sign-up — fill the nine disciplines, track containment and corrective actions with owners and dates, and export a print-ready report with a signature block for both approvers. A free editable Excel 8D template with the same structure is also available.

Related tools

• 5 Whys Builder — the why-chain on its own, for problems that never left your four walls
• Fishbone Diagram — widen the search before you commit to a chain in D4
• FMEA Builder — the document D7 sends you back to update
• A3 Problem Solving — the same story on one page, for an internal audience
• Pareto Chart — decide which recurring defect earns an 8D