CAPA Root Cause Analysis Examples (ISO 13485): What Good Looks Like
ISO Cloud Consulting editorial team
If your root cause is wrong, everything that follows will fail.
This is the core reason most CAPA systems break down—teams fix symptoms instead of causes.
Why Root Cause Analysis Fails in ISO 13485
Most CAPAs fail at the root cause stage because:
Template for this step: the CAPA SOP, CAPA register and root cause toolkit are in the ISO 13485 CAPA & Nonconformance Kit ($79).
- Teams stop at the first obvious answer
- Blame is assigned instead of causes identified
- No structured method is used
Weak vs Strong Root Cause (Core Principle)
| Weak Root Cause | Strong Root Cause |
|---|---|
| Operator error | Training process does not ensure competency verification |
| Procedure not followed | Procedure unclear and not effectively implemented |
| Human mistake | Lack of error-proofing in process design |
Key rule: A strong root cause points to a system failure—not a person.
CAPA Root Cause Analysis Examples
Example 1: Training Issue
Problem: Operator performed incorrect inspection
Weak Root Cause: Operator not trained
Strong Root Cause: Training system does not include competency assessment or verification
Corrective Action: Implement competency-based training and periodic reassessment
Example 2: Document Control Failure
Problem: Obsolete procedure used in production
Weak Root Cause: Staff used wrong document
Strong Root Cause: Document control system does not ensure removal of obsolete versions at point of use
Corrective Action: Implement controlled access and automated version control
Example 3: CAPA Recurrence
Problem: Same issue repeated after closure
Weak Root Cause: CAPA not effective
Strong Root Cause: No defined effectiveness criteria or verification process
Corrective Action: Define measurable effectiveness checks and enforce closure criteria
Example 4: Supplier Issue
Problem: Nonconforming materials received
Weak Root Cause: Supplier error
Strong Root Cause: Supplier qualification and monitoring process does not define acceptance criteria or performance tracking
Corrective Action: Strengthen supplier evaluation and monitoring system
Example 5: Complaint Handling Failure
Problem: Complaint not escalated to CAPA
Weak Root Cause: Staff oversight
Strong Root Cause: Complaint handling procedure does not define clear escalation criteria to CAPA
Corrective Action: Define escalation rules and integrate complaint-to-CAPA workflow
How to Perform Root Cause Analysis (Step-by-Step)
1. Define the Problem Clearly
- Use objective evidence
- Avoid vague descriptions
2. Map the Process
- Understand where the failure occurred
- Identify process breakdowns
3. Use a Structured Method
- 5 Whys
- Fishbone (Ishikawa)
- Fault tree analysis
4. Validate the Root Cause
- Does it explain the problem fully?
- Would fixing it prevent recurrence?
5 Whys Example (Simple Illustration)
Problem: Incorrect product released
- Why? Inspection missed defect
- Why? Inspector overlooked criteria
- Why? Criteria unclear
- Why? Procedure poorly defined
- Why? No formal review of inspection procedures
Root Cause: Lack of structured procedure review process
How Root Cause Links to Risk Management
Strong root cause analysis feeds directly into risk management.
Template for this step: the risk management plan, hazard register and report templates are in the ISO 14971 Risk Management File Kit ($129).
- Identified causes may introduce new hazards
- CAPA outcomes should update risk files
- Recurring issues indicate uncontrolled risk
Risk management requires systematic identification, evaluation, and control of risks across the lifecycle.
Common Root Cause Analysis Mistakes
- Stopping too early (first-level cause)
- Blaming individuals instead of systems
- No structured method used
- No validation of root cause
How Auditors Assess Root Cause Analysis
Auditors will look for:
- Logical linkage between problem and cause
- Evidence supporting the root cause
- Corrective actions aligned to the cause
- Effectiveness of actions
Weak root cause analysis is one of the most common ISO 13485 audit findings.
How to Strengthen Your CAPA Root Cause Process
- Train teams on root cause methods
- Standardise templates and approach
- Require evidence-based justification
- Review root causes during management review
FAQ: CAPA Root Cause Analysis
What is a root cause in CAPA?
The underlying system failure that led to the nonconformity.
What is the best root cause analysis method?
5 Whys and Fishbone are most commonly used, depending on complexity.
Why do CAPAs fail?
Because root causes are incorrect or incomplete.
How do you verify a root cause?
By confirming that eliminating it prevents recurrence of the issue.
Final Takeaway
CAPA success depends on one thing: accuracy of root cause.
Fix the cause, and the problem disappears. Miss the cause, and it comes back.
