8D report: what it is and how to fill it in step by step

An 8D report is the document a supplier uses to show a customer how it resolved a complaint or a recurring defect. It has eight steps, D1 to D8: team, problem description, immediate actions, causes, planned and implemented corrective actions, preventing recurrence and recognizing the team [1]. The customer needs to read three things from it: defective parts are no longer shipping, you know the real cause, and you have verified that the defect will not come back.

The German Association of the Automotive Industry (VDA) describes 8D as the standard procedure a supplier and a customer use to resolve a complaint together [1]. Below is what belongs in each step, where reports get stuck and what helps so that an 8D doesn’t take a whole week to assemble from e-mails.

When will a customer ask you for an 8D report?

When it is in their supplier quality manual, in the contract or directly in the complaint. An example from the Czech Republic: one of the large Czech engineering manufacturers reserves the right in its supplier quality manual to request an 8D report for a serious or recurring problem. For complaints, it wants the root cause identified and corrective actions defined. It requires the supplier’s first response no later than two business days after notification [2].

Deadlines, form and scope are therefore set by the customer. One sends its own form, another wants the data electronically. For electronic exchange of complaint data, the VDA has the QDX format [1]. Read each customer’s quality manual before a complaint arrives, and write down by when they want which steps.

The ISO 9001 standard does not prescribe a specific method. But clause 10.2 asks for the same things an 8D documents: react to the nonconformity and deal with its consequences, determine the cause, check whether a similar nonconformity could occur elsewhere, implement actions, review their effectiveness and keep a record of it [3]. The ISO 9001:2026 revision also contains clause 10.2 [4]. An 8D report is one way to meet and document this requirement.

The requirements for 8D are set by your customer’s contract and quality manual. This is neither legal advice nor an interpretation of the standard. For a specific case, contact your certification body or quality management consultant.

What goes into steps D1 to D8?

The step names follow the VDA [1]. The content of the columns is a recommendation. What exactly your customer wants, you will find in their form.

Step	What it answers	What belongs in the report
D1 Team	Who is handling the complaint?	The resolution lead and people from quality and production, possibly from purchasing or engineering. A role for each.
D2 Problem description	What exactly is wrong?	Complaint number, product, batch or production date, number of defective parts, photos, deviation from the requirement or drawing.
D3 Immediate actions	How do you stop defective parts from going further?	How many parts you have held in the warehouse, in transit and at the customer, how you are sorting them and from which batch you are shipping inspected parts.
D4 Causes	Why did the defect occur and why did nobody catch it?	Verified causes with evidence, not assumptions. The analysis method, for example 5 Whys or an Ishikawa diagram.
D5 Planned corrective actions	What will you change so the cause disappears?	An action for each cause, a responsible person and a deadline.
D6 Implemented corrective actions	Does it work?	From when and from which batch the action applies and how you verified effectiveness. Only then lift the immediate actions from D3.
D7 Prevent recurrence	Where else could this happen?	Updates to work instructions, the control plan or FMEA. The same action on similar products and lines.
D8 Team recognition	Is it done?	Closure date, customer approval, stored documentation and thanks to the team.

How do you find the real cause in step D4?

The VDA calls D4 a particularly important step. All causes that explain the problem should be examined systematically [1]. According to the VDA, the root cause is the one that cannot be traced any further, even when you repeatedly ask why the error occurred [1]. This is what the 5 Whys method is built on.

Look for two causes:

1. Why the defect occurred. For example a badly set-up machine, defective material from a supplier or an unclear drawing.
2. Why inspection didn’t catch it. PALSTAT CAQ, for example, calls this the escape point: the place in the process where the problem should have been detected and caught [5].

Follow each cause all the way to the process that failed. The VDA advises phrasing it with “due to”, for example “the hole occurred due to the welding process” [1]. It also sorts causes into categories by the product’s life phase: development, production, logistics, or cause unknown [1].

Two answers are not enough in D4: “operator error” and “we will retrain people”. Operator error is the start of the questions, not the end. Why did the procedure allow the error? Why didn’t inspection catch it? And retraining alone does not change the process. If the same mistake can be made again, it will come back.

Why does an 8D report take a week to put together?

The inputs for an 8D tend to be scattered. The complaint came by e-mail, the photos are on a phone, batches are in the accounting software, inspection records are on paper and measurements in Excel. The writing itself is usually quick. What slows things down is searching for information, most of all in step D3, when you need to know fast which batches the defect affects and who they were shipped to.

What helps, even without new software:

1. Record the nonconformity at the line immediately, with a photo, quantity and batch. Not in an e-mail in the evening.
2. Record batches at receiving and at shipping. Without them, in D3 you don’t know exactly what to hold, and you hold more than you have to. In POHODA, tracking numbers can only be kept for stock items of the Card or Product type, and you cannot add them retroactively to earlier movements [6]. It therefore pays to turn tracking on before the first complaint arrives.
3. Manage complaints in your accounting software or ERP. POHODA has a Complaints module with three types (customer, purchase and warehouse) and with statuses, but it is for record-keeping only [7]. ABRA Flexi has no separate complaints module. Complaints are handled there as a special type of received order, optionally with a dedicated complaints warehouse [8]. ABRA Gen works with a complaints warehouse and can also rate suppliers by the number of complaints [9]. The team, causes and actions with deadlines from the 8D are then kept alongside.
4. Set deadlines for the steps, not just for the whole report. The immediate actions from D3 and the actions from D5 and D6 need an owner and a date. Plan the effectiveness check right away, for example inspecting the next several deliveries.
5. Build the report from data, not from memory. When the nonconformity, photos, batches and actions are in one record, the 8D is just an export into the customer’s form.

When is a Word template enough and when do you need software?

Your situation	What is usually enough
A few complaints a year, one customer asks for 8D	A Word or Excel template based on their form and a shared folder for photos and documents. Don’t connect anything.
Complaints every month, several customers, defects keep coming back	One nonconformity register with photos and batches, action deadlines with reminders and an 8D export straight from the record. Plus a connection to the accounting software or ERP where you keep batches and complaints.
Automotive with FMEA, SPC and PPAP requirements	A CAQ system. The Czech PALSTAT CAQ, Q-LanYs, EISOD and KTK QMS have modules for nonconformities, complaints and 8D [5][10][11][12].

Automation makes sense mainly in the middle row. In the first, a template is enough; in the third, a ready-made quality system.

How we do it

When we record a nonconformity in our own packing operation in Kuřim, our batch records can block a delivery or batch and list which batches were made from it and who they were shipped to. For each batch, it also traces back the raw material delivery. That is exactly what an 8D report needs in steps D3 and D4.

Sources

1. VDA QMC – Definition of Failure Cause Categories for 8D Reporting V1.0 (2017, free version): steps D1 to D8, 8D as the standard complaint procedure between supplier and customer per VDA Volume 4, the importance of D4, definition of the root cause, the “due to” phrasing, cause categories, the QDX format. https://vda-qmc.de/wp-content/uploads/2023/01/VDA_Volume_8D__V1.0__EN__English.pdf
2. Supplier quality manual of a Czech engineering manufacturer (valid from 1 Nov 2021), ch. 7 Approval of deviations and ch. 8 Complaints.
3. Auditor Training Online – ISO 9001 Clause 10.2 Nonconformity and Corrective Action (unofficial interpretation; the text of the standard is paid). https://blog.auditortrainingonline.com/blog/iso-9001-clause-10.2-nonconformity-and-corrective-action
4. PJR – ISO 9001:2026: What’s Changed (Not Much), and What Has Stayed the Same (A Lot). https://www.pjr.com/iso-standards-and-technical-updates/iso-90012026-whats-changed
5. PALSTAT CAQ – Global 8D report: stop card, team, immediate actions, cause classification, escape point, corrective actions with deadlines. https://www.palstat.cz/kvalita/neshody/global-8d-report/
6. Stormware – POHODA, Tracking numbers (Evidenční čísla). https://www.stormware.cz/prirucka-pohoda-online/sklady/evidencni_cisla/
7. Stormware – POHODA, Complaints and Service modules (Agendy Reklamace a Servis). https://www.stormware.cz/prirucka-pohoda-online/Sklady/Agendy_Reklamace_a_Servis/
8. ABRA Flexi – Complaints. https://podpora.flexibee.eu/en/articles/4500558-complaints
9. ABRA – ABRA Gen: production, warehouse and logistics. https://www.abra.eu/ai-facts/abra-gen/vyroba-sklad-logistika/
10. Q-LanYs – CAQ quality management system (complaint management); Tasks, nonconformities, projects, APQP (resolving nonconformities with the 8D method, printing 8D reports). https://qlanys.cz/cz/caq-system-rizeni-jakosti ; https://qlanys.cz/cz/ukoly-neshody-projekty-apqp
11. EISOD X. https://www.eisod.com/
12. KTK Software – KTK QMS. https://ktksoftware.cz/qms

Are you assembling 8D reports from e-mails?

In a free 30-minute audit, we will go through where the inputs for your 8D reports come from: complaints, photos, batches and inspection records. We will also tell you when a Word template is all you need. We handle batch records from receiving to shipping in warehouse automation. Running POHODA? See how we integrate POHODA. For ABRA, you will find more on the ABRA Gen and ABRA Flexi pages.