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.