Workflow · D5 · The D-steps
D5 — Permanent Corrective Action
D5 turns the proven causes from D4 into a permanent corrective action. The action must address the actual occurrence or escape mechanism, not an assumption, and it must be feasible to own, implement and validate.
Key takeaways
- Link every action to a specific D4 finding and evidence.
- Separate immediate containment from the permanent change that removes the mechanism.
- Assess feasibility, side effects, customer impact and ownership before rollout.
- Define the implementation evidence and validation criteria that D6 will use.
Select actions against proven causes
- Occurrence cause: change the condition that created the defect.
- Escape cause: strengthen or redesign the control that failed to detect it.
- Evidence link: record which D4 finding and test support the action.
- Alternatives: reject actions that only retrain, remind or inspect without addressing the mechanism.
Plan ownership and implementation
- Named owner, due date, affected process and required approvals.
- Feasibility, safety, quality and customer-impact review.
- Implementation evidence: change record, parameter release, work instruction, tooling or control update.
- Validation plan: metric, observation window and source of objective production evidence for D6.
Hand off to implementation and validation
D5 chooses the permanent corrective action. D6 proves it was implemented as intended and works in production. Do not treat a planned action as validated effectiveness.
Common mistakes
- Selecting an action before D4 proves the mechanism.
- Using retraining or extra inspection as the only response to a design or process cause.
- Calling an approved action effective before it is implemented and validated.
In the Qhubio 8D workspace
How Qhubio structures D5
Qhubio keeps corrective actions linked to the investigation evidence and ready for controlled implementation and validation.
- Actions tied to occurrence and escape-cause findings.
- Ownership and evidence retained with the phase.
- A clear handoff to D6 implementation and validation.
Frequently asked questions
- Is D5 the same as containment?
- No. D3 is temporary interim containment. D5 selects the permanent corrective action against the proven cause.
- Can an action be chosen before the cause is proven?
- A team can evaluate options, but a permanent action should not be approved as the solution until D4 evidence supports the mechanism it addresses.
- What proves a D5 action worked?
- D6 provides the implementation and validation evidence. D5 defines what must be implemented and how success will be measured.
Related guides
The D-steps
D4 — Root Cause Analysis
D4 identifies and proves the root cause and escape cause. Learn how to move from candidate causes to proven root cause in 8D.
The D-steps
D6 — Implementation & Validation
D6 implements the approved corrective action in a controlled way and validates it with objective evidence that the action works in production.
The D-steps
D7 — Prevent Recurrence
D7 prevents recurrence by updating PFMEA, control plan, work instructions, training and supplier controls so the problem cannot come back.
The D-steps
D3 — Interim Containment
D3 contains the immediate risk while the investigation continues: define the suspect population, quarantine or inspect affected product, communicate clearly and verify that containment is effective.
Run this D-step inside a structured workspace
Qhubio is a structured 8D workspace: evidence-grounded phases, phase-gated approvals and audit-ready exports.