E3 and E9, protocol deviations should be addressed both in the SAP and in the Clinical Study Report (CSR). The SAP is where the plan for classification and handling must be defined in advance.

Key SAP Sections for Addressing Deviations

Protocol deviation handling should appear in multiple sections of the SAP. Below are the relevant areas and what to include:

1. Analysis Populations

• Define which deviations will exclude subjects from Per Protocol (PP) analysis
• List criteria for inclusion in the Intent-to-Treat (ITT) and Safety populations

For example, subjects with major deviations may be excluded from the PP population but retained in the ITT population for sensitivity analysis.

2. Protocol Deviation Definitions and Criteria

• Provide operational definitions of major vs minor deviations
• Include coding categories or deviation taxonomy if available

These definitions should align with internal SOPs or deviation tracking systems used by clinical operations.

3. Sensitivity Analyses

• Describe planned analyses with and without subjects with major deviations
• Justify the exclusion rules for primary, secondary, and exploratory endpoints

Sensitivity analysis strengthens the reliability of findings and is critical for trials with a high rate of deviations.

4. Handling Missing Data Due to Deviations

• Address missing data arising from early discontinuation or visit skips due to protocol violations
• Describe imputation methods or analysis models to adjust for this

Methods such as Last Observation Carried Forward (LOCF), multiple imputation, or mixed models may be defined here.

Step-by-Step Process to Document Deviation Handling in SAP

Step 1: Review the Protocol and Define Deviation Categories

• Identify critical protocol elements (e.g., inclusion/exclusion, endpoint timing)
• Classify which deviations will affect efficacy or safety analysis

Step 2: Align with Clinical Operations on Deviation Tracking

• Collaborate with clinical data managers to review deviation logs
• Ensure the deviation classification aligns with clinical SOPs

Step 3: Define Impact Rules in the SAP

• Clearly state how deviations will affect analysis sets
• Provide rationale for any exclusions from PP or primary efficacy analyses

Step 4: Include Sensitivity Analysis Plans

• Describe scenarios for re-running key analyses with modified subject sets
• Compare ITT vs PP populations and adjust confidence intervals accordingly

Step 5: Document All Decisions in a Version-Controlled SAP

• Include all updates related to deviation management in the SAP revision history
• Obtain cross-functional review and sign-off

Maintaining clear documentation aligns with best practices outlined at Pharma SOP documentation.

Statistical Techniques to Address Deviations

• Covariate Adjustment: Include deviation presence as a covariate in models
• Modified ITT Analyses: Exclude only subjects with protocol-critical deviations
• Per Protocol Analyses: Exclude major deviations entirely from efficacy population
• Multiple Imputation: Address missing data caused by protocol violations
• Worst-Case Scenario Testing: Test impact of deviations on key assumptions

These should be predefined in the SAP to avoid post hoc analysis bias.

Best Practices for Protocol Deviation Handling in SAPs

1. Classify deviations early and consistently
2. Ensure clear linkage between protocol, deviation logs, and SAP
3. Use validated deviation data sources
4. Document all impact decisions and sensitivity logic
5. Train statistical and clinical teams on deviation definitions

Proper training ensures a shared understanding of deviation management across teams and supports compliance with stability testing records.

Common Mistakes to Avoid

• ❌ Excluding subjects without clear justification in the SAP
• ❌ Inconsistent classification of deviation types across documents
• ❌ Failing to include sensitivity analyses for major deviations
• ❌ Handling deviations post hoc, without SAP documentation
• ❌ Inadequate collaboration with data management and clinical teams

Regulatory Considerations

According to ICH E3 and CDSCO guidelines:

• Deviations must be described in the CSR with reference to the SAP
• All statistical exclusions must be predefined and justified in the SAP
• Regulatory reviewers expect traceability between deviation records and statistical methods

Conclusion: Plan, Document, and Justify

Handling protocol deviations in the SAP is not just a statistical detail—it is a regulatory obligation and a scientific necessity. Proactively defining how deviations will be categorized, analyzed, and reported ensures transparency and protects trial validity. With a properly structured SAP and informed authoring team, sponsors can demonstrate GCP adherence and strengthen the credibility of trial outcomes.

Explore Further:

• GMP audit process
• Process validation