> The 8D report step by step: all eight disciplines explained, typical deadlines, a complete example and the most common mistakes when handling customer complaints.

Source: [https://docxpert.io/en/guides/8d-report](https://docxpert.io/en/guides/8d-report)

# 8D Report: Method, Structure and Example

## What is an 8D report?

8D stands for **eight disciplines** – eight consecutive steps a team uses to solve a problem systematically. The method was developed in the US automotive industry and is now a fixed part of many customer-specific requirements. The 8D report is the document that records this path and shows the customer that the problem is understood and permanently eliminated.

Unlike a simple complaint response, 8D requires a solid root cause analysis – both for why the defect **occurred** and for why it was **not detected**. Only when both causes are eliminated is the problem considered solved.

8D and CAPA

8D is a method, CAPA a process. In many companies an 8D report is produced within a CAPA record when a customer requests it. More in the guide [CAPA process](https://docxpert.io/en/guides/capa-process).

## The eight disciplines at a glance

| Discipline | Content | Key question |
| --- | --- | --- |
| D1 | Form the team | Who has the knowledge and authority to solve the problem? |
| D2 | Describe the problem | What exactly is the problem – measurable and bounded? |
| D3 | Containment actions | How do we protect the customer immediately? |
| D4 | Identify root causes | Why did the defect occur, and why wasn't it detected? |
| D5 | Choose permanent corrective actions | Which actions demonstrably eliminate the causes? |
| D6 | Implement and validate | Do the actions work in practice? |
| D7 | Prevent recurrence | How do we prevent the same problem elsewhere? |
| D8 | Close and recognise | What did we learn, and how do we recognise the team? |

Some guides add a **D0** for planning and emergency response before the actual 8D process.

## D1 to D3: team, problem, containment

### D1 – Team

An 8D team consists of three to six people from the affected areas – such as production, quality, engineering and purchasing. One person leads the team; a manager acts as champion and provides resources.

### D2 – Problem description

A precise description is half the solution. The **is/is-not analysis** has proven itself: what is affected – and what similar thing is not? Where, when, how many? The 5W2H questions (what, where, when, who, why, how, how many) also help. Avoid assumptions about causes at this step.

### D3 – Containment

Containment protects the customer until the cause is eliminated: block and inspect stock, sorting at the customer, additional inspections, marking inspected parts. Many customers expect D3 within 24 hours. The effectiveness of containment must be demonstrated – for example through sorting results.

## D4: root cause analysis

D4 is the heart of the 8D report. Two causes are sought:

-   **Occurrence root cause:** why did the defect occur? For example a worn tool.
-   **Escape (non-detection) root cause:** why wasn't it detected? For example a characteristic missing from the inspection plan.

Methods such as 5 whys, the Ishikawa diagram or fault tree analysis help you go beyond the first obvious answer. A cause is only confirmed when the defect can be deliberately produced or eliminated with it. Details on the methods are in the guide [root cause analysis methods](https://docxpert.io/en/guides/root-cause-analysis).

## D5 to D8: actions, validation, prevention, closure

### D5 – Choose permanent corrective actions

For each confirmed cause an action is selected and verified before introduction – for example through a trial. Technical solutions such as error-proofing (poka-yoke) are preferred over organisational appeals.

### D6 – Implement and validate

The actions are introduced, and containment ends once validation succeeds. Data shows that the defect no longer occurs.

### D7 – Prevent recurrence

Systemic actions make sure the problem does not occur on similar products, processes or sites: update the FMEA, extend the control plan, change work instructions, document lessons learned.

### D8 – Closure

The team is recognised, the report closed and sent to the customer. Recognition is not an end in itself: teams whose work is seen tackle the next problem with commitment too.

## Suitable tools per discipline

| Discipline | Proven tools |
| --- | --- |
| D2 | Is/is-not analysis, 5W2H, photos and measurements of defective parts |
| D3 | Block lists, sorting instructions, marking inspected parts, batch traceability |
| D4 | 5 whys, Ishikawa diagram, fault tree, comparing good and bad parts, confirmation trials |
| D5–D6 | Poka-yoke, process capability studies, before-and-after defect rates |
| D7 | FMEA, control plan, lessons learned database, change management |

Not every tool is needed in every case. What matters is that the chosen method fits the complexity of the problem and that the results are traceable in the report.

## Typical deadlines

| Milestone | Common customer expectation |
| --- | --- |
| Acknowledgement and D1–D3 | Within 24 hours |
| D4 with confirmed cause | Within about 10 working days |
| D5–D6 | Within about 30 days |
| Closure D8 | Within about 60 days |

Binding deadlines are in your customers' specific requirements and can differ considerably. Record them per customer.

## Example: 8D report on leaking connectors

| Discipline | Content |
| --- | --- |
| D1 | Team lead from quality, one person each from moulding, assembly and test engineering; champion: plant manager. |
| D2 | Water ingress at the customer on 14 of 2,000 connectors from batch 26-118; other batches and variants not affected. |
| D3 | Remaining stock blocked, 100% leak test, sorting at the customer: 9 more parts found. |
| D4 | Occurrence: seal groove too shallow after tool repair. Escape: groove depth not in inspection plan, leak test only by sampling. |
| D5 | Tool corrected; groove depth added as inspection characteristic; 100% leak test for three months. |
| D6 | Three batches without findings; actions confirmed, sorting ended. |
| D7 | Release after tool repair made mandatory in the work instruction; FMEA and control plan updated; transferred to all moulds with seal grooves. |
| D8 | Closure agreed with the customer, lessons learned presented in the team meeting. |

## Common mistakes in 8D reports

-   **Causes in D2:** the problem description already contains assumptions and steers the analysis in one direction.
-   **Only one cause:** the escape cause is missing – the next defect slips through as well.
-   **"Employees made aware":** training is not a permanent corrective action for a technical problem.
-   **D7 missing:** lessons are not transferred to similar products and processes.
-   **Deadlines missed:** customers also rate suppliers on response time.
-   **No evidence:** claimed effectiveness without data convinces no customer.

## What customers look for

Many vehicle manufacturers rate 8D reports systematically and feed the result into supplier ratings. Typical criteria are response time, quality of the problem description, evidence of both causes, effectiveness of actions and transfer to other products. A convincing report is short, fact-based and backed by evidence such as photos, measurements or test results.

## 8D reports with docxpert

docxpert provides a "Nonconformity & 8D report" template and connects it with [CAPA management](https://docxpert.io/en/features/capa-management): containment, root cause analysis with 5 whys or Ishikawa, action plan and effectiveness check are documented in fixed phases. Changed work instructions go through [change requests](https://docxpert.io/en/features/change-control) and approval, and training on the new requirement through training management.

## Frequently asked questions

What does 8D stand for?

Eight disciplines – eight steps from forming the team to closure that solve a problem in a structured way.

When is an 8D report required?

Mostly for customer complaints, especially in the automotive industry. Many companies also use 8D internally for important problems.

What is the difference between occurrence and escape root cause?

The occurrence cause explains why the defect happened. The escape cause explains why it was not detected before shipment. Both must be eliminated.

How long does an 8D process take?

Containment within 24 hours, causes within a few days to weeks, closure often within 60 days. Your customers set the exact deadlines.

Is there an 8D template?

Many customers prescribe their own form. docxpert includes a "Nonconformity & 8D report" template that you can adapt to your customers' formats.

What belongs in D7?

Systemic actions that prevent recurrence elsewhere: updating the FMEA, inspection plans and work instructions, and transferring lessons to similar products and processes.

Who should be on the 8D team?

Three to six people from the affected areas with expertise and decision-making authority, plus a team lead and a manager as champion.

Is 8D useful outside the automotive industry?

Yes. The method works wherever problems involving several parties need a structured solution – for example in machinery, medical devices or services.

How can I show that an 8D action actually removed the cause?

In D6, distinguish evidence that an action was implemented from evidence that it is effective. Define a measurable criterion, observation period and data source before implementation. Depending on the failure, this might be inspection results across several lots, complaint data, process parameters or a targeted audit sample. Check both the occurrence cause and the reason the issue escaped detection; a control at production alone may leave the second gap open. Compare results with a clear baseline and look for side effects on lead time, scrap or other products. If data conflict or the observation period is too short, extend the check and keep the status open. A reasoned effectiveness review supports closure and the broader preventive action in D7.

## Read next

[CAPA processFrom report to effectiveness check: the CAPA process in nine steps.Learn more](https://docxpert.io/en/guides/capa-process) [Root cause analysis5 Whys, Ishikawa and more: which method fits when.Learn more](https://docxpert.io/en/guides/root-cause-analysis) [CAPA managementCorrective and preventive actions in nine phases – with 5 Whys, Ishikawa, deadlines and effectiveness checks.Learn more](https://docxpert.io/en/features/capa-management) [IATF 16949Automotive QMS with customer-specific requirements, core tools and contingency plans.Learn more](https://docxpert.io/en/standards/iatf-16949) [CAPA checklistCheckpoints from problem statement to effectiveness check.Learn more](https://docxpert.io/en/checklists/capa)

## Try docxpert free for 14 days

Document control, approvals, training and evidence in one platform – with English and German templates for more than ten standards.

[Start free trial](https://docxpert.io/en/trial)[See pricing](https://docxpert.io/en/pricing)