Workflow · D2 · The D-steps
D2 — Containment action
D2 is the first thing the customer sees. Containment failure is the fastest way to lose customer trust in an 8D — worse than a slow root cause. This page describes how to scope containment, verify it and communicate it.
Key takeaways
- Define the suspect batch by date, lot, shift, tool or cavity — with margin.
- Quarantine before sorting.
- Add 100% inspection at the escape point until D6 is verified.
- Communicate containment status to the customer with numbers, not adjectives.
How to scope containment
Containment scope is defined by the suspect population, which is broader than confirmed defective units.
- Time boundary: first suspect date backwards to last known-good, forwards to last shipped.
- Process boundary: line, tool, cavity, shift, operator, material lot.
- Location boundary: plant, warehouse, in-transit, distribution centre, customer site.
Typical containment actions
- Quarantine hold on suspect inventory (plant + downstream).
- 100% sort using a defined, capable inspection method.
- Escape wall / firewall inspection at the outbound step.
- Customer notification with interim response.
- Stop-ship on affected part numbers if risk warrants.
How to verify containment is working
Containment effectiveness must be visible. Daily metrics beat weekly summaries.
- Sort yield by lot: how many defective units are the sorters finding?
- Firewall escapes: any defective units passing the outbound wall?
- Customer feedback: any new complaints after containment start date?
Common mistakes
- Scoping containment on confirmed defects only, leaving the wider suspect population unchecked.
- Using the same operators who missed the defect to sort — with no method change.
- Removing containment before D6 verification is complete.
In the Qhubio 8D workspace
How Qhubio handles D2 containment
The D2 phase in Qhubio captures suspect scope, containment actions and their verification status as structured fields — not free text buried in a Word document.
- Suspect population defined by batch, line, tool or lot.
- Containment actions tracked with owner, due date and evidence.
- Phase-gated approval before D3 can be advanced.
Frequently asked questions
- Is D2 the same as corrective action?
- No. D2 is temporary containment — it stops the bleed. D5–D6 corrective action fixes the cause so containment is no longer needed.
- When can containment be removed?
- Only after D6 corrective action is verified with production data over an agreed observation window.
- How fast must containment be in place?
- Automotive customers typically expect containment within 24 hours of notification. Most industries expect the same in practice, even without a written rule.
Related guides
The D-steps
D1 — Establish the 8D team
How to build the right 8D team in D1 — roles, size, authority and the difference between a working team and an attendance list.
The D-steps
D3 — Describe the problem
D3 quantifies the problem with Is/Is-Not and prepares D4 root cause analysis. Learn what a good problem description looks like.
The D-steps
D5 — Verify effectiveness
D5 verifies that the chosen corrective action actually eliminates the defect in production — not just in the lab. Learn the verification methods.
Getting started
The 8D steps explained
Walk through each of the 8D steps — D1 team, D2 containment, D3 problem description, D4 root cause, D5–D8 corrective action, prevention and closure.
Run this D-step inside a structured workspace
Qhubio is a structured 8D workspace: evidence-grounded phases, phase-gated approvals and audit-ready exports.