Free 8D Report Template
The 8D (eight disciplines) report takes one customer complaint from emergency response to a verified, permanent fix. Start from a filled-in example, then write your own on the blank form: D0 to D8, with an is/is-not analysis and an action tracker.
What is in the pack
- Filled-in example first: a B2B complaint about shipments with wrong carton labels, D0 to D8
- Blank 8D form with a prompt for every discipline
- Is / is not analysis sheet for the problem description (D2)
- Action tracker with status dropdowns; overdue actions turn red
- The 8D report as a Word document, plus a printable PDF (example + blank)
Example: shipments with wrong carton labels
Illustrative example, not customer data. This is page 1 of the template; page 2 is the same report, blank.
| Discipline | Example |
|---|---|
| D0. Plan and emergency response | A retail chain's distribution centre (DC) reported 46 cartons in 3 deliveries (23 Feb to 1 Mar) labelled with the other size: 500 ml cartons labelled 750 ml and the reverse. Chargeback: $3,680. Same day: shipments to this customer held, 100% label-to-content scan before dispatch, corrected delivery list sent. A full 8D is needed: repeated deliveries, a chargeback and an unknown cause. |
| D1. Team | Champion: operations director. Leader: quality manager. Members: line 2 night shift lead, labelling systems analyst, warehouse lead, key account manager. |
| D2. Problem description | Since 23 Feb, cleaning spray cartons packed on line 2 for one retail customer carry the label of the other size: 46 wrong cartons reported, 3.9% of the 1,180 cartons shipped to that DC that week. Is / is not below. |
| D3. Containment | 1,420 cartons in our warehouse checked (18 wrong, relabelled); 610 cartons at the DC checked with the customer (9 more found; 55 relabelled there in total). Until the fix: one size per shift on line 2 and a 100% label scan. No wrong labels in deliveries from 4 Mar. |
| D4. Root cause | Occurrence: since 23 Feb the night shift prints the customer labels for both sizes in a batch and keeps them in one tray; at the size changeover, leftover labels of the first size went on cartons of the second, and the changeover checklist has no label clearance step. Verified: all 73 wrong cartons were packed within 40 minutes after a changeover. |
| D4. Escape point | The end-of-line check scans the bottle barcode, not the carton label against the bottle, so a wrong carton label passes. Verified: a seeded wrong label passed 10 times out of 10. |
| D5. Permanent corrective actions | Occurrence: print each customer label on demand when the bottle is scanned, so only the right label exists (trial: 600 cartons, 0 wrong). Escape: end-of-line check compares the carton label with the bottle; a mismatch stops the line (seeded test: 20 of 20 caught). |
| D6. Implement and validate | Live on 16 Mar, all three shifts trained. Containment removed on 30 Mar. Four weeks after go-live: 0 wrong-label complaints on 5,240 cartons; the new check stopped 3 mismatches before dispatch. |
| D7. Prevent recurrence | Label clearance added to the changeover checklist on all lines; print-on-demand rolled out to line 1 and the 4 other customers with their own label format; "wrong carton label" added to the packing process FMEA; work instruction updated. |
| D8. Recognise the team | The customer accepted the report on 14 Apr. The operations director thanked the team at the monthly all-hands; the night shift lead presented the fix to the other lines. |
D2: is / is not
| Is | Is not | Distinction / what changed | |
|---|---|---|---|
| What | Carton label shows the other size | Bottle labels; other products | Only the carton label is applied separately |
| Where | Line 2; cartons for this customer | Line 1; other customers | This customer's label is printed on a desktop printer and applied by hand |
| When | From 23 Feb; night shift; within 40 minutes after a size changeover | Before 23 Feb; day shift | Since 23 Feb the night shift runs both sizes |
| How many | 46 reported; 73 found (55 at the DC, 18 in our stock) | Earlier deliveries | All 73 packed right after a changeover |
How to write a good 8D report
- 1Start D0 the same day: protect the customer first, then decide whether the problem needs a full 8D.
- 2Keep the team small (4 to 6 people) and cross-functional, with one leader and a champion who can clear obstacles.
- 3Describe the problem with is / is not before anyone names a cause. The differences between "is" and "is not" point to what changed.
- 4Find two causes: why it happened (occurrence) and why your checks did not catch it (escape point). Verify both with data.
- 5Choose permanent actions for both, test them before rollout, and remove containment only when the data shows the fix works.
- 6Prevent recurrence on similar lines, products and customers, update procedures and the FMEA, and thank the team before you close.
When to use an 8D report
Use an 8D when a customer complaint needs a documented, permanent fix: a repeat problem, a safety or cost impact, or a customer who asks for the report. For a quick, single-cause problem, a 5 Whys is often enough; to track the actions of any analysis to closure, use a corrective action plan.
Related free templates
Frequently asked questions
Is the 8D report template free?
Yes. The printable PDF downloads without an email. The Excel pack and the Word 8D report are sent to your email for free.
What does 8D stand for?
Eight disciplines: the steps D1 to D8 of a team-based problem-solving method, plus D0 for planning and the emergency response. It comes from the automotive industry and is now used wherever a customer complaint needs a documented, permanent fix.
What is an escape point in an 8D?
The earliest point in your process where the problem should have been caught, but was not. An 8D fixes both the root cause and the escape. In the example, the end-of-line check read the bottle barcode, not the carton label.
Is an 8D the same as a corrective action plan (CAPA)?
No. An 8D is a team method and report for one customer complaint, from emergency response to recognition. A corrective action plan tracks the actions and checks that they worked. Many teams use both: the 8D for the investigation, the CAPA plan to track the actions to closure.
How long should an 8D take?
Customers often set the deadlines. A common rhythm: containment (D3) within 24 to 48 hours, root cause (D4) within one to two weeks, and closure once the fix is validated, often 30 to 60 days later. The example ran from 2 Mar to 14 Apr.
Is there a Word, Excel or Google Sheets version?
Yes. The pack has an Excel workbook with four sheets and a Word version of the 8D report. For Google Sheets, upload the .xlsx file to Google Drive and open it with Google Sheets; the dropdowns and overdue highlighting carry over.
What if the same complaint shows up in thousands of tickets or reviews?
Then D2 and D4 need the full picture, not a sample. Pivony runs root cause analysis on all of your customer feedback.
Have thousands of complaints, reviews or tickets?
Pivony runs root cause analysis on all of your customer feedback, not a workshop sample.
Get a free root cause audit