8D report template: Eight disciplines. One clear report.
An 8D report is how a supplier shows a customer that a problem is contained, its root cause found and proved, and the fix made permanent. Download the template as Excel, PowerPoint or print-ready PDF, or fill it in right here in your browser. Free, no sign-up, no email.
What is an 8D report?
8D, the eight disciplines, is a structured problem-solving process that Ford published for its suppliers in 1987 and that the automotive and aerospace industries have used ever since. The 8D report is its record: one document that follows a problem from the first emergency response to the closed loop, with a section for each discipline. Customers ask for it after a complaint because it answers the questions they care about, in order.
Is the problem contained?
Which parts are suspect, how they are sorted, and from which breakpoint shipments are clean.
Is the root cause proved?
Not a list of possible causes: evidence that one cause switches the problem on and off.
Is the fix permanent?
A corrective action verified in a trial before it is implemented, and validated with data after.
Can it happen again?
Systems, documents and similar products updated, so the same cause cannot act elsewhere.
8D is a communication system between supplier and customer. It keeps the work visible and checkable: that the investigation is moving, that progress to the root cause is timely, that the cause is verified and the corrective action proven. What it does not do is tell the team how to find the cause.
The eight disciplines, and what each one must show
Every discipline ends with something the customer can check. The template has a box for each; the notes below say what belongs in it, and where reviewers look first.
- D0
Emergency response
Acknowledge the problem, protect the customer the same day — stop shipment, sort, replace — and decide whether a full 8D is needed. Certain impacts call for an immediate emergency response before any team exists.
Show: Date and content of the notification to the customer; emergency actions taken and their result.
- D1
Establish the team
A small, dedicated team: one leader who develops the strategy and drives it to the cause, one sponsor who removes roadblocks, provides resources and keeps the customer informed, and subject-matter experts only when needed.
Show: Names, roles and contacts of sponsor and leader; team composition reviewed at the start of each discipline.
- D2
Describe the problem
One failure mode, in measurable terms: what is wrong with what, where in the process it is first observed, since when, how many parts, and what it costs in quality, reliability and productivity.
Show: Discovery point, failure mode, quantities and impact in financial terms; an IS / IS NOT table narrows the focus.
- D3
Interim containment
Sort suspect parts as far upstream as possible, on a criterion that demonstrably predicts the customer’s experience, and name the breakpoint from which every shipment is protected. The further upstream, the stronger the protection and the smaller the waste.
Show: Process step and sorting criterion with the evidence behind it, a measurement system check, the breakpoint, and the counts inspected and rejected.
- D4
Root cause and escape point
The cause–effect relationship that explains the difference between good and bad parts, proved by switching the problem on and off with the suspected cause — plus the escape point: the last control that should have caught the problem, and why it didn’t.
Show: Verification data with sample sizes and statistical confidence; the escape point; the management-system weakness that let the cause exist.
- D5
Choose and verify the corrective action
Map how the cause drives the output, set a tolerance or control for it, choose the action together with the operators who will live with it, and show in a trial that it improves the output before it is implemented.
Show: The relationship between cause and output, the chosen tolerance, and trial results that demonstrate the improvement.
- D6
Implement and validate
Implement the action as a project, prove its effect with a run chart of the output before and after, update standard work so the fix cannot be undone, and remove the containment once it stops finding suspect parts.
Show: Implementation status, the before-and-after run chart, the date from which production is defect-free, and the customer’s concurrence.
- D7
Prevent recurrence
Fix the system that allowed the cause: procedures, standards, FMEA and control plan — and read across to similar products, processes and plants, with the insight passed to engineering for future designs.
Show: Updated documents with dates, read-across actions, and run charts from the other processes where the new control was applied.
- D8
Close and recognize
Record the business result, recognize the team, pass on the lessons about how the cause was found, and get the customer’s sign-off that the investigation can be closed.
Show: Impact in money, PPM or customer status; lessons learned; the customer’s sign-off with name and date.
Download the 8D report template
Three formats, the same nine sections, plus an online version. Free for your own and your company’s use: rename it, add your logo, adapt the fields. No sign-up, no email.
-
Excel workbook
.xlsxOne sheet to fill in, print-ready for A4 and Letter, with drop-downs for status and yes/no fields and a guide sheet listing the evidence each discipline needs.
-
PowerPoint deck
.pptxOne slide per discipline for customer reviews and management updates, 16:9, with the same fields and tables as the workbook.
-
PDF for printing
.pdfPrint it and fill it in by hand at the line or in a review meeting. Two page sizes.
-
Online form
in your browserNothing to install. The form saves itself in your browser as you type; print it or save it as a PDF when the report is ready.
The files are provided free of charge for use within your organization, including commercial use. They may be adapted; they may not be sold or offered for download elsewhere. No warranty: see the Terms of Use. Files updated .
Fill in an 8D report online
The same template as a web form. It saves as you type — in your browser only; nothing is sent to us or to anyone else. When the report is ready, print it or save it as a PDF, or copy it as text into an email or a ticket.
- Autosaves in your browser; reopen the page and continue where you left off.
- Print or save as PDF from the browser, with every box sized to its content.
- Copy the whole report as plain text for an email, a ticket or a customer portal.
- No account, no upload, no tracking of what you type.
Where 8D reports stall
D4 asks for a verified root cause. It does not say how to find one.
Three of the eight disciplines are only as good as the fourth. A containment that keeps finding bad parts, a corrective action that retrains operators and adds inspection, a problem that comes back — all of them trace to a D4 written from opinion rather than evidence. The usual way to fill it in is to study the symptoms, list the inputs that could explain them and pick the most plausible. That is asking what’s wrong. It depends entirely on the diagnosis, it produces long lists of candidate causes, and it often misses the input that is actually causing the problem.
Asking what’s wrong
From suspected inputs to the symptom
- Study the symptoms
- List the inputs that could explain them
- Test the favourites; fix the one that seems to work
Many candidate causes, a long list of actions, a root cause that is rarely proved.
Asking what’s different
From the measured output back to its cause
- Start from the measurement that defines the problem
- Contrast the best and the worst parts
- Eliminate what cannot be the cause; converge on the one that is
- Prove it by switching the problem on and off
One dominant cause — the Red X® — found by elimination and confirmed with evidence.
Five signs an 8D is stuck
- Containment is still finding suspect parts weeks after D3.
- D4 lists several “possible causes” and no experiment.
- The corrective action is retraining, awareness or more inspection.
- Nobody can switch the problem on and off at will.
- The same failure mode has had an 8D before.
If two of these apply, the report needs evidence, not more boxes. That evidence is what Shainin’s Red X® experts produce: the dominant cause, found from the parts themselves and proved with a confirmation test the customer can repeat.
8D vs. A3, CAPA and the rest
8D is one of several formats for a structured response to a problem. They differ in who asks for them and what they are for — and none of them finds a cause by itself.
| Format | Asked for by | Best for | What it does not do |
|---|---|---|---|
| 8D report | Automotive and aerospace customers after a complaint; required by many supplier quality manuals | Escaped defects that need containment, a proved cause and the customer’s sign-off | Say how to find the root cause in D4 |
| A3 report | Lean organizations, for their own improvement work | Telling an improvement project on one page, with the PDCA cycle | Formal containment and customer sign-off |
| CAPA record | Regulated industries under ISO 13485 and FDA quality-system rules | An auditable trail of corrective and preventive action | Guide the investigation itself |
| 5 Whys, fishbone | Any team, usually inside D4 | Listing candidate causes and structuring a discussion | Verify which candidate is the cause |
| Red X® problem solving | Teams facing a recurring technical problem, inside D4 and D5 | Finding and proving the dominant cause from the parts themselves | Replace the report: its results go into D4 and D5 |
IATF 16949 asks every automotive supplier for a documented problem-solving process — with containment, root cause analysis, systemic corrective action and verified effectiveness — and for the customer’s own format wherever one is prescribed. For most OEMs that format is an 8D.
8D report FAQ
What is an 8D report?
An 8D report documents a team’s response to a defect or customer complaint in eight disciplines: the team, the problem description, interim containment, the verified root cause and escape point, the chosen and verified corrective action, its implementation and validation, prevention of recurrence, and closure with recognition of the team. Most versions add a D0 for the emergency response. Customers in the automotive and aerospace supply chains ask for it so that containment, cause and fix are visible and verifiable.
What are the eight disciplines?
D1 establish the team; D2 describe the problem; D3 develop interim containment; D4 find and verify the root cause and the escape point; D5 choose and verify the permanent corrective action; D6 implement and validate it; D7 prevent recurrence; D8 recognize the team and close. D0, planning and emergency response, was added later and is now part of most templates, including this one.
Who developed 8D?
Ford Motor Company. Its manual “Team Oriented Problem Solving” (TOPS) of 1987 described the eight disciplines for Ford’s suppliers; the approach drew on the US military standard MIL-STD-1520 for corrective action on nonconforming material. In the late 1990s Ford’s Global 8D added the D0 step and the escape point. The method has since become the standard complaint response in the automotive industry and beyond; the German VDA published its own 8D volume in 2018.
When is an 8D report required?
Whenever a customer asks for one, typically after a complaint, a field return or a line stoppage; many automotive and aerospace supplier manuals prescribe it. IATF 16949 requires a documented problem-solving process with containment, root cause analysis, corrective action and verified effectiveness, in the customer’s format where one is prescribed. Internally, an 8D is worth the effort for any problem that reached the customer or keeps coming back.
What is the escape point?
The last point in the process that should have detected the problem and did not: the inspection, test or control that let the defect escape to the customer. Global 8D asks for it in D4 next to the root cause, because a problem has two causes — why it occurred and why it was not caught — and both need a corrective action.
How do you verify a root cause?
By showing that the problem can be switched on and off: set the suspected cause to its bad level and the defect appears, set it back and the defect disappears, on enough parts that the result is not chance — for most problems a risk of a false conclusion of 5% or less. A root cause that is only agreed on in a meeting, or supported by a 5 Whys chain without data, is not verified. Customers reject more 8Ds at D4 than at any other step.
What is the difference between D5 and D6?
D5 chooses the permanent corrective action and verifies it before implementation: a trial or designed experiment shows that the change improves the output. D6 implements it in production and validates it afterwards with data — a run chart of the output before and after — then removes the interim containment once it stops finding suspect parts.
When can the interim containment be removed?
After D6: when the permanent corrective action is implemented and the containment has stopped finding suspect parts or material. Keep the breakpoint and the containment records; many customers want them in the closed report.
How long should an 8D take?
Customers set their own clocks, and they differ. A common pattern is an emergency response and acknowledgement within 24 hours, interim containment within a few days, a verified root cause and corrective action within a few weeks, and closure once the validation data are in. The step that stretches the schedule is almost always D4.
Is this template free, and can we use it in our company?
Yes. The Excel, PowerPoint and PDF files and the online form are free for use within your organization, including commercial use, and may be adapted — add your logo, rename the fields, translate them. They may not be sold or offered for download on other sites. If the template does not get your 8D past D4, talk to a Shainin expert.
Sources: ASQ, “What is 8D (eight disciplines)?”; VDA QMC, “8D – Problem Solving in 8 Disciplines: Method, Process, Report”, 1st edition, 2018; IATF 16949:2016, clause 10.2.3 “Problem solving”; Shainin, “8 problem-solving methods compared: which one fits your problem?”; Ford Motor Company, “Team Oriented Problem Solving”, 1987, and Global 8D.
Stuck at D4?
Shainin’s Red X® experts find and prove the dominant cause of a problem, so the 8D closes on evidence — and the customer signs it off.