20 November 2026
8D Report Step by Step - From Containment to Closing the Problem

An 8D report usually arrives in a company the same way. A customer - most often automotive or a large retail chain - sends a complaint with a note: "please provide an 8D report". Someone finds a template, fills it in two days before the deadline and sends it back. The customer either accepts it or returns it asking why the root cause reads "operator error".
The 8D form is simple. Nine sections, a few tables, room for signatures. The hard part is that each section should be written at a different time, by different people and with different evidence - and in practice they are all written at once, at one desk, on the last day.
Below are the nine steps of the 8D method, D0 to D8. For each one, the same three things: what the team does, what has to go into the report, and what a report looks like when it gets through the customer's inbox but solves nothing.
D0. Preparation and emergency response
Before there is a team, someone has to decide this is an 8D at all. Not every complaint needs one - a single scratch on one unit is a different scale from a defect that may sit in the whole batch.
What goes into the report: how the problem became known (complaint, audit, line inspection, supplier notice), why a full 8D was started, and what was done immediately, before any analysis.
What a weak report looks like: D0 is skipped because "it is just a formality". Later nobody can say when the company actually learned about the defect - and that is the date the customer counts every deadline from.
D1. The team
8D is a team method for a simple reason: the person who knows the production process rarely knows the inspection process, and the person who knows inspection does not know logistics. The cause usually sits where they meet.
What goes into the report: the problem owner, a sponsor (someone with authority over decisions and resources), and team members with their function - quality, production, process engineering, logistics, sometimes the customer's or supplier's quality engineer.
What a weak report looks like: the team is one person - the quality engineer writing the report. The other names are there because the template has five rows. OEM customers notice: a root cause found without production usually reads like a guess.
D2. Problem description
The description is the step most often rushed. "Cracked housing" is a symptom, not a description. A description answers: what exactly, where, when, how many, in which batch - and how this case differs from the parts that are fine.
What goes into the report: part number and revision, batch or production date, defective quantity against quantity delivered, where it was found, photos, and an is / is-not comparison (batch A affected, batch B not; occurs on cavity 2, not on cavity 1).
What a weak report looks like: the description is one sentence copied from the complaint. Without the is / is-not comparison, D4 has nothing to stand on and root cause analysis starts with guessing.
D3. Containment
Containment protects the customer before the cause is found. It means blocking and sorting everywhere a defective part might be: at the customer, in transit, in your warehouse, in production, and at the component supplier.
OEM customers typically expect containment within 24 hours. It is the shortest deadline in the whole 8D and the only one measured in hours.
What goes into the report: where parts were blocked, how many were checked at each location, how many rejected, by what method, who sorted, from which batch or date parts are reliable again (the clean point), and how post-containment shipments are marked.
What a weak report looks like: "parts have been sorted". Without numbers and locations the customer cannot tell whether sorting covered goods in transit - which is usually where the next complaint is sitting.
D4. Root cause
This is the heart of the report and the step where customers reject the most 8Ds. You are looking for two causes, not one:
- occurrence cause - why the defect was created,
- escape cause - why inspection did not stop it.
The tools are well known: an Ishikawa diagram (causes grouped into the 6M categories - man, machine, method, material, measurement, environment) to collect hypotheses, and 5 Why to get from the symptom down to the cause. One 5 Why chain for occurrence, a separate one for escape.
What goes into the report: the analysis that leads to the cause, and evidence that it is the cause - reproducing the defect under controlled conditions, a measurement, a test showing the defect disappears once the cause is removed.
What a weak report looks like: the cause reads "operator error", "employee inattention" or "one-off event". Those are not causes, they are places where the analysis stopped. If an operator could make the mistake, the question is why the process allowed it - and that is the next "why".
D5. Choosing corrective actions
With the cause known, you choose the actions that will remove it. This is still a decision step, not implementation: which solution, why this one and not another, and how you know it will work.
What goes into the report: an action for each verified cause (separately for occurrence and escape), the reasoning behind the choice, an owner and a due date.
What a weak report looks like: the only action is "operators retrained". Training is sometimes needed, but it rarely removes a cause - if the defect could happen once, it will happen again with the next change in the crew. Stronger actions change the process: error-proofing in the fixture, a changed parameter, an extra check where the defect is created.
D6. Implementation and verifying effectiveness
An implemented action is not yet an effective action. D6 ends only when data shows the defect has stopped occurring - and only then can the D3 containment be lifted.
What goes into the report: implementation date, how effectiveness was checked (how many batches, over what period, against what measure), the result, and the date containment was lifted.
What a weak report looks like: status "implemented", dated yesterday, with no result. The customer knows effectiveness cannot be checked in a day. If an action turned out ineffective, the report should show it alongside the new action - a failed attempt that was hidden comes back at the next audit.
D7. Prevention
D6 removes the cause in this one place. D7 asks where else it could happen: on other lines, with similar parts, at other suppliers, in new projects.
What goes into the report: updates to the FMEA and control plan, work instructions, rolling the fix out to similar processes and parts, and lessons recorded so they reach the next project.
What a weak report looks like: D7 is empty or says "none". It is the most common gap in reports that customers accept - and the most common reason the same defect comes back a year later in a different part.
D8. Closure and recognising the team
Closure is the sponsor's decision that the problem is solved: cause verified, actions implemented and effective, prevention done. Thanking the team sounds like courtesy, but it has a practical point - people come back to the next 8D more willingly if the last one ended with something for them.
What goes into the report: closing date, who approved it, a short summary of what changed.
What a weak report looks like: the 8D is "closed" because the customer's deadline passed, while the D6 actions are still waiting for verification. On paper the document is complete; in practice the problem is still open.
8D or QRQC
Not every quality problem needs nine steps and a sponsor. QRQC (Quick Response Quality Control) is the fast track for defects found internally: on the shop floor, at inspection, at the morning meeting. Detection, containment, cause, countermeasure, lessons - in days, not weeks, without formal approvals.
A good practice: start with QRQC, and if the defect turns out to be more serious or the customer asks for a report, move to 8D. What matters is not starting over when you do - what the team established in the first hours is the most valuable evidence for D2 and D3.
What this means for the tool
Look at all nine steps at once and three things stand out that an 8D form will not handle:
Steps have different owners and different deadlines. Containment in a day, cause in a few days, closure in a few weeks. One deadline on the whole report only tells you when the customer will start calling.
Several people work in parallel. Logistics records the sorting, process engineering analyses the cause, the production manager plans the actions. A spreadsheet passed around by email gives you either a queue or "8D_final_v3_fixes.xlsx".
Closure should have conditions. A report in which D8 can be closed without a verified cause and a checked action will sooner or later be closed exactly that way.
In Reklamator a quality problem is a separate record, linked to any number of complaints or to none - when the defect was found by an audit or on the line. Steps run in parallel, each with its own owner and deadline (by default containment in 1 day, cause in 10, closure in 60, adjustable in settings). The cause, prevention and closure are approved by a sponsor who cannot be the problem owner. D8 will not close without a verified occurrence and escape cause and at least one effective corrective action. QRQC escalates to 8D in one click with all the work done so far, and the PDF report goes to the customer from the problem record, in their language.
One caveat: the software keeps track of steps and evidence, but it will not find the cause for the team. The quality of the report still depends on how well people worked through D2 and D4.
When a spreadsheet is genuinely enough
If you write an 8D once a quarter, the team sits in one building and the customer accepts the report in their own template - a spreadsheet or the customer's form is the right tool. A system for a few reports a year solves a problem you do not have.
Signs it has stopped being enough:
- several 8Ds are open at once and nobody can say offhand which are waiting on containment and which on effectiveness checks
- the same defect comes back and the previous report has to be dug out of the inbox of whoever wrote it
- the report gets written on the last day because nobody saw the D4 deadline pass
- an auditor asks who approved the root cause and when, and the answer is a signature on a PDF with no date
- several complaints from different customers concern the same defect and each gets a separate reply
Frequently asked questions
How long should an 8D take?
It depends on the customer and the industry. In automotive you often see an expectation of containment in 24 hours, root cause in about 10 days and closure in about 60 days. Your customer's requirements are what binds you - check the contract or the supplier manual before setting your own deadlines.
Does every complaint need an 8D report?
No. An 8D makes sense when the defect can recur, affects many units, or the customer explicitly asks for one. A single random damage case can usually be handled as a complaint - or as a quick QRQC if you want a record of the analysis.
Who should be the sponsor?
Someone who can make resource decisions: the plant manager, the quality director, the production manager. The sponsor does not write the report - they approve the key steps and unblock what the team cannot sort out alone. Ideally they are not the problem owner: approving your own work is no check at all.
What is the difference between the occurrence cause and the escape cause?
The occurrence cause explains why the defect appeared - for example a worn tool. The escape cause explains why inspection did not catch it - for example the gauge did not measure that dimension. OEM customers require both, because removing only the first leaves the way open for the next defect of the same kind.
Is an 8D report enough for an audit?
A report is evidence, not a certificate. An auditor asks about completeness, verified causes, checked effectiveness of actions and the history of changes. Whether your process meets the standard and the customer's requirements is for the auditor to judge - no document or software settles that for you. If the 8D comes from a complaint, it is also worth reading about the most common complaint handling mistakes - some of them start before D0.
Reklamator
Show us the last 8D report you wrote
In a 20-minute demo we will rebuild it in the system and show how much work is left for the team. You can also start with the 30-day trial.
Start for free