8D report: containment first, then the cause you can actually prove

An 8D report is a structured problem-solving record in eight disciplines, used across manufacturing and increasingly beyond it, and usually demanded by a customer after a complaint. It is a format and a discipline at once: the numbered steps exist to stop teams from jumping straight from a symptom to a fix.

That jump is what the format prevents, and it is why customers ask for it rather than for a free-form explanation. An 8D forces the team to separate protecting the customer now from understanding what happened, and to say how they know the cause is the cause.

The eight disciplines of an 8D report

• D1 — form the team: people with process knowledge and the authority to change things, not a list of names for the form.
• D2 — describe the problem: quantified. What, where, when, how many, first observed, and what is unaffected. The comparison between affected and unaffected is where the cause usually hides.
• D3 — interim containment: protect the customer while you investigate, and verify the containment actually works.
• D4 — root cause: the cause of the failure and, separately, the cause of the escape — why the control system did not catch it.
• D5 — choose permanent corrective actions, and verify they resolve the problem without introducing a new one.
• D6 — implement and validate: confirm in production, over enough time and volume to mean something.
• D7 — prevent recurrence: update the FMEA, the control plan, the work instruction and the standard, and check whether the same cause exists on similar parts.
• D8 — close and recognise the team.

Two root causes, not one

The step teams reliably skip is the escape. A defect happened, and the customer received it — those are two failures with two causes. The occurrence cause explains why the defect was made; the escape cause explains why inspection, testing or the control plan did not stop it leaving. A report that fixes only the first will produce another complaint from a different defect that escapes through the same gap. Customers who read a lot of these look at D4 for exactly this, and its absence is the most common reason a report comes back.

Verification means demonstrating that the cause and the effect move together — that removing the cause removes the failure, and reintroducing it brings the failure back where it is safe to test. Anything short of that is a plausible story, and plausible stories are why the same problem returns in six months under a different complaint number.

Containment is not the fix

D3 exists to buy time, and its failure mode is becoming permanent. Hundred per cent inspection introduced as containment is still running two years later, absorbing cost and quietly failing at the rate human inspection always does. Set a review date on every containment action at the moment it is introduced, and treat its removal as part of D6 rather than as an afterthought.

Writing it so it survives review

The report is read by someone who has read hundreds, and it is judged on quantification in D2, honesty in D4 and evidence in D6. Ettex Docs holds the report with version history through the review cycle, so the customer’s comments and what changed in response are recoverable; Ettex Board tracks the actions to closure with owners and dates rather than leaving them in a document nobody reopens; and Ettex Records keeps the closed reports per part and per customer, alongside the fmea updated in D7.

To be clear: this is documents, actions and records, not a quality management system, and an 8D is a method rather than a template you fill in. Where a customer mandates a portal or a form, theirs is the one to use.