Step-by-Step Guide to Conducting Structured Root Cause Analysis for Clinical Trial Deviations

Why Structured RCA Matters in Clinical Research

When deviations from protocol occur in a clinical trial, documenting the event isn’t enough. Regulatory bodies such as the FDA, EMA, and MHRA expect sponsors and investigators to conduct a structured Root Cause Analysis (RCA) that identifies the underlying causes—not just the symptoms—of non-compliance. This ensures effective CAPA (Corrective and Preventive Action) and prevents recurrence.

ICH-GCP E6(R2) reinforces the need for robust quality systems and risk-based thinking. A structured RCA supports both by ensuring that deviations are handled systematically and backed by documented, logical analysis. Poorly executed RCA—or none at all—is a common audit finding.

This guide walks you through a GCP-compliant, step-by-step RCA process applicable for sponsors, CROs, monitors, and sites.

Step 1: Define the Problem Clearly

Start with a precise, objective, and factual problem statement. Avoid assigning blame or assumptions.

Example: “Subject 103 missed pre-dose lab assessments on Visit 4 and received the investigational product without safety clearance.”

Include the deviation ID, study number, subject ID, date, protocol section violated, and any immediate impact on safety or data integrity.

Step 2: Assemble a Cross-Functional RCA Team

Include members from the following areas to ensure diverse perspectives:

• ✅ Site investigator or coordinator
• ✅ CRA or regional monitor
• ✅ Sponsor study manager or clinical lead
• ✅ QA representative
• ✅ Medical monitor (if applicable)

Assign an RCA facilitator who ensures impartial analysis and proper documentation.

Step 3: Gather Relevant Data and Timeline

Gather all documents and data sources associated with the deviation:

• ✅ Source documents and eCRFs
• ✅ Deviation form and initial classification
• ✅ Monitoring reports and correspondence
• ✅ SOPs and site training logs
• ✅ Audit trails (EDC, eTMF)

Create a timeline leading up to the deviation. This helps visualize any process or communication gaps that may have contributed.

Step 4: Identify Potential Causes Using an RCA Tool

Apply a structured RCA tool, such as:

• 5 Whys Analysis – Ideal for single-issue deviations
• Fishbone (Ishikawa) Diagram – Best for complex, multi-cause issues
• Process Mapping – Effective for workflow-related deviations

Example using 5 Whys:

1. Why was the pre-dose lab not performed? → Coordinator missed the lab schedule.
2. Why was the schedule missed? → Visit checklist was not used.
3. Why wasn’t it used? → Checklist not available in subject file.
4. Why was it missing? → Coordinator believed it was optional.
5. Why was it believed optional? → Training did not cover checklist use.

Root Cause: Training deficiency and unclear SOP on checklist use.

Step 5: Classify the Root Cause

Use a root cause category matrix to assign the issue to a broader failure domain:

Be cautious: labeling everything as “human error” can be a red flag in audits unless supported with evidence that no systemic factors were involved.

Step 6: Draft the RCA Report

The RCA report should include:

• ✅ Deviation summary and impact
• ✅ Participants involved in RCA
• ✅ Tools used (e.g., Fishbone, 5 Whys)
• ✅ Evidence collected and reviewed
• ✅ Root cause(s) identified
• ✅ Categorization of failure
• ✅ Recommendations for CAPA

Reports should be reviewed by the QA team and submitted into the trial’s quality documentation system (e.g., eTMF).

Step 7: Link RCA to Corrective and Preventive Actions

A structured RCA should directly feed into a tailored CAPA. For each root cause, ask:

• ✅ What action will correct the current issue?
• ✅ What change will prevent this from recurring?
• ✅ Who is responsible for implementation?
• ✅ What is the timeline?
• ✅ How will effectiveness be verified?

Example CAPA: Update SOP to include mandatory checklist review before each visit, retrain all site staff, and include checklist presence as a monitoring point in the CRA visit report template.

Step 8: Perform Effectiveness Check

RCA isn’t complete until the effectiveness of the CAPA is verified. This can be done by:

• ✅ Follow-up monitoring visits
• ✅ QA audits
• ✅ Spot checks during routine quality control reviews
• ✅ Deviation trend analysis

Tip: Include a timeline (e.g., 30 or 60 days post-CAPA) to trigger the effectiveness check, and document results accordingly.

Conclusion: Embed Structured RCA into Your Clinical Quality System

Structured RCA is not just a quality exercise—it is a regulatory expectation. Auditors frequently review RCA documentation for major protocol deviations and expect to see logical, data-supported reasoning behind all conclusions. By embedding RCA workflows into SOPs, training programs, and deviation logs, sponsors and CROs can drive true quality improvement while minimizing inspection risk.

Remember: a deviation without RCA is just a mistake waiting to happen again. A well-executed RCA transforms that mistake into a lesson—and a pathway to better compliance.

Essential Root Cause Analysis Tools for Clinical Trial Deviation Investigations

Why Root Cause Analysis Is Critical in Clinical Research

When a protocol deviation or non-compliance occurs in a clinical trial, documenting the event is only the first step. Regulatory authorities and Good Clinical Practice (GCP) guidelines require a thorough investigation into the root cause to prevent recurrence and to ensure data integrity and subject protection.

Root Cause Analysis (RCA) is the structured process of identifying why a deviation occurred, rather than just treating the symptoms. RCA plays a foundational role in the development of Corrective and Preventive Actions (CAPA), audit readiness, and continuous quality improvement.

Agencies such as the FDA and EMA expect sponsors and CROs to use RCA tools that are standardized, reproducible, and fit for purpose. Improper or shallow root cause assessments have led to warning letters, delayed submissions, and even study holds.

Key RCA Tools Used in Clinical Research

Various tools and frameworks are available for conducting structured RCA in GCP environments. Below are the most widely used:

• 5 Whys Analysis
• Fishbone (Ishikawa) Diagram
• Fault Tree Analysis (FTA)
• Failure Mode and Effects Analysis (FMEA)
• Barrier Analysis
• Cause and Effect Matrix

Each tool has its advantages depending on the complexity 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:

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.