Free 8D Report Template
Created by the 8Dflow team.
Use this 8D report template to work from the D2 problem statement and D3 containment record through D4 cause verification, corrective actions, implementation verification, effectiveness checks, prevention, and closure.
Download this 8D template in Word or Excel when a customer complaint, repeat defect, supplier issue, or significant internal nonconformance needs a documented D0–D8 response.
Free download · No signup · Editable Word and Excel versions
On this page
What is an 8D report?
An 8D report is a structured record of a team's D1–D8 problem-solving work. It documents the problem, immediate containment, occurrence cause, escape or detection weakness, corrective actions, implementation verification, effectiveness evidence and closure approval.
Use this template when an issue needs a formal 8D response rather than an NCR closed through local correction alone. It keeps the full response and supporting evidence in one report.
This template is built for manufacturing quality work, including:
- customer complaints;
- shipped product defects;
- repeat internal defects;
- supplier quality issues;
- inspection escapes;
- nonconformances that need cross-functional investigation;
- problems where the cause is unknown, disputed, or likely to recur.
It does not replace your company procedure or a customer-specific 8D form. It gives you a practical starting point for a complete 8D record.
8D report preview: from D0 triage to D8 closure
These screenshots are taken from the downloadable template. Open a preview to check the field order, evidence expectations, and D0–D8 flow before choosing the Word or Excel version.
Example records are fictional demonstration data.
01
Cover page and evidence guide
The first page is a check before the team starts writing. It covers when an 8D is the right response and what evidence should be in hand before the investigation moves to root cause.
Watch-out
Do not move straight to permanent corrective action before the problem, containment, and evidence are clear.
02
Report header and status summary
The header gives the reviewer the basic facts: source, part, revision, lot, defect, quantity, due dates, owner, and current status.
Watch-out
Do not leave affected quantity, suspect quantity, lot identification, owner, or response due date blank.
03
D2 problem definition, 5W2H, and Is / Is Not analysis
D2 keeps the problem factual before the team starts discussing possible causes. It captures the requirement, actual condition, scope, quantity, and what has been checked.
Watch-out
Do not put cause statements in D2. “Operator missed step” belongs in D4 only after evidence supports it; D2 should record the requirement, actual condition, location found, lot, and quantity.
04
D3 containment actions table
This table records the immediate actions taken to protect the customer and stop further escape while root cause is still being investigated.
Watch-out
Containment is temporary. Do not present containment as the permanent corrective action.
05
D3 product location and quantity check
This section shows where affected or suspect product was checked and what was found across customer stock, in-transit product, finished goods, work in progress, incoming material, and other sites.
Watch-out
Do not say “stock checked” without recording how much was checked, where it was checked, and what was found.
06
D3 customer and internal protection
This section records the actions used to protect the customer and the internal process while the 8D remains open.
Watch-out
Do not remove containment until permanent controls are implemented and checked.
07
D4 fishbone, 5 Whys, occurrence cause, and escape point
D4 separates why the problem happened from why the process did not detect it before escape. Both answers may need corrective action.
Watch-out
A brainstormed cause is not a root cause. Do not close D4 with guesses, opinions, or “operator error” without evidence.
08
D6 implementation verification and effectiveness plan
D6 records verification of implementation and a separate effectiveness check. It should show whether the approved changes were released and completed, and whether the action worked.
Watch-out
“Training completed” verifies one task; it does not show the corrective action was effective. Add results from the defined review window.
09
D8 closure checklist
The closure checklist confirms that the 8D is ready to close internally or send as a final customer response.
Watch-out
Do not close the 8D while containment is still open, the occurrence cause or escape point is unverified, or effectiveness evidence is missing.
10
Appendix C action tracker and common mistakes checklist
The appendix gives the team one place to track actions, owners, dates, status, evidence, and common issues to check before sending the report.
Watch-out
A good 8D can still fail review if actions have no owner, no due date, no evidence, or if the final customer response does not match the report evidence.
8D report sections quick reference
| Section | What it captures | Watch-out |
|---|---|---|
| Report header | Source, part, defect, lot, owner, due dates, and status | Do not leave affected and suspect quantity vague |
| D0 — Plan and prepare | Optional triage, risk, response due date, and decision to launch 8D | Do not launch an 8D without recording the trigger, risk level, owner, and response due date. |
| D1 — Team | People with product, process, supplier, and quality knowledge, plus authority to assign actions and approve the response | Avoid assigning a cross-functional issue to one person only |
| D2 — Problem description | Factual problem statement, 5W2H, Is / Is Not, requirement vs actual | Do not include assumed root cause |
| D3 — Interim containment | Customer protection, internal containment, sorted quantities, clean point | Containment is temporary |
| D4 — Occurrence cause and escape point | Verified occurrence cause, detection weakness, evidence, causes ruled out | Do not treat brainstormed causes as verified root causes |
| D5 — Choose corrective actions | Proposed actions tied to verified causes | Avoid “retrain operator” unless training was the supported cause |
| D6 — Implement and validate | Implementation verification, completion evidence, and effectiveness results from the defined review window | Do not treat action completion as effectiveness evidence |
| D7 — Prevent recurrence | Similar product/process review, document and control updates | Do not copy D5; look for wider system risk |
| D8 — Close and recognize | Closure checklist, final summary, residual risk, approval | Do not close with missing evidence or open containment |
| Appendices | Evidence log, customer communication log, action tracker | Make evidence easy to find later |
When to use an 8D report
An 8D is the right record when a local correction will not address the cause, escape point, recurrence risk, or formal response requirement. Use one when:
- a customer asks for a formal 8D response;
- the cause is unknown, disputed, or needs evidence;
- the issue affects shipped product, fit, form, function, safety, or customer use;
- the same defect keeps returning after quick fixes;
- containment, occurrence cause, escape point, corrective action, implementation verification, effectiveness, and prevention all need to be documented;
- more than one function is needed to solve the problem;
When a simpler corrective action record is the better fit
A full 8D may be more than you need when the cause is already known, the issue is low risk, the fix is local, and there is no customer requirement for an 8D.
In that case, use a corrective action plan, NCR, or simpler internal record. Reserve a full 8D for problems that require containment, cross-functional investigation, separate occurrence and escape analysis, effectiveness evidence, or a formal customer response.
Work through the 8D in order
Do not jump from D2 straight to action planning. Complete the early sections first: confirm the trigger, assign the team, define the requirement and actual condition, and record containment before moving into cause verification and corrective action.
D0 TO D3
Start with the decision, team, facts, and containment
D0 is optional. Some 8D formats start at D1. This template includes D0 as a triage step so the team can record why an 8D is needed, what risk exists, who owns the response, and when the initial or final response is due.
D1 should name the people needed to solve the problem. That usually includes quality, production, engineering, supplier quality, inspection, maintenance, or customer-facing roles depending on the issue.
D2 should describe the problem in factual, measurable terms. Use the part number, revision, lot, where found, requirement not met, actual result, affected quantity, suspect quantity, and evidence.
Do not put cause statements in D2. “Operator missed step” belongs in D4 only after evidence supports it; D2 should record the requirement, actual condition, location found, lot, and quantity.
D3 should record containment. This means the temporary actions taken to protect the customer and stop further escape while the investigation continues.
Good D2 entry
Apex Industrial returned 12 HSG-88 housings from HSG88-LOT-0726A that leaked at the seal interface during incoming test. DRW-HSG-88 Rev D requires the housing to seal at the mating face without leakage during the pressure hold test. Customer return documentation and incoming test records are attached.
Avoid
Customer received leaking housings due to assembly error.
D4
D4: prove the occurrence cause and the escape point
D4 fails when the report records an unsupported cause or never checks the escape point. The template separates two questions:
- 1Why did the problem happen?
- 2Why was it not detected before reaching the next process step or customer?
The first answer is the occurrence cause. The second is the escape point or detection failure. Both may need corrective action.
Use the fishbone diagram guide and 5 Whys guide to structure the cause checks, but do not call a possible cause the root cause until the evidence supports it. The evidence should show what confirmed the cause and what was ruled out.
The fishbone diagram template and 5 Whys template can be completed alongside D4 and attached as supporting evidence. For a full overview of the method, see the 8D problem solving guide.
Strong D4 entry
Occurrence cause: WI-ASSY-221 Rev C did not require a seal-orientation confirmation after the cleaning step, so a damaged or mis-seated seal could be installed before the pressure test. Evidence: EVD-120-04 WI-ASSY-221 Rev C gap review, EVD-120-03 seal inspection photos.
Escape point: IP-HSG-88 Rev B required final pressure testing but did not require a seal-face visual check before packing, so the team relied on the final test alone. Evidence: EVD-120-05 IP-HSG-88 Rev B review, EVD-120-02 leak test record.
Weak D4 entry
Root cause was assembly error. Retrained operator.
D5 TO D8
D5 to D8: choose actions, verify implementation, check effectiveness, prevent recurrence, and close
D5 should choose corrective actions that address the verified occurrence cause and the escape point. If the occurrence cause is a document control gap, the action should correct the document control gap. If the escape point is a missing inspection check, the action should correct the inspection control.
D6 should record verification of implementation and a separate effectiveness check. Do not stop at “work instruction updated” or “operator trained.” Verify that the approved changes were released and completed, then review the defined production window to confirm whether the action worked. Action completed is not the same as action effective.
D7 should look beyond the affected lot. Check similar products, similar processes, related work instructions, inspection plans, control plans, training records, supplier controls, maintenance plans, or PFMEA entries where relevant.
D8 should close the report only after the evidence supports closure. Confirm containment has been removed or replaced by permanent controls, corrective actions are implemented and verified, effectiveness criteria are met, D7 prevention actions are complete or formally transferred to a controlled action record with an owner and due date, the customer response has been sent if required, and approval is recorded.
Closure check
If the report still has open containment, an unverified occurrence cause or escape point, missing effectiveness evidence, or actions with no owner, it is not ready to close.
Manufacturing example: leaking housing customer return
This example shows the level of detail expected in an 8D record, including the triggering record, planned verification, effectiveness criteria, and the evidence required before closure.
| 8D area | Example entry |
|---|---|
| 8D report number | 8D-2026-042 |
| Triggering record | NCR-2026-120; CAR-2026-031 |
| Customer | Apex Industrial |
| Part | HSG-88 |
| Lot | HSG88-LOT-0726A |
| Problem | Apex Industrial returned 12 HSG-88 housings from HSG88-LOT-0726A that leaked at the seal interface during incoming test. |
| Requirement | DRW-HSG-88 Rev D requires the housing to seal at the mating face without leakage during the pressure hold test |
| Actual condition | HSG-88 housings from HSG88-LOT-0726A leaked at the seal interface during incoming test. |
| Containment | Held 48 suspect units from HSG88-LOT-0726A and related WIP and finished stock in the red-tag hold area; 100% seal-face visual check and leak test before release; containment completed 2026-07-03 |
| Affected quantity | 12 returned units confirmed nonconforming at customer |
| Suspect quantity | 48 suspect units from HSG88-LOT-0726A; related WIP and finished stock held for review |
| Linked corrective action | ACT-3012 (seal process) |
| Owner | Tom Alvarez |
| Due dates | Containment: 2026-07-03; customer response: 2026-07-10; WI/checklist update: 2026-07-17; verification: 2026-07-24; effectiveness review: 2026-08-21. |
| Evidence | EVD-120-01 customer return photos; EVD-120-02 leak test record; EVD-120-03 seal inspection photos; EVD-120-04 WI-ASSY-221 Rev C gap review; EVD-120-05 IP-HSG-88 Rev B review; EVD-120-06 retraining record. |
| Occurrence cause | WI-ASSY-221 Rev C did not require a seal-orientation confirmation after the cleaning step, so a damaged or mis-seated seal could be installed before the pressure test |
| Escape point | IP-HSG-88 Rev B required final pressure testing but did not require a seal-face visual check before packing, so the team relied on the final test alone. |
| Corrective actions | Update WI-ASSY-221 to Rev D and TC-SEAL-04 to Rev B; add seal-orientation confirmation and seal-face visual check; train assembly and test operators |
| Verification | By 2026-07-24, verify that WI-ASSY-221 Rev D and TC-SEAL-04 Rev B are released and the approved training is complete. |
| Effectiveness check | At the 2026-08-21 review, check the first three batches after release; target: no repeat leaks in 90 shipped units during the defined review window. |
| Closure decision | Close only after the 2026-08-21 effectiveness review is accepted, containment is removed, D7 prevention actions are complete or transferred to a controlled action record with an owner and due date, the customer response is sent, and approval is recorded. |
Weak vs strong 8D entries
A strong 8D entry states the requirement, the measurable condition, and the verified decision. A weak one stops at a vague note.
| Template field | Weak entry | Strong entry |
|---|---|---|
| Problem statement | Customer received bad parts | Apex Industrial returned 12 HSG-88 housings from HSG88-LOT-0726A that leaked at the seal interface during incoming test |
| Requirement | Part was not built correctly | DRW-HSG-88 Rev D requires the housing to seal at the mating face without leakage during the pressure hold test |
| Containment | Checked stock | Held 48 suspect units from HSG88-LOT-0726A and related WIP and finished stock in the red-tag hold area; 100% seal-face visual check and leak test before release |
| Occurrence cause | Operator forgot | WI-ASSY-221 Rev C did not require a seal-orientation confirmation after the cleaning step, so a damaged or mis-seated seal could be installed before the pressure test; evidence: EVD-120-04 WI-ASSY-221 Rev C gap review and EVD-120-03 seal inspection photos. |
| Escape point | Inspection missed it | IP-HSG-88 Rev B required final pressure testing but did not require a seal-face visual check before packing, so the team relied on the final test alone; evidence: EVD-120-05 IP-HSG-88 Rev B review and EVD-120-02 leak test record. |
| Corrective action | Retrain team | Update WI-ASSY-221 to Rev D and TC-SEAL-04 to Rev B, add seal-orientation confirmation and seal-face visual check, train assembly and test operators |
| Verification | Action done | By 2026-07-24, verify that WI-ASSY-221 Rev D and TC-SEAL-04 Rev B are released and the approved training is complete. |
| Effectiveness | No leaks seen | At the 2026-08-21 review, check the first three batches after release; target: no repeat leaks in 90 shipped units during the defined review window. |
| Closure | Closed after response sent | Closed after containment was removed, the occurrence cause and escape point were verified, corrective actions were implemented and verified, effectiveness criteria were met, D7 prevention actions were completed or transferred to a controlled action record, the customer response was sent, and approval was recorded. |
8D report mistakes to catch before sending
These are the mistakes that most often weaken an 8D or create problems at customer review.
| Mistake | Better practice |
|---|---|
| Problem statement includes assumed root cause | Describe only the facts: part, lot, defect, requirement, actual condition, location found, quantity |
| D0 does not explain why an 8D is needed | Record the trigger, risk, owner, and response due date |
| Containment is missing or vague | Record what was held, sorted, checked, released, replaced, or controlled |
| Affected and suspect quantities are not recorded | Separate confirmed nonconforming quantity from suspect quantity |
| Clean point is missing | Record the first known conforming lot, serial number, shipment, or production date where relevant |
| Occurrence cause and escape point are mixed together | Explain why the problem happened and why it was not detected |
| Root cause is a guess | Show the evidence that supports the cause and the causes ruled out |
| Corrective action does not match the verified cause | Tie each action directly to the occurrence cause or escape point |
| The record stops at action completion | Verify the action was implemented as planned, then record a separate effectiveness result from the defined review window. |
| D7 prevention is skipped | Check similar parts, processes, documents, suppliers, inspection controls, and risk records |
| Actions have no owner or due date | Assign an owner, due date, completion date, status, and evidence |
| Attachments are referenced but hard to find | Use a clear evidence log with file names, owners, and locations |
| Final customer response does not match the evidence | Confirm the reported occurrence cause, escape point, actions, and effectiveness results match what the attachments actually show. |
Use the format your customer requires. Before sending, remove internal guidance, verify that the evidence supports the conclusions and confirm that the response matches the current action status.
When Word and Excel 8D templates become hard to manage
Word and Excel work well for a single 8D report. They become harder when several reports are open, actions sit across different files, evidence is stored in email, and owners need follow-up before closure. At that point, the team needs a managed 8D record rather than separate files and email follow-up. 8Dflow is being built to keep the issue, actions, evidence, review, and closure decision together.
Download the free 8D report template
Download the Word or Excel file and use it as your D0–D8 working record for the next customer complaint, repeat defect, supplier issue, or internal nonconformance.