If you supply more than one automotive customer, you've probably noticed that "send us an 8D" doesn't mean the same thing everywhere. Ford wants a Global 8D with a D0 and an escape point. German OEMs often point you to the VDA 8D approach, with its focus on occurrence and non-detection. Everyone else accepts some version of a standard 8D.
The good news is that all three are the same method underneath. The differences are in emphasis, terminology and a few extra steps. This guide compares Ford G8D vs VDA 8D vs the standard 8D, discipline by discipline, so you can write one solid analysis and present it the way each customer expects.
A short history
The 8D method grew out of Ford's Team Oriented Problem Solving (TOPS) approach in the late 1980s. Ford later evolved it into the Global 8D (G8D), which added a preparation step, D0, and formalized the idea of the escape point. Other industries adopted the eight disciplines in a more generic form, which is what most people now call the standard 8D.
The German automotive association VDA later published its own guidance on 8D problem solving. It keeps the eight disciplines but puts strong emphasis on separating the cause of occurrence from the cause of non-detection, and on proving the effectiveness of actions.
In North America, the AIAG's CQI-20 guideline on effective problem solving is another reference that customers sometimes cite. It isn't a separate 8D format, but it reinforces many of the same expectations.
The big differences at a glance
| Topic | Standard 8D | Ford Global 8D | VDA 8D |
|---|---|---|---|
| Preparation step | Not required | D0: emergency response actions and decision to start a G8D | Not a separate numbered step in most templates; immediate actions are usually covered in D3 |
| Detection side of D4 | Often included as "non-detection" | Required as the "escape point" | Required as "root cause of non-detection" |
| Systemic causes | Often left to D7 | Addressed in D7 (prevent recurrence) | Strong emphasis on systemic and process causes |
| D5 language | Permanent corrective actions | Choose and verify permanent corrective actions (PCAs) | Planned corrective actions with proof of effectiveness |
| D6 language | Implement and validate | Implement and validate PCAs | Implemented corrective actions and effectiveness check |
| D8 language | Closure and recognition | Recognize team and individual contributions | Closure and team success |
Always confirm details against your customer-specific requirements (CSRs). Many OEMs publish their own templates and portals that override the generic form.
Discipline by discipline
D0: Only in Ford Global 8D
D0 asks whether the problem warrants a G8D and what Emergency Response Actions (ERAs) are needed right now to protect the customer. ERAs are the very first moves, often within hours: stop shipment, sort at the customer, switch to known-good stock.
If you're writing a standard or VDA 8D, you'll typically cover the same immediate actions in D3. If you're writing a G8D, don't leave D0 thin. Reviewers look at it to judge how quickly you reacted.
D1: Team
All three formats agree here: a cross-functional team with a champion or sponsor and a leader. Ford's G8D places weight on having process knowledge and authority on the team. VDA guidance similarly stresses that the team needs the right expertise and the mandate to act.
D2: Problem description
All three expect a precise, data-based description. In practice:
- Ford G8D reviewers expect a clear problem statement and an Is / Is Not analysis
- VDA 8D emphasizes describing the deviation against the requirement objectively, with data, and avoiding assumptions about the cause
- Standard 8D typically uses 5W2H
These tools work together. A 5W2H statement plus an Is / Is Not table will satisfy any of the three.
D3: Containment
Same purpose everywhere: protect the customer until the permanent fix is in. Ford calls them Interim Containment Actions (ICAs) and distinguishes them from the ERAs in D0. VDA expects containment to be effective and verified, covering all stock and the supply chain.
Whatever the format, show quantities, locations, the sorting method and proof that the sort catches the defect.
D4: Root cause. This is where formats differ most
All three expect you to find out why the defect happened and why it wasn't detected. They frame it differently:
- Ford G8D: identify and verify the root cause and the escape point. The escape point is the earliest place in the process where the problem should have been detected but wasn't. You need corrective actions for both in D5.
- VDA 8D: identify the root cause of occurrence and the root cause of non-detection, both verified. VDA guidance also pushes teams to look at the systemic level: why did the management system allow this?
- Standard 8D: root cause plus, in good reports, a non-detection cause. Weaker templates only ask for one root cause, which is a common reason reports get rejected by automotive customers.
In practice, if you always write two verified causes (occurrence and escape/non-detection), you'll satisfy all three. Our guide on how to write a D4 root cause shows the structure.
D5: Corrective actions
Ford talks about choosing and verifying Permanent Corrective Actions (PCAs) for both the root cause and the escape point, before implementation. VDA separates planned actions in D5 from implemented ones in D6, and expects proof of effectiveness. The standard 8D lists permanent corrective actions with owners and due dates.
The common thread: every root cause gets an action, and each action is proven to work.
D6: Implementation and validation
Ford: implement and validate the PCAs, then remove the ICAs. VDA: record the implemented actions and check their effectiveness over time. Standard: implement, validate, end containment.
Make sure you state when and how containment was removed. It's a detail reviewers check in every format.
D7: Prevent recurrence
All three want you to fix the system: update FMEAs, control plans, procedures and standards, and spread the lesson to similar products and processes. Ford's G8D uses D7 to address the systemic weaknesses that allowed the problem and its escape. VDA reports often include this systemic thinking earlier, in D4, and then show the resulting changes in D7.
D8: Closure
The same in spirit: confirm completion, close formally and recognize the team. Ford's wording specifically mentions recognizing both team and individual contributions.
Which format should you use?
Simple rule: use what the customer asks for, in their template if they have one. If they don't specify:
- Supplying Ford: G8D, including D0 and the escape point
- Supplying German OEMs or their Tier 1s: VDA-style 8D with separate occurrence and non-detection causes
- Everyone else: a standard 8D, but still include both occurrence and non-detection causes
Many suppliers keep one internal analysis and present it in different customer formats. That works well as long as the underlying analysis is complete. The format can't rescue a shallow root cause.
Writing one 8D that works for every customer
If you build every investigation to the strictest common denominator, the format becomes a presentation choice rather than extra work:
- Record emergency actions from the first hours, even if your format has no D0
- Write D2 with both 5W2H and Is / Is Not
- Verify containment effectiveness in D3
- Always find and verify two causes in D4: occurrence and escape
- Give every cause an action in D5, with verification
- Show effectiveness over time in D6
- Name the documents changed and the read-across in D7
Vantage 8D lets you pick Standard 8D, Ford Global 8D or VDA 8D per report. The section headings, the D0 step and the AI's wording change to match, and the export carries the right document title. You can also try the disciplines for free with our 8D report template.