8D Report in Practice (Part 1): Steps D1–D4 for Automotive

Pavel Ryvola 01. 09. 2026
8D Report in Practice (Part 1): Steps D1–D4 for Automotive

8D Report in Practice (Part 1): From Defect Notification to the Real Root Cause

You know the drill. The phone rings, the OEM customer's name flashes on the screen, they immediately report a line issue, send a photo of a defective part, and demand an urgent response. The clock is ticking, and you have to start working on an 8D report.

In this first part, we will look at how to manage the initial chaos, stop bleeding money, and most importantly – how to find the real reason things went wrong right at the machine.

D1: Team Formation (Get Out of the Office)

On paper, everything looks good, so many quality engineers just list managers' names in D1 to make it look professional. The customer might let it slide, but it won't help you solve the problem.

  • Practical Tip: If the defect started occurring on the night shift, you need the machine setter who was there at the time on your team. You need a production operator from that specific workstation. If you don't have shop-floor people in D1, you stand almost no chance of finding the real root cause.

D2: Problem Description (Define It Precisely)

Writing "Customer claims non-conforming part" in the report is a guaranteed way to show your incompetence right from the start. The description must be so precise that anyone reading it knows exactly what to look for.

  • Practical Tip: Always use the 5W2H method (Who, What, Where, When, Why, How, How many). Attach a photo of a good (OK) and a bad (NOK) part with the defect clearly marked. Include batch numbers, the exact position on the part, and how the defect physically manifests at the customer's site. In short, include everything that helps specify the defect. Extract information, interview the customer, and involve your Resident Engineer.

D3: Interim Containment Actions (ICA)

This is about one thing: stopping the bleeding. The customer must be absolutely sure that from tomorrow on, they will only receive 100% inspected parts, and you won't throw money away on external sorting.

  • Practical Tip: It is not enough to just order the sorting of finished goods in the warehouse. What about Work in Progress (WIP)? And what about the parts already sitting in a truck on their way to the customer? Containment must cover the entire supply chain. There is nothing more embarrassing than sending the customer an 8D with D3 closed, only for another pallet of defective parts to arrive the next day.
  • Practical Tip: Start with yourself and verify your process. Most defects that make the customer call you are systematic, meaning you likely have defective parts on your own line or in your warehouse. You can start analyzing immediately without waiting for the NOK part to be returned.

visualization of immediate containment actions

D4: Root Cause Analysis (RCA)

This is where 80% of all 8D reports fail. If you write "operator error" in D4, you are begging the customer to throw the report back at you. People don't make mistakes on purpose. Your job is to find out why the system allowed them to make the mistake and why it failed to detect the defect. Moreover, in automotive, a strict rule applies: you must always define two independent root causes.

  • Practical Tip (Root Cause of Occurrence): Go to the shop floor, use an Ishikawa diagram to break down possible causes, and drill down using the 5 Whys. Why did the clip pop out? Because it lacked pre-tension. Why did it lack pre-tension? Because the hole in the plastic was too large. Why was it too large? You discover that the error originated in the design itself – the CAD data did not account for actual material shrinkage. The root cause of occurrence, therefore, does not lie in production, but in the engineering design.
  • Practical Tip (Root Cause of Non-Detection): Why did the defective part with a loose clip pass through the rest of the line and end up in the customer's pallet? This is a step many people forget. The operator did push the clip into the hole, it looked seated from the visible side, and a visual inspection was performed. However, missing mechanical pre-tension cannot be seen by the naked eye. The root cause of the escape is the fact that visual inspection is blind to this type of defect, and there is no physical strength detection on the line.
Save time: Drawing an Ishikawa diagram in Excel is a nightmare. For a quick breakdown and instant export to a professional PDF, try our free Ishikawa diagram generator at nastrojekvality.cz, which does not store any data.