An 8D report template is a structured worksheet that walks a team through Ford’s eight disciplines — from emergency response (D0) through containment (D3), dual root cause analysis (D4), verified corrective actions (D5–D6), prevention (D7) and closure (D8). Below you’ll find free downloads in the AIAG-style layout customers expect, plus field-by-field guidance for each discipline. No signup, no email — direct download.

Download the 8D report template

All three formats cover D0–D8 with the header block (report #, dates, customer/part, champion) and per-discipline prompts — including the occurrence-vs-escape split in D4 that customer SQEs check first.

8D Template — Excel

Editable .xlsx with all nine disciplines as structured sections. Works in Excel, Google Sheets, and LibreOffice. Best for living reports updated over the 30-60 day cycle.

Download .xlsx

8D Template — Word

Editable .docx — best when the 8D is submitted as a formal customer document or embedded in a larger quality report.

Download .docx

8D Template — PDF

Printable A4 worksheet for kickoff meetings and war-room walls. Work by hand during sessions, then transfer to the Excel master.

Download .pdf

Worked 8D example

Want to see every field filled in? The complete guide includes a full worked automotive 8D from symptom to closure.

Read the guide

What each discipline needs

The template prompts you for these — here is what a reviewer (customer SQE or auditor) expects to see in each section:

DisciplineWhat must be in itMost common rejection reason
D0 SymptomSymptom exactly as the customer reported it + emergency action and dateSymptom rewritten in your words, losing the customer's framing
D1 TeamChampion, leader, members with roles — cross-functional, includes the process ownerA list of managers with no one from the line
D2 Problem5W2H: what, where, when, how many; is/is-not; measure vs targetA vague paragraph instead of quantified facts
D3 ContainmentAction protecting the customer NOW, % effectiveness, verification data"Operators instructed to be careful" — not a containment
D4 Root causeCause of occurrence AND cause of escape — each with evidenceEscape analysis missing entirely (the #1 rejection)
D5 Chosen PCACorrective action per cause + why chosen over alternativesRetraining listed as the permanent fix
D6 Implement & validateDates + before/after data + when containment was removedNo validation data, just "implemented"
D7 PreventionFMEA updated, control plan updated, similar products/processes coveredD7 left empty or repeating D5
D8 ClosureLessons learned, team recognition, champion sign-off, closure dateClosed without champion sign-off

The D4 rule that saves reports from rejection

Every defect has two root causes: why it happened (occurrence) and why your controls didn't catch it (escape). The template forces both. If your escape answer is "inspector missed it" — keep asking why: what about the inspection method made the miss possible?

See both chains in the worked example →

8D report, 8D form, 8D format, D8 — the same document

Customer portals and supplier quality manuals name this document inconsistently, and the request you receive rarely matches the phrase your QMS uses:

The template below covers D0 through D8 in the layout customers expect, so it answers all four requests. One caution: if your customer supplies their own 8D form, use theirs. A supplier corrective action that arrives on the wrong template gets returned before anyone reads the content, and the clock keeps running.

Tips for getting the most from the template

  1. Open the report on day one, not at the end. An 8D written retrospectively reads like fiction — and reviewers can tell. Fill D0–D3 in the first 72 hours. If you would rather be walked through the disciplines than stare at a blank sheet, the online 8D report generator asks for each field in order and flags the gaps that get reports returned.
  2. Quote the customer's symptom verbatim in D0. Your job in D2 is to translate it into facts; D0 preserves the original complaint.
  3. When the complaint covers several defect modes, rank before you analyse. One 8D per root cause — not one 8D for a basket of symptoms. Count the modes, then run a Pareto to pick the one worth D4, and say in D2 which modes you excluded and why.
  4. Don't write D4 from memory. Run the actual analysis — fishbone for breadth (how to build one), 5 Whys for depth — and paste the result. If the branch is contested, D4 belongs in a room with the process owner, not at your desk: the facilitation walkthrough covers who to invite and how to keep the chain honest.
  5. Containment is not correction. D3 protects the customer today (sorting, 100% inspection); D5–D6 remove the cause. If they look the same, D5 is wrong.
  6. D7 is where repeat complaints die. Update the FMEA and control plan, then check sister products and lines for the same weakness — that's what "systemic" means.
  7. Keep one Excel master per report. The 30-60 day cycle (see the facilitation guide) means many hands touch it — one living file beats five conflicting copies.

Frequently asked questions

What is an 8D template?

The standard form for the eight disciplines problem-solving method developed at Ford: one document that carries a problem from D0 (symptom and emergency response) through containment, root cause, permanent corrective action and prevention to D8 (closure). It exists because a customer needs a single auditable record of what went wrong and what you changed — the template is the audit trail, not a worksheet for thinking.

Is a D8 report the same as an 8D report?

Yes — “D8 report” is a common transposition and refers to the same document covering all eight disciplines, not to the eighth discipline alone. The same applies to “8D form” and “8D format”, which show up in supplier corrective action requests: all four phrases describe the same D0 to D8 record.

What should an 8D report template include?

All nine sections D0–D8 plus a header block: report number, date opened, customer and part reference, champion, and date closed. D4 must have separate fields for the cause of occurrence and the cause of escape.

What's the difference between occurrence and escape in D4?

Occurrence explains why the defect was created; escape explains why it reached the customer undetected. Both need their own why-chain and their own corrective action in D5. Most rejected 8Ds fail on a missing escape analysis.

When do I need a full 8D instead of a simpler analysis?

When a customer formally demands a corrective action response, when the defect left your factory, or when an auditor needs documented containment and validation. For internal-only problems, a 5 Whys session is usually enough.

Can I use the Excel template in Google Sheets?

Yes — upload the .xlsx to Google Drive and open with Sheets. Structure and sections are preserved.

Are the templates free for commercial use?

Yes. Customer responses, audits, client deliverables — no restrictions.

Related resources