What is an 8D report?
An 8D report is the written record of the eight disciplines (8D) problem-solving process. Suppliers usually send it to a customer after a complaint to show how they contained the defect, fixed the root cause and prevented recurrence. Think of it as the case file for a defect: every decision, test and owner sits in one place.
The method is widely reported to have been developed at Ford in the 1980s, under the name Team Oriented Problem Solving (TOPS). The American Society for Quality (ASQ) describes 8D as a problem-solving approach commonly used in the auto industry. ASQ also notes that some organizations add an optional D0 planning stage.
A good 8D report does three jobs:
Customer communication: It shows the customer what you did, who owns each action and when it closes.
Root cause proof: It records the evidence behind the confirmed cause, so the fix is grounded in data.
Prevention record: It lists the process and document changes that stop the problem from returning.
The 8 disciplines of the 8D method
The 8D methodology runs through eight disciplines, D1 to D8, plus an optional D0 for planning. Each discipline produces a written section, so the finished report shows what the team decided and the evidence behind it. Work through the 8D steps in order, because each one builds on the last.
D0: plan and emergency response
Someone assesses the symptom and decides whether a full 8D is justified. If customers or safety are at risk, emergency actions such as a shipping stop start right away. Write down the symptom, the emergency actions and the decision to open the 8D.
D1: form the team
Pick a small cross-functional team with product and process knowledge, usually from quality, production, engineering and maintenance. Name one team leader and a champion from management who can unlock resources. Record names, roles and responsibilities.
D2: describe the problem
Describe the problem in measurable terms and leave causes for D4. Tools such as 5W2H (who, what, where, when, why, how, how many) and an is/is not analysis keep the description precise. Write down the defect, affected part numbers, quantities, lots, where it was found and how it was detected.
D3: contain the problem
Containment is temporary and does not remove the cause. The team protects the customer right away by quarantining stock, sorting suspect parts or adding 100% inspection. Record each containment action, its owner, the quantities checked and the results, and keep it running until D6 validates the permanent fix.
D4: find and verify the root cause
Find and document two root causes: why the defect occurred and why your controls let it escape. Use the 5 whys or a fishbone diagram to form hypotheses, then prove each one with tests or data.

D5: choose and verify permanent corrective actions
Choose permanent corrective actions that remove each verified root cause, for both occurrence and escape. Before rollout, prove on a small scale that each action works and does not create new problems. Record the chosen actions, alternatives considered, owners and verification results.
D6: implement and validate
Implement the permanent actions and validate them with production data, such as test results from new lots. Once the fix holds, remove the D3 containment in a controlled way. Write down implementation dates, validation evidence and the date containment ended.
D7: prevent recurrence
Stop the same problem from appearing elsewhere. Update the FMEA, control plan, work instructions and training, then check similar parts, lines and plants for the same weakness. Record every updated document and each place the lessons were applied.
D8: close and recognize the team
Confirm with the customer that the actions worked, then formally close the report. Recognize the team's work so people stay willing to take on the next 8D. Record the closure date, the customer's sign-off and the lessons learned.
8D report example from production
Here is a complete 8D report example for a leaking pump housing caused by wrong bolt torque. Hartwell Components, a fictional supplier, assembles PH-210 pump housings with a cover, an O-ring seal and four M8 flange bolts. A customer found six pumps leaking at the cover during their own end-of-line test.
D0 and D1: The quality lead stopped shipments and formed a team from quality, assembly, maintenance and test engineering.
D2: Six of 1,200 housings in lot 2417 leaked at the cover seal. All six came from assembly station 3.
D3: The team quarantined stock at Hartwell and the customer. Every housing was leak-tested at 2 bar before release.
In D4, the team ran the 5 whys twice. The occurrence chain looked like this:
The pump leaked because the O-ring seal was not compressed evenly.
The seal was uneven because the flange bolts were torqued to 18 Nm instead of the specified 25 Nm.
The bolts were low because the new nutrunner at station 3 ran the wrong torque program.
The wrong program went unnoticed because no one checked the torque after the tool change.
Nobody checked because the tool change procedure had no first-part torque check.
The escape chain explained why Hartwell's own test missed the leak:
The defect passed because the end-of-line leak test did not detect it.
The test missed it because its pressure was lowered to 0.5 bar during a trial and never reset.
The setting stayed because leak test parameters had no change control.
The team then closed out the case:
D5: The team added a first-part torque check after every tool change and put test parameters under change control. Trial runs confirmed both.
D6: Maintenance set the nutrunner to 25 Nm and reset the test to 2 bar. Containment ended after three clean lots.
D7: The team updated the process FMEA, control plan and tool change instruction, then checked the two other nutrunner stations.
D8: The following six lots passed the 2 bar test with no leaks. The customer confirmed there were no new complaints and accepted the closure.
8D report template
Copy the fields below into your own document and fill in one discipline at a time. If your customer requires their own 8D form, use it and treat this 8D report template as a content checklist.
Header fields
8D number
Customer
Customer complaint reference
Part number and name
Complaint date
Team lead
Champion
Status
Target close date
Discipline fields
D0 plan: symptom, emergency response, decision to open an 8D
D1 team: members, roles, team lead, champion
D2 problem: 5W2H, is/is not, quantities, lots, detection point
D3 containment: actions, owner, quantities sorted, results, start and end dates
D4 root cause: occurrence cause, escape cause, analysis method, verification evidence
D5 corrective actions: chosen actions, alternatives, owner, verification result
D6 implementation: implementation date, validation data, containment removal date
D7 prevention: updated FMEA, control plan, work instructions, similar parts checked
D8 closure: customer sign-off, closure date, team recognition, lessons learned
Short, factual entries help the customer review the report more quickly and allow auditors to trace each decision.
8D report vs corrective action plan vs FMEA
An 8D report is reactive and formal: it addresses a defect that has already occurred, often at the customer's request. A lighter corrective action plan suits smaller internal issues, while a preventive FMEA risk analysis finds failure risks before production starts.
8D report: Use it for customer complaints, repeat defects or safety issues that need a cross-functional team and documented proof.
Corrective action plan: Use it when the cause is clear and a few owners can fix it without a full team investigation.
FMEA: Use it during design and process planning to rank risks and add controls before parts reach customers.
The three tools work together. D7 feeds what the 8D revealed back into the FMEA, so the next risk analysis starts with better knowledge.
How to track 8D actions in MeisterTask
MeisterTask tracks the actions that result from an 8D, so each one has an owner and reaches verified closure. It is not dedicated 8D or CAPA software and does not produce 8D forms. Your team still does the analysis, and MeisterTask keeps the follow-up visible.
Step 1: Set up one project per 8D case
Create one project for each 8D case, named with the 8D number and part. Add sections for each discipline or status sections such as Open, In progress, Verify effectiveness and Closed. Either way, the board shows where every action stands.
Step 2: Turn each action into a task
Turn every containment, corrective and preventive action into a task with one assignee and a due date. In the Hartwell case, the nutrunner task could hold a checklist for calibration, first-part check and sign-off. Add the 8D number to the task description or a custom field so actions stay traceable.
Step 3: Schedule the effectiveness check
Create a recurring task for the D7 and D8 effectiveness check, for example, every week. The assignee logs leak test results in the task comments, which builds an audit trail. Once the agreed number of clean lots has been logged, the quality lead closes the case.
Step 4: Automate the hand-off
Automations in MeisterTask are rule-based: you define a trigger and an action. Set a rule that notifies the quality lead when a task moves into the Verify effectiveness section. The projects overview then shows deadlines and progress across all your 8D cases.
MeisterTask is hosted in Germany and certified to ISO/IEC 27001:2022, which matters when suppliers handle customer complaint data. Read more about project management for manufacturing with MeisterTask.
Common 8D mistakes
Most weak 8D reports break down in the same four places. Each one leaves the customer exposed to a repeat defect, even when the paperwork looks complete.
Treating containment as the fix: Sorting parts is the bucket under the leak. The repair happens in D5 and D6.
Guessing the root cause: A cause identified in a meeting without tests or data often recurs as a complaint.
Spreading ownership: Actions owned by "quality" or "the team" stall, so assign each one to a single named person and set a date.
Closing before verification: Close the case only after production data and the customer confirm the problem has stopped.
Take time to capture lessons learned afterward so that the next team can start with your findings.
Make every 8D fix last
A strong 8D report links a verified root cause to permanent actions and proof that they worked. Keep containment separate from the fix, give every action one owner and close only after verification.

MeisterTask keeps the follow-up organized and transparent, with one task per action and progress the whole team can see. Start with your next complaint and let every 8D leave your process stronger than before.