The situation

It is 16:40 on Thursday. The customer’s plant has found 42 brackets with a missing hole. Their quality manager wants an 8D report by tomorrow morning. You have a half-empty template, a pallet number, and a lot of opinions from the people around you.

Everyone wants the form filled. Few people want to find out why the hole is missing. This guide helps with the second part.

What an 8D report is for

An 8D report is a structured problem-solving report. “8D” means eight disciplines, or steps. A team uses it to protect the customer, find the real cause, fix it, and prove the fix works.

The report is also evidence. The customer reads it to decide if they can trust you again. So it must be clear, honest, and checkable.

Key terms, defined once:

  • Containment: an action that protects the customer today, before you know the cause. Sorting parts is containment.
  • Root cause: the reason the problem happened. Removing it stops the problem.
  • Escape point: the place where the defect should have been caught, but was not.
  • Corrective action: an action that removes the root cause.

A short history

The roots are in a US military standard, MIL-STD-1520, about corrective action for nonconforming material. Ford Motor Company wrote the eight disciplines into its “Team Oriented Problem Solving” course in 1987. In the mid-1990s Ford added a step zero, D0, for preparation and emergency response. Many car makers and suppliers use the method today. Exact details of how each customer adopted it are unclear, so always check which format your customer wants.

Where it applies, and where it does not

Use an 8D when:

  • a customer complains about a defect or a delivery stop;
  • the cause is unknown and several departments must help;
  • an audit finding needs formal closure;
  • scrap has jumped and nobody knows why.

Do not use an 8D when:

  • the cause is obvious and the fix takes ten minutes;
  • a standard procedure already covers the case;
  • a 5-Why at the line board can solve it today.

A formal 8D for a small blip creates paperwork, not learning.

How to do it

We follow one example. The plant is fictional: PolaTech Precision Stampings. The part is bracket BRK-4412-R. Marek is the quality engineer and team leader. Anna is the press tooling specialist. Tomasz is the shift leader.

  1. D0, prepare. Decide if an 8D is needed. Protect people and equipment. Marek stops shipments of the bracket and starts the report.
  2. D1, form the team. Choose people who know the product, the process, and the shop floor. Name a leader and a sponsor. Marek, Anna, and Tomasz join.
  3. D2, describe the problem. Say what, where, when, and how many. Write facts only. Example: a 6.5 mm hole is missing on the right flange of 42 brackets on pallet P-804, made on Press Line 3, night shift.
  4. D3, contain. Protect the customer now. Quarantine 1,200 parts in transit, sort the warehouse stock, and put a go/no-go pin gauge at packing. Check that the containment really works.
  5. D4, find the root cause. Find why the defect was made, and why it was not caught. Use a fishbone or a 5-Why, and back each cause with evidence. The punch sheared from fatigue after guide bushing lubrication failed. It escaped because the optical sensor was bypassed during die setup.
  6. D5, choose the corrective action. Pick actions that remove both causes. Test them first. Anna proposes a tool steel punch with a load monitor, and a sensor bypass that needs a maintenance key.
  7. D6, implement and validate. Put the action into production. Remove the containment only when data supports it. The new tooling runs 10,000 hits with no missed punch. The sort station is closed.
  8. D7, prevent recurrence. Spread the lesson. Update the control plan, the failure analysis document, and the maintenance schedule for all piercing dies. Bushings are now replaced every 50,000 cycles.
  9. D8, close. Thank the team, archive the data, and get the customer’s approval.

Three ways it goes wrong

1. Containment treated as the fix. The team sorts 100% of parts and relaxes. Months pass, sorting costs pile up, and the cause is still there. Containment is not correction. It buys time. Use the time.

2. “Operator error” as the root cause. The report says “operator forgot a step” and the action says “retrain the operator”. This stops the thinking too early. Ask what in the process allowed the error, and why nothing caught it. In our example, a bypassed sensor was the real finding.

3. Closing without checking. The report is signed the day new tooling arrives. Nobody looks at run data. Weeks later the same defect returns. Closed is not solved. An action is finished when its effect is verified.

Our recommendations

  • Go and see. Visit the press before you write D4. Evidence beats opinion.
  • Mark facts and assumptions. Write “observed” or “assumed” next to each cause.
  • Look for two causes. One for how the defect was made. One for how it escaped.
  • Set a check date in D6. Put a date in the calendar to look at the data again.
  • Keep it readable. The customer will read it on a laptop, late in the day. Short sentences win.
  • Do not fill the form to look busy. Solve the problem first, then write.

Try it

Our 8D tool is coming soon. It will run in your browser, with no account, and your data will stay on your device. Meanwhile, see the tool page: /tools/eight-d.

From the book

This guide follows Chapter 10, the 8D chapter, of the field manual. See /book for the book.