8D Report with Example: How to Close a Customer Complaint Properly

An 8D report is a standardised report that a company uses to work through and document a quality problem in eight steps, from forming a team through root cause analysis to closure. The eight disciplines D1 to D8 make sure that the symptom is not merely fixed, but that the actual root cause is found, permanently eliminated and prevented from recurring. The 8D report is used above all for customer complaints in manufacturing, often because the customer requires it.

Where the 8D method comes from

The 8D method goes back to Ford. The company described it in 1987 in its manual «Team Oriented Problem Solving», TOPS for short. In the 1990s Ford added a preliminary step D0 and called the revised version Global 8D. Through the automotive industry and its suppliers, the 8D report has since spread across manufacturing as a whole. In the German-speaking world, the German Association of the Automotive Industry (VDA) has described the method in a volume of its own.

Disciplines D0 to D8 at a glance

Discipline	Goal	Typical result
D0 Prepare	Decide whether an 8D is needed and start an emergency response	Decision for or against an 8D, first emergency response
D1 Form the team	Bring together the right people with expertise and authority to decide	Team list with team lead and responsibilities
D2 Describe the problem	Define the problem in measurable, unambiguous terms	Problem statement by what, where, when and how many
D3 Containment actions	Protect the customer until the cause is eliminated	Blocked stock, sorting inspection, evidence that it works
D4 Determine root causes	Find and verify the root cause, including why the defect was not detected	Verified root cause for occurrence and non-detection
D5 Choose permanent corrective actions	Select actions that eliminate the root cause	Selected actions with evidence that they can work
D6 Implement and verify effectiveness	Introduce the actions and lift the containment	Proof of implementation and effectiveness check
D7 Prevent recurrence	Transfer the lessons to processes, specifications and similar products	Updated work instructions, FMEA and inspection plans
D8 Close	Formally close the case and recognise the team’s work	Closed report, customer informed

Each discipline explained, with an example

The following example is fictitious but typical of a Swiss industrial SME. A turned parts manufacturer with around 80 employees, here called «Example Ltd», supplies bushings to a maker of hydraulic components. The customer reports by email that part of a delivery of 2,000 bushings cannot be assembled. At incoming inspection, 140 pieces were above the upper tolerance of the outside diameter.

D0 Prepare

In D0 the company checks whether the case justifies a full 8D. Criteria include the impact on the customer, whether the defect recurs and whether the customer requires the report. If needed, an emergency response is triggered at this point.

Example. The customer requires an 8D report by contract, and its assembly line is at a standstill. The quality manager decides on a full 8D and confirms receipt to the customer the same day.

D1 Form the team

An 8D is teamwork. The team includes people from the affected areas who know the process and can decide on actions. One person leads the team and is responsible for the report.

Example. The quality manager leads the team. She is joined by the head of the turning shop, the setter of the affected CNC machine, an inspector from quality control and the sales back office as the contact to the customer.

D2 Describe the problem

A good problem description is measurable and free of assumptions. The questions what, where, when and how many have proven useful, complemented by stating what is not affected.

Example. The outside diameter of the bushing is up to 0.02 mm above tolerance. 140 of 2,000 parts from a single production lot are affected, all made on one machine. Parts from other lots and other machines are not affected.

D3 Containment actions

Containment actions protect the customer until the cause is eliminated. They treat the symptom, not the cause, and must work in their own right.

Example. Stock and ongoing production are blocked. Example Ltd sorts the remaining quantity at the customer’s site and in its own warehouse with a 100 percent inspection of the outside diameter. Replacement parts go out inspected and labelled with the next delivery.

D4 Determine root causes

D4 is the core of the method. The aim is the root cause, the cause whose elimination prevents the problem permanently. In addition, the team determines why the defect was not detected in-house. Two widely used tools are the Ishikawa diagram and the 5 Whys.

The Ishikawa diagram, also called cause and effect or fishbone diagram, collects possible causes sorted by category, often by the 6M of man, machine, method, material, measurement and milieu, meaning the environment. The 5 Whys keep asking why until a cause is reached that the company can influence. The number five is a guide, not a rule.

Example. In the Ishikawa diagram two categories stand out, material and method. Shortly before the affected lot, production had switched to a different material. The 5 Whys chain looks like this.

1. Why is the diameter too large? Because the turning tool was worn.
2. Why was it worn? Because it was used longer than the new material allows.
3. Why was it used too long? Because the CNC program still held the tool life for the old material.
4. Why was the tool life not adjusted? Because the material change was approved without checking the machining parameters.
5. Why was there no check? Because the procedure for material changes does not include a review of tool life.

For non-detection, the analysis shows that sample inspection took place only at the start and the end of the lot. The wear built up in between. The root causes are therefore the missing review of tool life when materials change and an inspection interval that was too wide.

D5 Choose permanent corrective actions

In D5 the team selects actions that address the root cause and, before introducing them, shows that they can work, for example through a trial.

Example. The tool life for the new material is determined in a trial and stored in the program. The inspection interval for the outside diameter is shortened. A trial run shows that all parts are within tolerance.

D6 Implement and verify effectiveness

The actions are introduced, and their effectiveness is checked over a period defined in advance. Only then are the containment actions from D3 lifted.

Example. Example Ltd specifies that the 100 percent inspection continues until three consecutive deliveries arrive without findings. The criterion is met and the sorting inspection ends.

D7 Prevent recurrence

D7 asks where the same defect could still arise. The lessons flow into procedures, specifications and risk assessments and are transferred to similar products and machines.

Example. The procedure for material changes gets a checklist that includes reviewing tool life. The process FMEA is updated, and the tool life on all machines that process the same material is reviewed.

D8 Close

At the end the report is formally closed, the customer is informed and the team’s work is recognised. Recognition is not a ritual. It shows that thorough root cause analysis is valued.

Example. The quality manager sends the completed 8D report to the customer and thanks the team at the next department meeting.

What ISO 9001 requires

ISO 9001:2015 does not prescribe an 8D report. Clause 10.2 «Nonconformity and corrective action» does require you to react to a nonconformity, including one arising from a complaint, to take action to control and correct it and to deal with the consequences. You then evaluate whether action is needed to eliminate the cause so that the defect does not recur or occur elsewhere. This includes determining the cause and checking whether similar nonconformities exist or could occur. The effectiveness of corrective actions must be reviewed, and where necessary risks and opportunities are updated and the management system is changed. The nature of the nonconformity, the actions taken and their results are retained as documented information.

A properly kept 8D report covers these requirements. D3 corresponds to reacting and containing, D4 to determining the cause, D5 and D6 to the corrective action with its effectiveness check, D7 to the question of similar defects and to changing the system. The report itself is the documented information. The same logic applies to findings from internal audits. There, too, you need a cause, an action and an effectiveness check.

8D report or simple corrective action?

Not every defect needs an 8D. A simple corrective action is enough when the cause is obvious, the defect is a one-off and the impact is small, for example a typo on a delivery note.

An 8D pays off when the cause is unclear, the defect recurs, several departments are involved, the impact on the customer is significant or the customer requires the report. The difference lies not in the form but in the depth. The 8D demands teamwork, a verified root cause, an analysis of non-detection and the transfer to similar cases.

Common mistakes in 8D reports

• Confusing containment with permanent corrective action. A 100 percent inspection protects the customer but eliminates no cause. If it appears in D5, the report is not finished.
• «Human error» as the root cause. If a person was able to make a mistake, the cause usually lies in the process that allowed it. Retraining alone is rarely an effective corrective action.
• Analysing occurrence only. Without asking why the defect was not detected, half of the analysis remains open.
• Not verifying effectiveness. An implemented action is not yet an effective one. Define in advance how you will measure effectiveness.
• Writing the report afterwards. If the 8D report is only written in Word at the end, it reflects what people remember rather than what was recorded in the case.

Producing the 8D report directly from the complaint case

Many SMEs keep complaints in an Excel list and then write the 8D report in Word. Once actions have to be tracked and key figures evaluated, the list becomes a second set of books.

In QuKI, our quality management software, everything belongs to one case. You drag the complaint email, a PDF or a photo into the window, and the AI reads the content and pre-fills title, description, contact details, article reference and reason for complaint as a suggestion. You review and approve. The root cause analysis is recorded in the case, and the 8D report for your customer reflects what is documented there. At the end the customer rates the handling through a link. How complaint management in QuKI works in detail and where AI in quality management helps elsewhere is shown on the respective pages.

Frequently asked questions about the 8D report

What does 8D stand for?

8D stands for eight disciplines, eight working steps from D1 form the team to D8 close. Many companies also work with D0 as preparation, as Ford introduced it with its Global 8D version.

Is an 8D report mandatory?

Not by law, and ISO 9001 does not prescribe a specific method either. It does require you to eliminate the cause of nonconformities and to review the effectiveness of the corrective action. Many customers, especially in the automotive and supplier industries, require the 8D report by contract.

Who fills in an 8D report?

A team from the affected areas, such as quality, production and engineering. One person leads the team and is responsible for the report, often someone from quality management.

How long does an 8D report take?

The deadlines are usually set by the customer, for example in its terms of delivery or a quality assurance agreement. A short deadline for containment actions and a longer one for root cause analysis and closure are common.

What is the difference between D3 and D5?

D3 protects the customer in the short term and treats the symptom, for example by sorting. D5 defines the permanent action that eliminates the root cause.

8D reports with QuKI

Would you like to see how a complaint runs in QuKI from the email to the completed 8D report? In a 30-minute demo we show you, using your own workflows.