The 8D Report per VDA Band 8D: Guide, Worked Example and What IATF 16949 Actually Requires

Updated 30 September 2026. This article has been rewritten and now rests on primary sources only: VDA, IATF, the OEM requirements published by the IATF, and ISO 9001. The earlier claim that almost every major OEM prescribes 8D did not survive a check of the published customer requirements and has been corrected.

The 8D report has a worse reputation than almost any other document in quality management. The method is not to blame; the habit is — treating 8D as a form that gets filled in once the real work is done. This article walks through the eight disciplines on one running case, explains the single distinction most reports get wrong, and sets out what IATF 16949 and the OEMs actually require.

What VDA Band 8D is — and what it is not

The German automotive industry association VDA describes the method in a volume of its own: 8D — Problemlösung in 8 Disziplinen. Methode, Prozess, Bericht (8D problem solving in eight disciplines: method, process, report), first edition, November 2018, published by VDA QMC. VDA still lists that edition as current [1].

More telling than the title is where VDA draws the line itself. The volume covers 8D as a tool for sustainable problem solving and explicitly not as a general complaint-handling process [1]. Complaint processes usually impose deadlines, the disciplines take different amounts of time, and VDA warns that sustainable problem solving must not come into conflict with time targets aimed at handing over the report [1].

That is exactly where 8D bends in practice. If the report is due before the cause is proven, a plausible cause gets written into it. More on that under deadlines below.

On origins: the method is usually traced to Ford’s Team Oriented Problem Solving programme of the late 1980s, from which Ford’s current Global 8D grew. There is no freely accessible primary source for that history; that Ford still works with Global 8D is documented in its customer-specific requirements [4].

The eight disciplines on one example

A tier-1 supplier receives a complaint: in a shipment of milled brackets, a bore is out of tolerance, found by the customer at final assembly.

D0 — Emergency response. Before any team exists: are further shipments in transit? Does the customer need to be told, do shipments need to stop? D0 is not part of every 8D variant; Ford asks for the 8D explicitly from D0 [4].

D1 — Team. Quality, production, manufacturing engineering, and depending on the case whoever owns gauges or tooling. What matters is not size but a named facilitator and clear roles. The classic failure: one person writes the report alone and the team exists only on the cover sheet.

D2 — Problem description. Not “bore out of tolerance” but: what exactly (bore Ø 8H7, measured 8.04 mm), where found (customer’s incoming inspection at final assembly), when (shipment week 38), who reported it, how many (14 of 240 parts, 5.8%). A description without quantity and time frame cannot be verified later — you will not know whether the fix worked or the problem merely became rarer.

D3 — Containment. Quarantine stock, sort at the customer, 100% inspection of the bore until the fix is in. Containment protects the customer; it does not remove the cause. Its effect needs evidence too: 100% inspection with the same gauge that already missed the defect once protects nobody.

D4 — Root causes. Two chains, not one — see the next section.

D5 — Choose and prove corrective actions. One action per confirmed cause, with its effect demonstrated before rollout: trial runs, capability study, simulation.

D6 — Implement and validate. Roll out into series production, then prove on production parts that the defect no longer occurs. Only now may the D3 measures be lifted.

D7 — Prevent recurrence. The lesson goes back into the FMEA, control plan and inspection instructions — and onto similar parts and processes. If D7 merely repeats D5, the analysis stopped one level too early.

D8 — Closure. Formal sign-off, evidence of effectiveness, recognition of the team. In practice the most frequently skipped step: the report goes to the customer but is never closed internally.

D4: why the defect occurred — and why it escaped

VDA Band 8D requires two separate cause chains in D4 [1]: one for occurrence (why did the defect arise?) and one for non-detection (why did inspection not catch it?).

In the example:

	Occurrence chain	Non-detection chain
Symptom	Bore too large	Defective parts shipped
Why?	Drill worn	Sampling missed the parts
Why?	Tool change not triggered	One sample per shift; wear sets in within the shift
Why?	Tool-life counter reset after machine stop	Inspection interval never matched against tool life
Action	Store counter persistently, log stops	Tie inspection interval to tool life, boundary sample at the station

Work only the left column and the tooling problem is solved — while inspection stays exactly as blind to the next, independent cause of the same defect type. Each chain works like a 5 Whys analysis, with the same rule: every answer has to be evidenced, not assumed.

Assessment: the non-detection chain is the one most often missing from submitted reports, or shrunk to a single line (“inspection staff sensitized”). To a customer it is often the more important of the two, because it shows whether the supplier understands its own safeguards.

Is 8D mandatory? What IATF 16949 and the OEMs require

IATF 16949 does not name 8D. Clause 10.2.3 requires a documented problem-solving process that prevents recurrence. It must include defined approaches for different types and scales of problem, containment, root cause analysis with method and results, systemic corrective actions including their impact on similar processes and products, verification of effectiveness, and updating documents such as the PFMEA and control plan [3]. The recurrence requirement was added by Sanctioned Interpretation 20, effective January 2021; the IATF’s stated reason is that corrective actions often miss that step [3].

The same clause settles the decisive point: where the customer prescribes specific problem-solving processes, tools or systems, the organization has to use them unless the customer approves otherwise [3]. Whether 8D is mandatory is therefore the customer’s call.

What the OEMs actually require. The IATF publishes the OEMs’ customer-specific requirements (CSRs) in one place. A review on 30 September 2026 gives a mixed picture:

OEM	CSR for IATF 16949	8D named?
Ford	June 2026	Yes: analysis using 8D and 3×5 Why; response within 24 hours, 8D through D3, after 15 calendar days an 8D or 6-panel with preliminary or verified root cause [4]
General Motors	October 2025	No; instead process elements such as daily review by a cross-functional team, documented containment, exit criteria [5]
BMW Group	April 2021	No [6]
Mercedes-Benz	February 2022	No [7]

The table covers only the documents filed with the IATF. Many OEMs also govern complaint handling through their own supplier manuals and portals, which are not public, and 8D may well be required there.

Assessment: “IATF requires 8D” is wrong; “the automotive industry works with 8D” is right. In practice that means defining in your own procedure which method applies when, and recording per customer which format that customer requires. The other requirements of the automotive standard are covered in the article on IATF 16949 audit requirements; the upcoming second edition in IATF 16949, 2nd edition.

Deadlines: the report and the fix run on two clocks

Ford’s requirements show the tension VDA describes quite precisely. After 15 calendar days an 8D is due with a preliminary or verified root cause, plus a plan for corrective and preventive actions [4]. The deadline does not demand a proven cause after 15 days — it demands a status.

Assessment: the most common failure is submitting a preliminary cause as a verified one because the form has no way to tell them apart. An 8D that marks a preliminary cause as preliminary and names the date for confirmation is more honest, and easier to defend in an audit, than one whose D4 is quietly swapped out three weeks later.

8D and ISO 9001: the same duties in a different order

8D is not a requirement on top of ISO 9001 but one way of carrying out clause 10.2. The mapping is fairly direct:

ISO 9001:2015, 10.2.1 [2]	IATF 16949, 10.2.3 [3]	8D
a) react, control, correct, deal with consequences	b) containment, interim actions	D0, D3
b) review the nonconformity, determine causes, check for similar cases	c) root cause analysis with method and results	D2, D4
c) implement action needed	d) systemic corrective actions, including similar processes	D5, D6
d) review effectiveness	e) verify effectiveness	D6, D8
e) update risks and opportunities; f) change the QMS	f) update PFMEA, control plan	D7

ISO 9001:2026 keeps 10.2.1 in this structure [8], so the mapping survives the transition; what changes elsewhere is covered in every change in ISO 9001:2026. How the corrective action process under ISO 9001 fits together as a whole is set out in the article on the CAPA process.

When 8D, when 5 Whys?

IATF 16949 clause 10.2.3 a) explicitly requires different approaches depending on the type and scale of the problem, and lists audit findings alongside field failures and manufacturing issues [3]. An audit finding can trigger an 8D just as a customer complaint can.

Assessment: three questions separate the cases fairly reliably:

1. Is the customer affected, or does it prescribe a format? Then its format applies.
2. Does the fix need several functions? A facilitated team is the core of 8D; if one person can find and remove the cause alone, 8D is overhead.
3. Is it unclear why the defect was not detected? Then you need the second chain — which points to 8D rather than a single 5 Whys.

For one-off cases with an obvious cause, the 5 Whys method is enough. How audit findings flow into a root cause analysis is described in the article on findings and CAPA.

Where 8D breaks in practice

Three places, almost always the same:

• D3 without evidence of effect. Containment is running, but nobody has shown that it actually protects the customer.
• D4 with one chain. The occurrence cause is well analysed; the non-detection cause is one sentence.
• D7 without feedback. The lesson reaches neither the FMEA nor similar parts — which is precisely what IATF 16949 clause 10.2.3 d) and f) require [3].

A report that runs through D1 to D8 formally but ticks one of these boxes for show satisfies the form and misses the point.

How qportal handles it

In qportal, 8D is a guided process rather than a form. Progress per discipline is derived from what has been recorded, not from a checklist someone maintains. D1 requires roles, including a facilitator; D2 is structured into the five questions what, where, when, who and how many. D4 keeps the occurrence and non-detection chains apart, each as a why-chain. Containment, corrective and preventive actions from D3, D5/D6 and D7 become regular actions with an owner and a due date; D5/D6 counts as done only once the effect has been checked, not merely the implementation. Submission for the effectiveness review stays locked until D1 to D7 are complete. An 8D can be started directly from an audit finding and exported as a PDF report for the customer.

Details are on the 8D report page; the individual steps are in the 8D documentation.

Conclusion

8D is not a form but a process with built-in checkpoints: the effect of containment, the second cause chain, the feedback into prevention. The method is prescribed not by IATF 16949 but by the customer — and even there less uniformly than is often claimed. Anyone using 8D should keep two things apart: the deadline for the report and the time a proven cause takes.

Sources

1. VDA QMC: 8D — Problemlösung in 8 Disziplinen. Methode, Prozess, Bericht. First edition, November 2018; product page noting the current edition and the distinction from complaint handling. https://webshop.vda.de/QMC/de/8d-probleml%C3%B6sung-in-8-disziplinen (accessed 2026-09-30). The volume itself is paid; statements about its content are paraphrased.
2. ISO 9001:2015, Quality management systems — Requirements, consulted in the bilingual edition DIN EN ISO 9001:2015-11, Beuth Verlag, Berlin. Clause 10.2.1.
3. IATF: IATF 16949:2016 — Sanctioned Interpretations (SIs). Status November 2025, including SI 20 on clause 10.2.3 (issued December 2020, effective January 2021) and SI 12 on 5.1.1.2. https://www.iatfglobaloversight.org/wp/wp-content/uploads/2025/11/IATF-16949-SIs-Nov-2025.pdf (accessed 2026-09-30)
4. Ford Motor Company: Customer Specific Requirements for IATF 16949:2016. Effective June 2026, section 10.2 and “Customer Concerns”. Published via IATF Global Oversight. https://www.iatfglobaloversight.org/wp/wp-content/uploads/2026/06/Ford-IATF-CSR_Jun-2026-SCCAF_Final.pdf (accessed 2026-09-30)
5. General Motors: Customer Specific Requirements for IATF 16949. Effective 2025-10-30, clause 10.2.3. https://www.iatfglobaloversight.org/wp/wp-content/uploads/2025/10/IATF-16949-GM-Customer-Specific-Requirements-October-2025.pdf (accessed 2026-09-30)
6. BMW Group: Customer Specific Requirements for IATF 16949:2016. April 2021. https://www.iatfglobaloversight.org/wp/wp-content/uploads/2021/04/BMW-Customer-Specific-Requirements_APR2021.pdf (accessed 2026-09-30)
7. Mercedes-Benz AG: Customer Specific Requirements for IATF 16949. February 2022. https://www.iatfglobaloversight.org/wp/wp-content/uploads/2022/03/Mercedes-Benz-AG-IATF-16949-CSR-February-2022.pdf (accessed 2026-09-30)
8. ISO/DIS 9001:2025(en): Quality management systems — Requirements. ISO/TC 176/SC 2, committee ballot 2025-08-27 to 2025-11-19. Not publicly available; checked against a copy on 2026-09-30 (clause 10.2.1) — not the published IS edition.

Consultancy, certification-body and content-marketing pages are not cited. Normative text is copyrighted; requirements are paraphrased with their clause reference. Where this text goes beyond the documented evidence, it is marked as an assessment.