Root Cause Analysis (RCA)

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.

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

Related investigation terms

RCA connects tightly to other investigation and improvement concepts:

• CAPA — RCA feeds the action plan
• Deviation — deviations require RCA for closure
• OOS — phase 2 OOS investigation uses RCA methods
• Audit Trail — RCA evidence must be attributable and traceable
• Validation — RCA may reveal validation gaps needing rework