How to Document Missing Data Handling in Clinical Trials: Best Practices

Missing data can jeopardize clinical trial outcomes, and how you handle and document it can make or break regulatory approvals. Agencies like the USFDA and EMA expect comprehensive documentation of all aspects related to missing data—covering classification, reasons, analysis, and assumptions.

This tutorial provides a step-by-step guide to documenting missing data handling in clinical trials, aligning with global regulatory guidance, such as ICH E9(R1). By following these best practices, sponsors and CROs can ensure transparency, consistency, and inspection-readiness throughout the clinical development process.

Why Documentation Matters in Missing Data Handling

Incomplete or vague documentation of missing data raises serious concerns about trial integrity. Accurate records serve multiple purposes:

• Support regulatory submission and audit readiness
• Enable reproducibility and peer review
• Facilitate proper statistical interpretation
• Prevent bias in efficacy and safety conclusions

Documentation should reflect planning (protocol/SAP), execution (eCRFs), and analysis (CSR) phases, with consistency across documents maintained through GMP-aligned systems.

1. Plan Ahead in the Protocol and SAP

The first step in missing data documentation is proactive planning. Regulatory bodies expect detailed strategies in your protocol and Statistical Analysis Plan (SAP):

• Protocol: Describe anticipated types of missing data, prevention strategies, and estimand strategies (e.g., treatment policy, hypothetical)
• SAP: Define the classification (MCAR, MAR, MNAR), statistical methods (e.g., MMRM, MI), and sensitivity analysis plans
• Document the rationale for method selection and assumptions

This forward planning ensures that missing data handling is pre-specified and avoids concerns of data-driven post hoc methods.

2. Use Standardized eCRF and Audit Trails

Proper data collection and auditability are essential. Use standardized electronic Case Report Forms (eCRFs) to track:

• Which data points are missing and at which visits
• Dropout dates and reasons
• Protocol deviation types linked to missing assessments
• Investigator notes explaining missing entries

Ensure all changes are captured in an audit trail and regularly reviewed. This facilitates inspection-readiness during regulatory audits.

3. Maintain a Comprehensive Missing Data Log

A centralized missing data log helps track trends and ensure consistent classification. Include fields such as:

• Subject ID and Visit Number
• Missing variable or test
• Reason for missing data (e.g., patient refusal, technical error)
• Associated protocol deviation (if any)
• Assumed mechanism: MCAR, MAR, or MNAR

Logs should be version-controlled and reviewed during trial monitoring visits and data management meetings.

4. Clarify Assumptions and Justifications in SAP

The Statistical Analysis Plan must provide a rationale for each method chosen to handle missing data, including:

• Justification for assuming data is MAR (e.g., patterns observed in dropout)
• Exploration of MNAR through tipping point analysis or pattern mixture models
• Handling strategy per estimand (as per ICH E9 R1)

Failure to document these assumptions may lead to regulatory queries or delays in approval.

5. Include Sensitivity Analyses Documentation

Documenting your sensitivity analyses is as important as performing them. Ensure that:

• Each analysis is pre-specified in the SAP
• Assumptions and parameters used are clearly described
• Results and impact on conclusions are transparently presented
• All figures, outputs, and tables are archived with versioning

This provides evidence that your primary conclusions are robust across different missing data scenarios.

6. Consistency Across Protocol, SAP, and CSR

Regulatory reviewers expect alignment across all trial documents. Ensure that:

• Missing data reasons listed in the CSR match what was anticipated in the protocol
• Analysis methods in the CSR follow the SAP
• Any deviations from the original plan are justified and explained

Discrepancies can lead to critical findings during regulatory inspections.

7. Common Mistakes to Avoid

• Relying solely on LOCF without justification
• Not recording reasons for missing data in eCRFs
• Failure to run or report sensitivity analyses
• Inconsistent reporting across protocol, SAP, and CSR
• Retrospective classification of data as MCAR or MAR

These mistakes are frequently flagged by agencies and undermine trust in trial results.

8. SOPs for Missing Data Documentation

Establish Standard Operating Procedures (SOPs) for documenting and managing missing data. These should cover:

• eCRF design and data entry conventions
• Missing data log maintenance
• SAP requirements for assumptions and analysis
• Quality control checks before CSR submission

Use templates aligned with industry SOP guidelines to standardize the process across trials.

Conclusion

Comprehensive and consistent documentation of missing data handling is essential for regulatory success and scientific credibility. From the protocol to the CSR, every step should reflect clear, planned, and justified decisions. By aligning your practices with FDA, EMA, and ICH guidance, and by implementing strong internal SOPs and logs, you can confidently defend your trial outcomes against scrutiny and ensure a smooth path to approval.

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.