The 8D Report: A Template, a Worked Ceramic Example, and Why It Works

The Problem: Fixes That Live Only in an Email

A defect is found, an email is exchanged, a replacement is shipped, and everyone moves on. Six weeks later the same defect arrives on the next delivery, with a different person reading the email chain. The failure is not a lack of effort — it is the absence of a structure that forces the three questions that actually resolve a problem: what exactly happened, why did it happen, and what has changed so that it cannot happen again. The eight-discipline report exists exactly for that, and the discipline is more useful than the acronym.

Products in this guide: Luxury Ceramic Spice Jar Set · Nordic Ceramic Spice Jar Set With Bamboo Lids

A corrective action is a specification change, so the report belongs in the specification file rather than in a mailbox. The spec freeze guide explains how artwork and packing files are locked between orders. Where packing or transport caused the failure, the fix is a packaging decision. The packaging guide explains how retail-ready and protective layers are specified together. The full chain follows the standard sourcing map. See the full ceramic sourcing process map.

The Eight Disciplines, and What Each One Is For

D1 — Assemble a small team. Two or three people: someone who knows the process, someone who owns the specification, and someone who can authorise a change. A committee produces length; a small team produces answers.

D2 — Describe the problem. One paragraph, with numbers. What the defect is, where it was found, how many of how many, when it appeared, and against which specification. This is the single most valuable paragraph in the document, because a vague problem guarantees a vague cause.

D3 — Containment. The immediate actions that protect the customer while the analysis runs: hold remaining stock of the affected batch, decide what the customer receives, and check whether the same condition can exist in goods already in transit.

D4 — Root cause. Why it happened, with evidence, and — the part most reports omit — why it was not detected. A defect that reaches a customer has two causes: the one that made it, and the one that let it through.

D5 — Corrective action for the cause. The change to the process or the specification. This must be a change to something, not a reminder to someone. "Operator retrained" is not a corrective action; "the handle joint load test was added at the end of the glazing line" is.

D6 — Implement and validate. The action was made, and its effect was measured. Validation is what distinguishes a report from an intention.

D7 — Prevent recurrence. The systemic step: does the same failure mode exist on other items, other lines, other customers? A chipped handle on one mug usually means the same risk exists across the range.

D8 — Close and recognise the team. A closing entry with the date, the validated result, and the signature of whoever accepted it. Closure matters because an open report quietly becomes a habit.

A Worked Example

The case: a buyer of 6,000 sixteen-ounce mugs reports that 41 pieces arrived with the handle detached or loose, across 12 of 120 cartons, concentrated in cartons in the middle of two pallets.

D1: the factory assembles the production manager, the moulding line lead, and the QC supervisor.

D2: "41 of 6,000 pieces, from the shipment despatched on 4 August, packed in cartons 34–45, show a detached or loose handle. Typical sales sample and the approved golden sample have sound joints. Failure concentrated in the centre cartons of two pallets, not at the edges."

D3: remaining stock of the same batch held; 60 replacement pieces shipped by air; the customer's stock checked for the same cartons; the pallets in transit flagged for priority inspection on arrival.

D4 (root cause). Two strands, both needed.

*Why it happened*: the handle joint is applied with a slip of a defined consistency. In the affected period, a new batch of clay was used with a slightly higher moisture content, so the slip dried more slowly, and the joints were loaded into the kiln one stage earlier than the drying time required. Result: a proportion of joints that were green-strong but not fully developed. Evidence: the production record showing the kiln-loading time and the clay batch reference; the failure concentrating in a batch rather than at random; a reproduction run confirming the same failure with the same timing.

*Why it was not detected*: the outgoing inspection sampled handles visually and by a light hand check, which does not detect an under-developed joint. No load test was performed on the joint as part of routine inspection.

D5 (corrective action). Three changes: a minimum drying interval between handle application and kiln loading, written into the process sheet; a new incoming check on clay moisture content for the handle-slip batch; and a handle joint load test — a defined load applied to the handle of sampled pieces — added at the end of glazing, with the result recorded.

D6 (validation). The next three production batches were tested at the new interval: 300 pieces load-tested, zero failures, with the test results attached to the report. The buyer was sent the results before the next shipment, not after.

D7 (prevention). The same clay-moisture sensitivity was checked on the two other bodies produced on the same line. The kiln-loading interval was reviewed across all items with applied handles, not only this one. The inspection standard for the buyer's range was updated to include the load test as an item on the incoming sheet.

D8 (closure). The report was closed with the buyer's acceptance, dated, and filed against the item code — which is what makes it findable when the same question is asked in two years' time.

What Makes a Report Credible, and What Destroys It

Credible: numbers where numbers are available; the production record referenced; a reproduction that demonstrates the mechanism; a change that names a document, a step or an instrument; and validation data attached.

Not credible: "the worker was careless"; "we will improve inspection"; a cause with no evidence; an action consisting of retraining with no process change; a closure with no verification. A buyer who receives the second kind learns something useful about the supplier's quality system — which is not the lesson the supplier intended.

The Light Version, for Smaller Claims

Not every defect needs eight sections, and insisting on the full document for a minor finding trains everyone to treat it as paperwork. A two-page version works for smaller cases and keeps the essential structure:

1. What happened — the problem statement with numbers.
2. Immediate action — what the customer receives and when.
3. Cause — why it happened and why it was not caught, in two or three sentences.
4. What changed — the process or specification change, named.
5. How it will be verified — the check on the next shipment, with the date.

The rule for choosing: use the light version when the cause is already understood and the fix is a small change; use the full report when the cause is unknown, when the defect is a Class A failure, or when it has happened before. A repeat of a previously closed defect always deserves the full document, because the real finding is that the previous corrective action did not hold.

What to Ask For, and What to Send

A buyer should ask for four things after a complaint: the problem statement, the cause with evidence, the action expressed as a change, and the verification method with a date. A supplier should send those four without being asked, because a buyer who has to chase a report is a buyer who begins to look for alternatives.

Two practical notes make reports easier to produce than most factories expect. First, most of the evidence already exists — the production record, the batch reference, the inspection sheet — and the work is assembling it rather than generating it. Second, the report should be written once and reused: the species of defect in ceramics is small, and a well-built report for a chipped rim, a warped base or a colour deviation becomes the template for the next one.

The Habit That Ties It Together

The habit is to treat a complaint as a free inspection of the process, and to write the answer down. Programs that do this accumulate a file of solved problems — which is the only form of quality assurance that survives a change of staff on either side.