How to Apply the 5 Whys Technique in Clinical Deviation Investigations

Why Use the 5 Whys in Clinical Trial RCA?

The 5 Whys technique is a simple but powerful Root Cause Analysis (RCA) tool that helps uncover the true origin of a problem—not just its symptoms. In clinical research, where protocol deviations can disrupt subject safety and data integrity, identifying the root cause is essential for implementing effective Corrective and Preventive Actions (CAPA).

Regulators like the FDA, EMA, and MHRA expect that every significant deviation be investigated using a structured approach. The 5 Whys method satisfies this expectation by providing a traceable rationale behind deviation classification, CAPA actions, and effectiveness monitoring.

This article shows how to apply the 5 Whys method specifically within the GCP-compliant deviation handling process and how it aligns with ICH E6(R2) requirements.

Overview of the 5 Whys Method

The 5 Whys technique involves asking “Why?” multiple times (usually five) to peel away layers of symptoms and expose the root cause of a problem. It is best used when:

• ✅ The issue appears to have one dominant root cause
• ✅ The problem is straightforward, like a missed procedure or documentation lapse
• ✅ Timely RCA is needed to comply with deviation closure timelines

Benefits of using 5 Whys in GCP trials:

• ✅ Easy to apply by site staff, CRAs, or sponsor personnel
• ✅ Suitable for most protocol deviations, especially operational ones
• ✅ Audit-friendly—provides a logical narrative trail
• ✅ Requires no specialized software or tools

Step-by-Step Example: Applying 5 Whys to a Realistic Deviation

Deviation: Subject 207 received IP 1 day early—outside of the protocol-defined visit window.

5 Whys Analysis:

1. Why did the subject receive IP early? → Coordinator scheduled visit incorrectly.
2. Why was the visit scheduled early? → Calendar invite didn’t match protocol-specified visit window.
3. Why was the calendar incorrect? → The coordinator created a manual visit calendar based on a misread version of the protocol.
4. Why was the wrong protocol version used? → Site downloaded version 1.2 instead of version 1.3.
5. Why did this happen? → No SOP for version control of protocol documents at the site.

Root Cause: Lack of a site-level SOP for protocol version control and calendar creation.

CAPA: Implement version-controlled protocol binder SOP, train staff on protocol updates, and use sponsor-supplied visit calculator tools going forward.

Documentation Format for 5 Whys in Deviation Logs

Many sponsors and CROs now require the 5 Whys output to be embedded directly in deviation records or RCA forms. A simple format may include:

Root Cause: Missing SOP for protocol document control.

CAPA: Create and implement SOP. Retrain site staff.

When to Use (and Not Use) the 5 Whys Method

Recommended for:

• ✅ Missed visits or assessments
• ✅ Incorrect dosing or procedure timing
• ✅ Delayed data entry or safety reporting
• ✅ Documentation lapses

Not recommended for:

• ❌ Multi-site systemic issues
• ❌ Cross-functional operational failures
• ❌ Deviations requiring layered root cause categories

In such cases, Fishbone diagrams or FMEA may be more appropriate.

Auditor Expectations for 5 Whys in RCA

Regulators and auditors are increasingly checking whether sponsors and sites used structured RCA methods. For 5 Whys in particular, they will expect:

• ✅ A logical flow between each “Why” and its answer
• ✅ No blame language (e.g., “staff carelessness”)
• ✅ A root cause that is actionable
• ✅ CAPA that addresses the final Why

Example audit finding: “The RCA was inadequate. The deviation form listed ‘staff forgot’ as the reason, with no structured analysis or preventive action.”

Integrating 5 Whys into SOPs and Training

To embed the 5 Whys in your organization’s quality culture:

• ✅ Add a 5 Whys template to deviation forms and CAPA logs
• ✅ Include the technique in GCP and deviation handling SOPs
• ✅ Train investigators and CRAs to use 5 Whys consistently
• ✅ Review 5 Whys narratives during QA audits for completeness

Tip: Assign a deviation review committee to validate root causes and prevent shallow or circular logic in RCA reports.

Conclusion: 5 Whys as a GCP-Compliant RCA Tool

The 5 Whys technique is a simple yet powerful approach to uncovering the true cause of protocol deviations in clinical trials. When applied correctly, it supports CAPA planning, meets auditor expectations, and contributes to continuous improvement in trial operations.

By integrating the 5 Whys into SOPs, templates, and training, clinical teams can elevate their deviation management processes from reactive fixes to proactive prevention—ensuring GCP compliance and protecting the integrity of clinical data.

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.