1 Purpose

The Statistical Analysis Plan (SAP) provides detailed, pre-specified statistical methods for the analysis and reporting of a clinical trial.

The SAP should:

2 SAP Development Process

2.1 Review Study Documents

Before developing the SAP, review:

  • Final or near-final protocol.
  • Protocol amendments.
  • Case Report Forms (CRFs/eCRFs).
  • Data Management Plan.
  • Randomization specifications.
  • Endpoint definitions.
  • Estimand framework.
  • Clinical and regulatory requirements.
  • Relevant statistical guidance.
  • Planned SDTM and ADaM specifications, when available.

The SAP must remain consistent with the protocol. Any deviations from protocol-specified statistical analyses should be clearly documented and justified.

2.2 Timing

The SAP should normally be finalized and approved:

Before database lock and before treatment unblinding.

For studies with interim analyses, relevant statistical methods and decision rules should be finalized before the corresponding interim analysis.

3 Study Background

Briefly describe:

Keep this section concise because detailed clinical background belongs in the protocol.

4 Study Objectives and Endpoints

Specify:

4.1 Primary Objective

The main confirmatory objective of the study.

4.2 Secondary Objectives

Important additional efficacy or safety objectives.

4.3 Exploratory Objectives

Hypothesis-generating objectives.

For each objective, clearly identify the corresponding:

  • Primary endpoint.
  • Secondary endpoints.
  • Exploratory endpoints.
  • Safety endpoints.

For each important endpoint define:

  • Variable.
  • Measurement method.
  • Analysis time point.
  • Baseline definition.
  • Change-from-baseline definition, if applicable.
  • Responder definition, if applicable.
  • Event definition and censoring rules for time-to-event endpoints.

5 Estimand

For each primary endpoint, and important secondary endpoints when appropriate, define the estimand.

Specify:

  1. Population
  2. Treatment condition
  3. Variable / endpoint
  4. Intercurrent event strategy
  5. Population-level summary measure

Common intercurrent events include:

Possible strategies include:

The statistical estimator should be aligned with the estimand.

6 Study Design

Summarize the design, including:

If applicable, describe:

7 Statistical Hypotheses

For confirmatory endpoints, specify:

Example:

\[ H_0: \mu_T-\mu_C=0 \]

versus

\[ H_1: \mu_T-\mu_C\neq0 \]

For non-inferiority or equivalence trials, specify the pre-defined margin.

8 Sample Size

Describe:

If applicable, describe:

9 Analysis Populations

Clearly define each analysis population.

9.1 Intent-to-Treat / Full Analysis Set

Usually includes all randomized subjects and analyzes subjects according to randomized treatment.

9.2 Modified Intent-to-Treat

Specify any additional criteria, for example:

  • Received at least one dose.
  • Has at least one post-baseline assessment.

Any modification of ITT should be scientifically justified.

9.3 Per-Protocol Population

Usually excludes subjects with important protocol deviations that could materially affect efficacy assessment.

9.4 Safety Population

Usually includes subjects who received at least one dose of study treatment.

Safety analyses are generally performed according to actual treatment received, when appropriate.

Additional populations may include:

  • Pharmacokinetic population.
  • Pharmacodynamic population.
  • Immunogenicity population.
  • Biomarker population.

10 Protocol Deviations

Define how protocol deviations will be classified.

Common major deviations include:

Specify whether deviations affect inclusion in:

Final classification should normally be completed before database lock and unblinding.

11 General Statistical Considerations

Specify general conventions such as:

Continuous variables will typically be summarized using:

Categorical variables will typically be summarized using:

For inferential analyses, report when appropriate:

Clinical interpretation should not rely only on statistical significance.

12 Baseline Definition

Define baseline for each relevant endpoint.

Typically:

The last non-missing assessment obtained before the first administration of randomized study treatment.

Specify special rules when multiple pre-treatment assessments exist.

13 Visit Windows

Define rules for assigning observations to analysis visits.

Specify:

A common rule is to select the assessment closest to the target visit.

Tie-breaking rules should also be pre-specified.

14 Missing Data

Describe the expected missing-data mechanism and primary handling strategy.

Possible approaches include:

Avoid relying routinely on simple methods such as Last Observation Carried Forward (LOCF) unless scientifically justified.

Distinguish:

15 Sensitivity Analyses for Missing Data

Primary analyses should generally be supported by sensitivity analyses assessing robustness to missing-data assumptions.

Possible methods include:

The choice should reflect the estimand and clinical context.

16 Multiplicity

Identify all confirmatory hypotheses contributing to Type I error.

Potential sources include:

Possible methods include:

Clearly distinguish:

Confirmatory analyses

from

Nominal or exploratory analyses.

17 Interim Analysis

If applicable, specify:

Possible outcomes include:

18 Subject Disposition

Summarize by treatment group:

Summarize reasons for:

A CONSORT-style subject disposition figure should be produced when appropriate.

19 Demographic and Baseline Characteristics

Summarize important baseline characteristics by treatment group.

Typical variables include:

In randomized trials, formal significance testing of baseline imbalance is generally not necessary; descriptive summaries are usually sufficient.

20 Treatment Exposure and Compliance

Summarize:

If relevant, summarize rescue medication and concomitant treatment use.

21 Primary Efficacy Analysis

The primary analysis must be specified in sufficient detail to be reproducible.

For each primary endpoint define:

21.1 Continuous Endpoint

A common method is ANCOVA:

\[ Y_i = \beta_0 + \beta_1 Treatment_i + \beta_2 Baseline_i + \beta_3 Stratification_i + \epsilon_i \]

The treatment effect may be reported as:

  • Adjusted mean difference.
  • Least-squares mean difference.
  • 95% confidence interval.
  • P-value.

For repeated measurements, MMRM may be used.

Typical fixed effects include:

  • Treatment.
  • Visit.
  • Treatment-by-visit interaction.
  • Baseline value.
  • Baseline-by-visit interaction.
  • Stratification factors, when appropriate.

21.2 Binary Endpoint

Possible methods include:

  • Logistic regression.
  • Cochran-Mantel-Haenszel test.
  • Risk difference.
  • Risk ratio.
  • Odds ratio.

21.3 Time-to-Event Endpoint

Possible methods include:

  • Kaplan-Meier method.
  • Log-rank test.
  • Cox proportional hazards model.

Typical treatment effects include:

  • Hazard ratio.
  • Median survival time.
  • Survival probabilities at clinically important time points.

21.4 Count Endpoint

Possible methods include:

  • Poisson regression.
  • Negative-binomial regression.

22 Model Diagnostics and Alternative Models

When appropriate, assess important model assumptions.

22.1 ANCOVA / Linear Models

Consider:

  • Residual distribution.
  • Variance assumptions.
  • Influential observations.

22.2 MMRM

Consider:

  • Covariance structure.
  • Model convergence.

A fallback covariance structure should be pre-specified if the primary covariance structure fails to converge.

22.3 Cox Model

Assess the proportional-hazards assumption when appropriate.

22.4 Logistic Regression

Assess:

  • Model convergence.
  • Sparse-data problems.
  • Separation.

Reasonable fallback methods should be pre-specified when possible.

23 Secondary Efficacy Analyses

For each important secondary endpoint specify:

Clearly indicate whether the analysis is:

24 Supportive Analyses

Supportive analyses may include:

They should support interpretation of the primary analysis rather than replace it.

25 Sensitivity Analyses

Sensitivity analyses evaluate robustness of the primary result.

Common analyses include:

Primary conclusions should consider consistency across these analyses.

26 Subgroup Analyses

Pre-specify clinically meaningful subgroups.

Examples include:

For each subgroup report:

When appropriate, evaluate the treatment-by-subgroup interaction:

\[ Outcome = Treatment + Subgroup + Treatment \times Subgroup \]

Subgroup analyses are usually exploratory unless explicitly included in the confirmatory testing strategy.

27 Safety Analyses

Safety analyses are generally descriptive and based on the Safety Population.

27.1 Exposure

Summarize:

  • Treatment duration.
  • Dose received.
  • Dose interruptions.
  • Dose reductions.

27.2 Adverse Events

Summarize:

  • Treatment-emergent adverse events (TEAEs).
  • Serious adverse events (SAEs).
  • Severe adverse events.
  • Treatment-related adverse events.
  • Adverse events leading to dose interruption.
  • Adverse events leading to treatment discontinuation.
  • Deaths.
  • Adverse events of special interest (AESIs).

Adverse events are usually summarized by:

  • System Organ Class (SOC).
  • Preferred Term (PT).
  • Treatment group.

The applicable MedDRA version should be specified.

27.3 Laboratory Tests

Summarize:

  • Observed values.
  • Change from baseline.
  • Shift tables.
  • Clinically significant abnormalities.
  • Liver-function abnormalities.
  • Hy’s Law cases when relevant.

27.4 Vital Signs

Summarize:

  • Observed values.
  • Change from baseline.
  • Clinically significant abnormalities.

27.5 ECG

When applicable, summarize:

  • Heart rate.
  • PR interval.
  • QRS interval.
  • QT interval.
  • QTc interval.
  • Clinically important categorical QTc abnormalities.

Additional safety analyses may include:

  • Physical examinations.
  • Suicidality.
  • Immunogenicity.
  • Device events.
  • Disease-specific safety endpoints.

28 Concomitant Medications

Specify:

29 PK, PD, and Biomarker Analyses

If applicable, describe:

These analyses may also be described in a separate PK/PD SAP.

30 Data Handling Conventions

Pre-specify important data-handling rules including:

Rules should be implemented consistently in ADaM datasets and statistical programming.

31 Tables, Listings, and Figures

The SAP should include or reference planned TLF shells.

31.1 Tables

Typical tables include:

  • Analysis populations.
  • Subject disposition.
  • Protocol deviations.
  • Demographics and baseline characteristics.
  • Exposure and compliance.
  • Primary efficacy analysis.
  • Secondary efficacy analyses.
  • Sensitivity analyses.
  • Subgroup analyses.
  • Adverse event summaries.
  • Serious adverse event summaries.
  • Laboratory summaries.
  • Vital signs.
  • ECG.
  • Concomitant medications.

31.2 Figures

Typical figures include:

  • Subject disposition figure.
  • Longitudinal treatment profiles.
  • Kaplan-Meier curves.
  • Forest plots.
  • Treatment-effect plots.

31.3 Listings

Typical listings include:

  • Deaths.
  • Serious adverse events.
  • Adverse events leading to discontinuation.
  • Important protocol deviations.
  • Clinically significant laboratory abnormalities.
  • Important individual subject data.

32 Statistical Programming and Validation

Statistical programming should follow validated procedures.

Where applicable, use the workflow:

\[ SDTM \rightarrow ADaM \rightarrow TLF \]

Analysis variables should be traceable to source data.

Primary and important secondary analyses should undergo appropriate independent validation or quality control.

Statistical outputs should be reproducible from the final analysis datasets.

33 Changes From Protocol

Document any SAP analysis that differs from the protocol.

For each change specify:

Changes made after unblinding should be clearly identified as post hoc.

34 Post Hoc Analyses

Analyses not pre-specified in the protocol or SAP should be clearly labeled:

Post hoc / exploratory analysis

and should not be presented as pre-specified confirmatory evidence.

35 SAP Approval

The final SAP should be reviewed and approved by appropriate study-team members.

These may include:

The final approved SAP should be version-controlled and archived.

36 Practical SAP Workflow

A practical clinical-trial SAP workflow is:

  1. Protocol and estimand.
  2. Objectives and endpoints.
  3. Statistical hypotheses.
  4. Multiplicity strategy.
  5. Sample size and randomization.
  6. Analysis populations.
  7. Protocol deviations.
  8. Baseline and visit-window rules.
  9. Primary statistical model.
  10. Missing-data strategy.
  11. Intercurrent-event strategy.
  12. Sensitivity analyses.
  13. Secondary analyses.
  14. Subgroup analyses.
  15. Safety analyses.
  16. TLF shells.
  17. ADaM and programming specifications.
  18. Statistical QC and validation.
  19. SAP review and approval.
  20. Finalization before database lock and unblinding.

37 Minimum Critical SAP Checklist

Before SAP finalization, confirm that the following are unambiguously defined:

38 Core SAP Principle

A useful way to organize the statistical logic of a clinical trial SAP is:

\[ \text{Clinical Question} \rightarrow \text{Estimand} \rightarrow \text{Endpoint} \rightarrow \text{Analysis Population} \rightarrow \text{Statistical Model} \rightarrow \text{Treatment Contrast} \rightarrow \text{Estimate and CI} \]

The critical components that should generally be determined before database lock are:

Estimand \(\rightarrow\) Population \(\rightarrow\) Endpoint \(\rightarrow\) Intercurrent Events \(\rightarrow\) Missing Data \(\rightarrow\) Model \(\rightarrow\) Contrast \(\rightarrow\) Multiplicity \(\rightarrow\) Sensitivity Analysis.