Back to Blog
Problem Solving

8D Report Example: A Complete, Filled-In 8D With Explanations

A full 8D report example for a real-world automotive defect, written discipline by discipline, with notes on why each section is written the way it is.

Vantage 8D TeamNovember 7, 20268 min read

Most guides explain what goes into each discipline. Very few show you a complete 8D report example from start to finish, written the way a customer quality engineer expects to receive it. This article does exactly that.

Below is a fully filled-in 8D for a realistic automotive defect. The company, part numbers and people are fictional, but the problem, the analysis and the actions are typical of real supplier 8Ds. After each discipline there's a short note on why it's written the way it is, so you can apply the same thinking to your own reports.

The situation

A Tier 1 supplier assembles fuel line quick connectors. Each connector has two O-rings, placed automatically by a pick-and-place station and checked by a vision camera. The OEM's assembly plant reports a fuel leak at end-of-line leak test. Teardown shows a connector with one O-ring missing.

One leak at the OEM triggers a formal complaint and a request for an 8D within the usual 24-hour / 10-day / 30-day timeline.

The completed 8D report example

Header information

FieldEntry
Report no.8D-2026-00117
Customer complaint no.QN-448213
PartQuick connector assembly, P/N QC-8812-A
DefectMissing secondary O-ring, fuel leak at customer EOL test
Date of occurrence2 October 2026 (customer detection)
Production date28 September 2026, Line 3, night shift
FormatStandard 8D

D1: Team

RoleNameFunction
ChampionR. OkaforOperations Manager
Team leaderD. LindqvistCustomer Quality Engineer
MemberP. VargaAutomation Engineer, Line 3
MemberS. ChenProcess Engineer
MemberM. AlvarezNight Shift Team Leader
MemberK. BrandtVision Systems Technician

Why it's written this way: the champion has authority to stop the line and approve spending. The team includes the people who own the O-ring station and the camera, plus someone from the shift that built the parts.

D2: Problem description

On 2 October 2026 the customer's Plant 7 detected a fuel leak at end-of-line test on one vehicle. Teardown found quick connector QC-8812-A (lot L0928-N3, built 28 September, Line 3, night shift) with the secondary O-ring missing. The primary O-ring was present and correctly seated. One defect confirmed out of 6,400 connectors delivered from the lot (156 ppm). The customer requires both O-rings present per drawing QC-8812-A rev F, note 4.

IsIs Not
WhatSecondary O-ring missingPrimary O-ring missing, damaged O-rings
WhereLine 3Lines 1 and 2 (same design)
WhenNight shift, 28 SeptemberDay shifts, earlier lots
Detected byCustomer leak testOur vision check, our sample leak test

Why it's written this way: it states facts, quantities and the exact requirement, with no guesses about the cause. The Is / Is Not table already points the team toward Line 3 and something that changed around 28 September.

D3: Interim containment actions

ActionLocationQuantityResultOwnerDate
Quarantine and sortCustomer Plant 74,100 pcs0 defects foundD. Lindqvist (with customer)3 Oct
Quarantine and sortOur warehouse2,300 pcs1 defect foundM. Alvarez2 Oct
Quarantine and sortWIP, Line 3900 pcs0 defects foundM. Alvarez2 Oct
Stop shipments from Line 3 until 100% manual check addedLine 3n/aIn placeR. Okafor2 Oct

Sort method: 100% visual check of both O-ring grooves under 3x magnification, plus 100% leak test at 1.5 bar. Certified parts identified with a blue "C" label until D6 is closed. Sort effectiveness was confirmed by seeding 10 parts with a missing secondary O-ring into a tote: all 10 were found.

Why it's written this way: every location is listed with quantities and results, there's a clear way to identify certified parts, and the sort itself is proven to work. Customers check these details first.

D4: Root cause analysis

The team built an Ishikawa diagram across man, machine, method, material, measurement and environment, then ran a 5-Why on the two most likely branches: the O-ring placement station and the vision check.

Occurrence root cause (why the O-ring was missing): The vacuum gripper on the secondary O-ring station intermittently dropped O-rings during transfer. The vacuum line filter was partially blocked, which reduced vacuum to roughly 55% of nominal. The filter is not on the preventive maintenance plan, so it had not been changed since the station was installed.

Verification: with the blocked filter installed, the station dropped 7 O-rings in 1,000 cycles. With a new filter, zero drops in 3,000 cycles. The defect could be switched on and off by switching the filter condition.

Escape root cause (why the vision camera passed the part): On 26 September the Line 3 nest fixture was replaced after a crash. The new fixture positions the part about 2 mm lower. The camera's inspection window was not re-taught, so it was checking an area above the secondary groove. The camera recipe is not under change control, and the fixture change checklist does not include re-validating the camera.

Verification: with the current recipe, 10 of 10 parts with a missing secondary O-ring passed. After re-teaching the window, 10 of 10 were rejected.

Why it's written this way: there are two separate, verified root causes, one for occurrence and one for escape, each with evidence that turns the defect on and off. That's what makes a D4 credible. Our guide on writing a D4 root cause goes deeper on this structure.

D5: Permanent corrective actions

Root causeActionOwnerDueVerification
Blocked vacuum filterReplace filter; add vacuum pressure sensor with alarm and auto-stop below 80% nominalP. Varga9 Oct3,000-cycle run, zero drops; alarm triggers when filter is restricted
Filter not on PM planAdd filter replacement every 4 weeks to PM planMaintenance Lead9 OctPM plan rev C approved
Camera window not re-taughtRe-teach window; add a daily master part check (one good part, one part with each O-ring missing) at shift startK. Brandt4 OctMaster parts detected 10 of 10 runs
Vision recipe not controlledPut camera recipes under change control; add camera re-validation to the fixture change checklistS. Chen16 OctProcedure WI-ENG-022 rev B released

Why it's written this way: every root cause from D4 maps to at least one action, each action has an owner and a due date, and each has a defined verification. Notice that the strongest actions are automatic (sensor and auto-stop) rather than "operator to check filter."

D6: Implementation and validation

All D5 actions were implemented by 16 October. Validation period: 8 weeks of production on Line 3 (about 210,000 connectors).

Results:

  • Zero missing O-rings found at the camera, at our sample leak test, or at the customer
  • Daily master part check passed on every shift
  • Vacuum alarm triggered once (week 5) during a filter change; the station stopped as designed

The 100% manual check and the blue "C" label were removed on 11 December with customer approval.

Why it's written this way: validation runs long enough to cover the conditions that caused the problem, uses measurable criteria, and records exactly when and how containment ended.

D7: Prevent recurrence

  • PFMEA for O-ring assembly updated: new failure mode "O-ring dropped during transfer due to low vacuum," occurrence rating reduced from 6 to 2 with the vacuum sensor, detection rating reduced from 7 to 3 with the master part check
  • Control plan updated with the daily master part check and vacuum monitoring
  • Read-across: all 11 vacuum pick-and-place stations in the plant checked. Two more blocked filters found and replaced on Line 1; sensors added to all stations by 20 November
  • Read-across: all 6 vision systems now under recipe change control
  • Lesson learned added to the engineering change checklist used for every fixture or tooling change

Why it's written this way: D7 names the documents that changed and shows the team looked beyond the one station that failed. Finding two more blocked filters on another line is exactly the kind of evidence customers like to see.

D8: Closure

All actions are complete and verified. The customer accepted the 8D on 15 December 2026. Approved by R. Okafor (Champion) and the Quality Manager on 15 December 2026. The team presented the findings at the December plant quality review and received the site's quarterly improvement award.

What makes this 8D report example strong

If you only take a few things from this example, take these:

  1. D2 is pure fact. No guesses, no blame, just what, where, when and how many, with the requirement quoted.
  2. D3 covers the whole pipeline and proves the sort works.
  3. D4 has two verified root causes, one for occurrence and one for escape.
  4. D5 maps one-to-one to D4, with automatic controls favored over reminders.
  5. D7 reaches beyond the failed station and updates the living documents.

Use this structure for your own reports

You can copy this layout straight into the free 8D report template, which follows the same disciplines and exports to a clean document. If you're new to the method, start with our guide to the 8 disciplines explained.

And if you'd rather not spend an afternoon formatting tables, Vantage 8D turns your rough notes into a report in this format, builds the Ishikawa diagram for D4, and exports to Word or PDF with your company's logo and a proper sign-off block.

Try AI-Powered 8D Reporting Free

Generate complete 8D reports, run AI-guided 5-Why analyses, and evaluate supplier 8Ds — all in one place.