CAPA & Deviations
Explore this topic in more depth to build a complete picture of your quality and compliance operations.
Explore
Glossary Term
Root Cause Analysis (RCA)
A systematic method for identifying the underlying cause of a quality issue — not the symptom — so corrective action can actually prevent recurrence.
Inspectors distinguish between fixing a symptom and addressing a cause. A weak root cause like 'human error' almost always signals insufficient investigation and weak CAPA evidence.
On this page
What Root Cause Analysis means
Root Cause Analysis (RCA) is a structured investigation method used to identify the fundamental underlying cause of a quality event, rather than its visible symptom or proximate trigger.
The distinction matters: a symptom is what you see (a failed batch), a proximate cause is what directly preceded it (wrong temperature), and the root cause is what allowed it to happen (a missing alarm in the control system design). Corrective actions targeting symptoms fail. Actions addressing root causes prevent recurrence.
Why weak RCA is a top inspection finding
"Human error" written as a root cause is one of FDA's most-cited inspection findings. It indicates the investigator stopped at the last person who touched the process rather than asking why a human-dependent step existed at all, why training did not prevent the error, or why a control check did not detect it.
Strong RCA evidence shows the investigator asked "why" multiple times, considered system-level causes, and documented the logic chain. This becomes the foundation for credible CAPAs.
The 'human error' trap
If your root cause is 'operator made a mistake', you have almost certainly not completed your investigation. The real question is: why did the system allow a single operator mistake to cause a quality event?
Where RCA is expected
RCA is implicit in most GxP regulations and explicit in modern quality frameworks:
- FDA 21 CFR 211.192 — Requires thorough investigation of discrepancies
- FDA 21 CFR 820.100 — CAPA procedures must identify causes
- ICH Q10 §3.2.2 — CAPA as an enabler for continuous improvement requires understanding causes
- ICH Q9(R1) — Quality risk management requires causal assessment
- ISO 13485 §8.5.2 — Determining causes of nonconformities
- FDA Guidance on Quality Metrics — Root cause trending is a CGMP indicator
Common RCA tools
Several analytical tools support root cause investigation. Use the one fitted to the event's complexity:
- 5 Whys — ask 'why' iteratively. Best for simple, single-thread causes
- Fishbone (Ishikawa) Diagram — categorize causes across people, process, equipment, materials, environment, method. Best for multi-factor events
- Fault Tree Analysis — deductive top-down analysis. Best for safety-critical failures
- FMEA — forward-looking; identifies potential failure modes. Best for preventive analysis
- Pareto Analysis — prioritize which causes drive most of the impact
- Kepner-Tregoe — structured problem analysis for complex multi-variable events
What good RCA controls look like
Quality systems with strong RCA practice share:
- Controlled root cause taxonomy — a finite list of categories with definitions
- Minimum 5-Whys depth required before root cause selection
- Investigator training and certification
- QA review gate before root cause is locked
- Trending reports on root cause categories across deviations and CAPAs
- Feedback loop — repeat root causes trigger systemic review
- Evidence attachments — photos, data, interview notes stored with the record
How Complere structures RCA
Complere provides a controlled root cause framework inside CAPA and Deviation records, preventing shallow single-word causes and enforcing evidence-backed conclusions.
- Configurable root cause taxonomy scoped to your QMS
- Required 5-Whys chain entry before root cause save
- Fishbone template selector by event type
- Evidence attachment with audit trail per file
- Pre-built trending dashboards by root cause category, site, product line
- Automatic flagging of recurring root causes for leadership review
- Linkage to FMEA in the Risk Assessments module for preventive pivots
Frequently asked questions
Common questions about Root Cause Analysis (RCA) sourced from regulatory references and inspection patterns.
What is root cause analysis in a regulated quality system?
Root cause analysis is the structured investigation that identifies the underlying reason a deviation, complaint, or audit finding occurred — not just the surface symptom. It's the foundation of every CAPA, deviation closure, and recurring-issue prevention program.
Which RCA methods do FDA and EMA inspectors recognize?
Inspectors expect a method appropriate to the issue's complexity: 5 Whys for simple deviations, Fishbone (Ishikawa) for multi-cause issues, FMEA for risk-prioritized failure modes, and fault tree analysis for safety-critical events. Method choice should be documented in the SOP.
How deep should the investigation go before declaring root cause?
Until removing the identified cause would prevent recurrence — not just until a contributing factor is found. Premature closure on operator error or 'human factors' is a common 483 finding; inspectors expect investigation of why the system allowed the error.
What is the most common reason root cause analyses fail inspection?
Two patterns drive most findings: closure at the first plausible cause without testing alternatives, and corrective actions disproportionate to the cause (e.g., retraining when the SOP itself was unclear). Both signal weak investigation discipline to inspectors.
How does Complere structure root cause investigations?
Complere captures the investigation method, evidence reviewed, ruled-out hypotheses, and confirmed root cause as linked records — so inspectors see the analytical path, not just the conclusion, and recurring causes surface across deviations and CAPAs over time.
Continue Exploring
Explore related topics, modules, and compliance resources for a deeper understanding of your quality system.
See structured root cause analysis in Complere
Explore how Complere's controlled RCA taxonomy and guided investigation templates drive deeper root causes and stronger CAPA evidence.