How to Handle Dropouts and Protocol Deviations in Clinical Trial Analysis

Dropouts and protocol deviations are almost inevitable in clinical trials. Whether due to patient withdrawal, non-adherence, or procedural inconsistencies, these events can distort the trial results if not properly handled. Regulators like the USFDA and EMA expect clear definitions and pre-specified methods for managing these issues in both the protocol and Statistical Analysis Plan (SAP).

This tutorial explains how to classify, analyze, and report dropouts and protocol deviations in a way that preserves data integrity, ensures regulatory compliance, and supports valid conclusions from your clinical trial.

What Are Dropouts and Protocol Deviations?

Dropouts:

Subjects who discontinue participation before completing the study, often due to adverse events, lack of efficacy, consent withdrawal, or personal reasons.

Protocol Deviations:

Any departure from the approved trial protocol, whether intentional or unintentional, including incorrect dosing, visit window violations, or missing assessments.

Proper classification and documentation of both are required in GMP-compliant studies.

Types of Protocol Deviations

• Major Deviations: Affect the primary endpoint or trial integrity (e.g., incorrect randomization)
• Minor Deviations: Do not impact key trial outcomes (e.g., visit outside window)
• Eligibility Deviations: Inclusion of ineligible subjects
• Treatment Deviations: Non-adherence to investigational product protocol

Major deviations usually exclude subjects from the Per Protocol (PP) analysis set but may remain in the Intent-to-Treat (ITT) set.

Statistical Approaches for Dropouts

1. Intent-to-Treat (ITT) Analysis:

Includes all randomized subjects, regardless of adherence or dropout. This approach preserves randomization benefits and is the gold standard for efficacy trials.

However, missing data due to dropouts must be addressed using methods such as:

• Mixed Models for Repeated Measures (MMRM)
• Multiple Imputation (MI)
• Pattern-Mixture Models
• Last Observation Carried Forward (LOCF) – discouraged for primary analysis

2. Per Protocol (PP) Analysis:

Includes only subjects who adhered strictly to the protocol. This provides a clearer picture of treatment efficacy under ideal conditions.

It is often used as a supportive analysis to ITT and must be predefined in the SAP and CSR.

Handling Protocol Deviations in Analysis

Deviations should be categorized and analyzed for their impact. Best practices include:

• Pre-specify major vs minor deviations in the SAP
• Perform sensitivity analysis excluding subjects with major deviations
• Justify inclusion/exclusion of deviators in each analysis set
• Report all deviations in the CSR by type and frequency

Major deviations that affect endpoints (e.g., missing primary assessments) should typically exclude those subjects from PP analysis.

Estimand Framework and Intercurrent Events

The ICH E9(R1) guideline encourages defining “intercurrent events,” which include dropouts and deviations. These are addressed through different strategies like:

• Treatment Policy: Analyze all randomized subjects regardless of intercurrent events
• Hypothetical: Model the outcome as if the event had not occurred
• Composite: Combine event with outcome into a single endpoint
• Principal Stratum: Restrict analysis to subgroup unaffected by the event

Choosing the right estimand and handling approach is a regulatory expectation and should align with trial registration strategies.

Regulatory Expectations for Dropouts and Deviations

USFDA: Emphasizes transparency in dropout handling and discourages LOCF as a primary method. Requires dropout reasons to be detailed in submission.

EMA: Requires analysis of protocol adherence and impact on efficacy interpretation. Supports multiple sensitivity analyses.

CDSCO: Encourages sponsor accountability in tracking and preventing protocol violations. Dropout management is critical during audits.

Best Practices for Managing Dropouts and Deviations

• Include dropout prevention strategies in the protocol
• Use eCRFs to track deviation type, reason, and impact
• Train sites on protocol adherence and data quality
• Implement real-time deviation monitoring dashboards
• Review deviation reports during interim data reviews

Example Scenario

In a Phase III diabetes trial, 10% of patients dropped out before the Week 24 endpoint. ITT analysis used MMRM to handle missing data, assuming MAR. A per-protocol analysis excluded 6% with major protocol deviations. Sensitivity analyses using pattern-mixture models supported the robustness of findings, as treatment effect remained statistically significant under all assumptions. The FDA approved the submission based on the transparent and well-planned analysis of dropouts and deviations.

Conclusion

Handling dropouts and protocol deviations effectively is essential for the credibility and regulatory acceptance of your clinical trial. Start with proper planning and classification, follow with appropriate statistical handling, and ensure transparent documentation. Using robust ITT and PP analyses, backed by sensitivity analyses and regulatory guidance, helps ensure that your results are reliable, unbiased, and ready for global submission.

How to Meet Regulatory Expectations for Missing Data in Clinical Trials

Missing data in clinical trials can threaten both the credibility and regulatory acceptability of your study results. Regulatory authorities such as the USFDA, EMA, and CDSCO expect sponsors to proactively plan for, minimize, and transparently report all aspects of missing data. Failure to do so can lead to delayed approvals, requests for additional trials, or outright rejection.

This tutorial provides a comprehensive overview of regulatory expectations regarding missing data—covering how to document, analyze, and justify your approach. It also discusses strategies to align with key guidelines such as ICH E9(R1) and the FDA’s “Guidance for Industry on Missing Data in Clinical Trials.”

Why Regulatory Authorities Prioritize Missing Data

Regulators require clarity on how missing data may have influenced study conclusions. They expect the sponsor to:

• Plan for missing data prevention and mitigation in the protocol
• Analyze the potential impact of data loss on trial outcomes
• Conduct appropriate sensitivity analyses
• Document everything in the SAP and Clinical Study Report (CSR)

In short, missing data isn’t just a statistical issue—it’s a matter of trial integrity, reliability, and ethical responsibility.

1. Documenting Missing Data in Protocol and SAP

Both the clinical protocol and the Statistical Analysis Plan (SAP) should address missing data explicitly. According to ICH E9(R1), this includes:

• Identifying the estimand and how intercurrent events like dropout affect it
• Describing strategies for preventing missing data (e.g., flexible visit windows, retention efforts)
• Pre-specifying statistical handling approaches (e.g., MMRM, Multiple Imputation, LOCF)
• Defining sensitivity analysis plans to assess robustness under MNAR assumptions

Failure to specify these elements may raise red flags during regulatory review and compromise GMP compliance.

2. Analysis Requirements in the CSR

Clinical Study Reports (CSRs) submitted to regulators must clearly report:

• Extent and reasons for missing data
• Number of missing observations by treatment arm and timepoint
• Statistical models used for handling missingness
• Sensitivity analysis results and interpretation

Transparency is critical. Sponsors should avoid selective reporting or retrospective justifications for missing data handling.

3. Regulatory Preference for Certain Statistical Methods

Acceptable Approaches:

• MMRM (Mixed Models for Repeated Measures): Appropriate under MAR assumptions
• Multiple Imputation (MI): Widely supported if implemented correctly
• Pattern-Mixture Models: Useful for MNAR sensitivity analysis

Discouraged Methods:

• LOCF (Last Observation Carried Forward): Discouraged as a primary method due to unrealistic assumptions
• Complete Case Analysis: Acceptable only under MCAR, which is rare

To demonstrate compliance with regulatory standards, sponsors should include sensitivity analysis methods aligned with ICH stability principles and current statistical practices.

4. Reporting Missing Data by Reason and Mechanism

Regulators expect missing data to be classified by reason (e.g., AE, withdrawal of consent, lost to follow-up) and potentially by missingness mechanism:

• MCAR: Missing Completely at Random
• MAR: Missing at Random (most common)
• MNAR: Missing Not at Random (most difficult to handle)

Although the missing data mechanism is untestable, the classification provides a framework for sensitivity analysis and modeling choices.

5. Regulatory Guidelines on Missing Data

Key Guidance Documents:

• FDA Guidance on Missing Data (2010)
• EMA Draft Guideline on Handling Missing Data
• ICH E9(R1) Addendum on Estimands

These guidelines stress the importance of planning, pre-specification, and transparency in handling missing data. Non-compliance may lead to major findings during regulatory audits.

6. Sensitivity Analysis Expectations

Sponsors must demonstrate that their results are robust under alternative missing data assumptions. Typical methods include:

• Delta-adjusted multiple imputation
• Tipping point analysis
• Pattern mixture models

These analyses help reviewers assess whether conclusions hold if missing data mechanisms differ from assumptions used in primary analysis.

7. Real-World Example: EMA Rejection Due to Missing Data

In a 2019 case, EMA declined approval of a CNS drug because the trial failed to appropriately handle high dropout rates. The sponsor used LOCF as the primary imputation strategy without sensitivity analyses, leading to doubts about the treatment’s efficacy. This underscores the need for regulatory-aligned strategies.

8. Internal SOPs and Training

To ensure compliance, sponsors should develop internal SOPs that mandate:

• Inclusion of missing data strategies in protocol/SAP
• Documentation of all imputation methods
• Clear communication with CROs and vendors
• Regular training on evolving regulatory guidance

Integrating these steps into validation protocols also ensures inspection readiness and internal consistency.

Conclusion

Regulatory expectations for missing data are stringent and evolving. Sponsors must anticipate and prevent data loss wherever possible, document their assumptions, and transparently analyze and report missing data in compliance with global standards. By adhering to ICH, FDA, EMA, and CDSCO guidance, and by embedding these practices into trial design and reporting systems, sponsors can significantly improve their chances of regulatory success.