of the deviation and the availability of site or process data.

Using the 5 Whys for Simple Deviation Investigations

The 5 Whys technique is ideal for simple, single-cause deviations. It involves asking “Why?” iteratively (typically five times) to drill down to the core problem.

Example: A subject was dosed without completing a visit ECG.

1. Why was the ECG missed? → Staff forgot to perform it.
2. Why did staff forget? → The ECG checklist wasn’t followed.
3. Why wasn’t the checklist followed? → Staff was covering for a sick colleague and unfamiliar with the workflow.
4. Why was the substitute untrained? → No backup staff training program existed.
5. Why was there no training program? → SOPs didn’t mandate cross-training.

Root Cause: Lack of SOP for backup staff training.
CAPA: Revise SOP, implement training matrix, and add ECG check to the pre-dose checklist.

Fishbone Diagrams for Complex Root Cause Mapping

Also known as the Ishikawa Diagram, the fishbone tool is useful for visualizing multiple potential root causes across categories. This is especially helpful in complex deviations involving people, processes, technology, and environment.

Common categories include:

• People (training, staffing, roles)
• Process (SOPs, workflows, handoffs)
• Equipment (IT systems, monitoring devices)
• Environment (site workload, time pressure)
• Materials (forms, templates, protocol)
• Management (oversight, communication)

Tip: Use fishbone diagrams during cross-functional deviation review meetings to align sponsor, site, and CRA perspectives.

Cause-and-Effect Matrix for Prioritizing Root Causes

When multiple causes are identified, a Cause-and-Effect Matrix helps prioritize them based on severity, occurrence, and detectability. This is especially valuable in evaluating systemic issues or in large-scale deviations across sites.

Example Matrix Structure:

Cause	Severity	Frequency	Detectability	Risk Priority Score
Inadequate SOPs	High (3)	Frequent (3)	Low (3)	27
Staff turnover	Medium (2)	Frequent (3)	Medium (2)	12

Higher scores indicate higher priority for CAPA planning. This matrix helps sponsors focus their quality improvement resources effectively.

Documentation Expectations for RCA Tools

Regulators expect RCA results to be documented clearly and stored as part of the CAPA record or Deviation Investigation Report. A complete RCA package should include:

• ✅ Description of the deviation
• ✅ Tool(s) used for RCA (e.g., 5 Whys, Fishbone)
• ✅ Identified root cause(s)
• ✅ Supporting evidence (meeting minutes, audit trail)
• ✅ CAPA developed based on the RCA
• ✅ Effectiveness check plan

Note: Avoid listing “human error” as the sole root cause. Regulatory authorities expect deeper process-based or systemic causes, such as inadequate training or poor workflow design.

Regulatory Insights on RCA Expectations

Authorities such as the FDA, EMA, and MHRA have cited sponsors for:

• ❌ RCA tools not used or documented
• ❌ CAPAs developed without identifying true root causes
• ❌ Repetitive deviations with no formal RCA conducted

During inspections, auditors will often request RCA documentation for major deviations, asking how the root cause was determined and how CAPA was linked to it. Using structured tools increases transparency and regulatory confidence.

Conclusion: Embedding RCA Tools into Clinical Quality Systems

Effective use of RCA tools goes beyond fixing a deviation—it helps sponsors and CROs prevent recurrence, improve trial quality, and pass inspections. Whether using the simple 5 Whys or the more advanced Cause-and-Effect Matrix, RCA should be built into every CAPA process, QA review, and deviation SOP.

Invest in RCA training for site staff, CRAs, and QA professionals, and ensure that your quality management system includes templates, timelines, and escalation pathways for RCA execution. A structured, documented approach to deviation investigations will elevate both compliance and credibility in every clinical trial.