Complete guide

8D problem solving: the 8 disciplines explained, with an example

8D problem solving: the 8 disciplines explained, with a worked example for supplier problems, common mistakes and free 8D report templates.

Written by , Head of Quality (AS/EN 9100)

Updated:

Grounded in practiceWritten for real quality work
Ready to applyUse examples, templates, and clear steps
Useful next stepsConnected to relevant tools and guides

8D problem solving is a structured method for permanently fixing a problem in eight steps, the “eight disciplines” (D1–D8). A small team describes the problem with facts, protects the customer with immediate containment, finds the root cause of why the defect occurred and why it was not detected, implements corrective actions, proves they work, and changes the system so the problem cannot come back. The result is documented in an 8D report.

8D was developed at Ford in the late 1980s and is now the standard way to answer a customer complaint in automotive, aerospace and most of manufacturing. This guide explains each discipline, shows a complete example from a supplier complaint, and lists the mistakes that make 8D reports fail. To write one now, use the free 8D report generator.

The 8 disciplines at a glance

Step Discipline Purpose Typical output
D0 Emergency response React immediately, before the team is formed Shipments stopped, customer informed
D1 Team The right people with product and process knowledge Team with leader and champion
D2 Problem description Describe the problem with facts and numbers 5W2H, is / is not
D3 Containment actions Protect the customer now Sorted stock, blocked lots
D4 Root cause analysis Find why it occurred and why it was not detected Verified root causes
D5 Permanent corrective actions Choose actions that remove each root cause Action plan with verification method
D6 Implement and validate Implement, prove effectiveness, remove containment Data showing the problem is gone
D7 Prevent recurrence Change the system: FMEA, control plan, instructions Updated documents, lessons learned
D8 Closure and recognition Close the report and recognise the team Signed-off 8D

D0 was added in Ford’s later “Global 8D” version; many forms still start at D1. Either is fine as long as the emergency reaction is documented somewhere.

When to use 8D (and when not)

Use 8D when the problem is important (customer complaint, safety or regulatory impact, repeated defect, high cost) and the root cause is not obvious. A supplier who receives a corrective action request (SCAR) from a customer is usually expected to answer with an 8D.

Do not start an 8D for a simple, one-off problem with an obvious cause and fix: correct it and record it as a non-conformance. An 8D for every scratch buries the team in paperwork and devalues the method.

The disciplines in detail

D0 Emergency response

The first hours count. Stop deliveries of suspect parts, inform the customer, protect people and equipment. Document what you did and when. D0 is not the containment (D3), it is the immediate reaction before anyone has analysed anything.

D1 Team

Three to six people who know the product and the process: quality, production, engineering, often the operator who knows the machine best. One team leader owns the 8D; a champion (a manager) removes obstacles and approves resources. For a supplier problem, include someone from the supplier, or ask the supplier to name their team.

D2 Problem description

Describe the problem so that someone who was not there understands it. The 5W2H questions help: what is the problem, where was it found, when (and since when), who found it, how was it detected, how many parts are affected. Add what is not affected (is / is not): other part numbers, lots, machines, shifts. The difference between “is” and “is not” is often the best hint to the root cause.

A good D2 contains numbers: “340 of 2,000 housings from lot 2391 have burrs in bore Ø12, found in incoming inspection on 2 October; lots 2388–2390 are not affected.”

D3 Containment actions

Protect the customer now, while you search for the cause: sort stock at your site, at the customer and in transit, block suspect lots, add a 100 % inspection. Every action needs an owner and a date, and you need to verify that it works. Containment is temporary: it ends in D6 when the permanent fix is proven.

D4 Root cause analysis

The heart of the method, and where most 8D reports are weak. Find two root causes:

  • Root cause of occurrence: why did the defect happen?
  • Root cause of non-detection (escape point): why did your controls not catch it before it reached the customer?

Use 5 Why, a fishbone (Ishikawa) diagram or fault tree analysis, then verify the cause: can you switch the problem on and off by changing that one factor? “Operator error” is almost never a root cause; ask why the process allowed the error.

D5 Permanent corrective actions

Choose actions that remove each root cause, one for occurrence and one for non-detection. Decide in advance how you will prove effectiveness: which data, over which period. Prefer actions that make the error impossible (poka-yoke, process change) over actions that rely on attention (training, an extra check).

D6 Implement and validate

Implement the actions, record the dates, and validate with data: for example three consecutive lots without the defect, or capability before and after. Only then remove the containment from D3. Without validation, an 8D is a plan, not a solution.

D7 Prevent recurrence

Fix the system, not just this part: update the FMEA, the control plan and work instructions, train the people involved, and check whether similar products and processes have the same weakness. Record the lessons learned so the next team does not start from zero.

D8 Closure and recognition

Confirm with the customer (or internally) that the problem is solved, close the report and recognise the team’s work. Closure means the customer accepts the 8D, not just that the form is full.

A complete example: burrs on a machined housing

D0 Customer informed the same day; all shipments of part A-4711 stopped.
D1 Quality engineer (leader), production supervisor, CNC operator, process engineer; plant manager as champion.
D2 340 of 2,000 housings from lot 2391 have burrs in bore Ø12, found in incoming inspection at the customer on 2 October. Lots 2388–2390 not affected; only machine 4.
D3 All stock sorted (at the supplier, in transit, at the customer); 100 % visual inspection of bore Ø12 until further notice. Verified: no defective parts found after sorting.
D4 Occurrence: the deburring tool was worn; no tool-life limit defined for this tool. Non-detection: the control plan checked the bore diameter, but not burrs. Verified: a new tool produces no burrs, the worn tool reproduces them.
D5 Tool change every 2,000 parts, controlled by the machine counter; visual check for burrs added to the control plan (1 part per hour).
D6 Implemented on 18 October. Three consecutive lots with zero burrs; 100 % inspection removed on 25 October.
D7 FMEA updated (tool wear as failure cause), tool-life limits defined for all deburring tools on machines 1–6, operators trained.
D8 8D accepted by the customer on 30 October; team recognised in the monthly quality meeting.

You can enter this example in the 8D generator and download it as a PDF.

8D, 5 Why, PDCA and A3: how they relate

5 Why and the fishbone diagram are tools inside D4. PDCA (plan–do–check–act) is the general improvement cycle; 8D is a more detailed version of it for problems that have already reached the customer, with containment (D3) and system changes (D7) built in. A3 reports serve a similar purpose on a single page and are common in lean organisations. What makes 8D the standard for supplier complaints is that every customer recognises the format.

8D in supplier quality

When a supplier causes a non-conformance, the 8D connects the complaint to the supplier’s performance:

  1. You document the non-conformance and send the supplier a corrective action request with response dates.
  2. The supplier answers with an 8D report.
  3. You review it critically: are both root causes found and verified? Is the effectiveness proven with data?
  4. The quality of the response feeds into the supplier evaluation: in our scoring model, the share of non-conformances with a complete 8D (D1–D7) is its own criterion, and late closure lowers the score too.

AS/EN 9100 expects corrective action requirements to be flowed down to the supplier when the supplier is responsible for the non-conformance. IATF 16949 requires a documented problem-solving process (clause 10.2.3). The 8D format satisfies both.

Response times are set by the customer, not by the method. Many customers expect the containment within 24 hours, the root cause within about 10 working days and the closed 8D within 30 to 60 days.

In practice the deadlines depend on how critical the non-conformance is. A typical scheme:

Severity Containment (D3) Root cause (D4) Closed 8D
Critical (safety, function, line stop at the customer) within 24 hours 5 working days 30 days
Major within 48 hours 10 working days 30–60 days
Minor within 5 working days or with the next delivery 15 working days 60 days

Your customer’s requirements override this. In aerospace and defence, flow down what your customer asks of you.

The most common weakness I see in supplier 8Ds: the root cause is not actually a root cause. It describes what happened (“operator error”, “wrong machine setting”), not why it could happen. That shows the supplier has not really understood the problem, and a supplier who has not understood the problem cannot define an action that stops it from coming back. It is the first thing I check, and the most common reason an 8D goes back.

Common mistakes in 8D reports

  • Root cause “operator error” or “human error”. The real question is why the process allowed the error.
  • Only one root cause. Without the non-detection cause, the next defect escapes the same way.
  • Corrective action = “retrain the operator”. Training rarely removes a root cause on its own.
  • No validation. D6 says “implemented” but shows no data that the problem is gone.
  • Containment that never ends, or ends before the permanent fix is proven.
  • D7 left empty. The FMEA and control plan still contain the old weakness.
  • The 8D is written by one person at a desk. Without the people who know the process, D4 stays theoretical.

Templates and tools

FAQ

What does 8D stand for?

Eight disciplines: the eight steps of the method, from forming the team (D1) to closing the report (D8). Many forms add D0 for the emergency response.

What is an 8D report?

The document that records the 8D process: team, problem description, containment, root causes, corrective actions, validation, preventive measures and closure. Customers usually request it in response to a complaint.

How long does an 8D take?

Containment within hours or days, the root cause typically within one to two weeks, the complete 8D including validation within 30 to 60 days. The exact deadlines are set by the customer.

When is an 8D complete?

When the root causes of occurrence and non-detection are verified, the corrective actions are implemented and validated with data, the system is updated (D7) and the customer has accepted the report.

Is 8D required by ISO 9001?

No. ISO 9001 (clause 10.2) requires you to react to non-conformities, determine their causes and take corrective action, but it does not prescribe a method. 8D is a widely accepted way to meet the requirement, and many customers specify it.