Independent and not affiliated with the FDA, MHRA, ISPE, PDA, or any agency. Get the appgoutham@madhadi.com
madhadi.comData Integrity & GxP Quality
Browse all topics → Articles Templates & Procedures Learning paths GlossaryScenariosToolsRegulatory ReferencesLearning PathsTopics About Start here
Template Plug-and-play starting point Clinical & GCP

Template: Estimand Specification for a Clinical Trial (ICH E9(R1))

A plug-and-play estimand specification built on ICH E9(R1): the five attributes, an intercurrent-event table with a chosen strategy per event, the aligned estimator and sensitivity analyses, and the data-collection consequences, with a filled specimen.

Document type: Template

Read and copy the template below into your own quality system. It is a generic starting point for your own internal use, provided as is, with no warranty; see the Terms and License. Adopting it does not by itself create compliance.

This is a ready-to-use estimand specification for the protocol and statistical analysis plan of a clinical trial, built on the ICH E9(R1) framework. It forces the treatment effect to be defined precisely and in advance, with a chosen strategy for every anticipated intercurrent event, and it makes the data-collection consequences explicit so the estimand is not quietly broken during conduct. Replace every <<FILL: ...>> placeholder. A filled specimen follows. This is educational reference content, not regulatory advice.

Why this template earns its place

Without an estimand, the same data can yield different defensible answers depending on how intercurrent events are handled. E9(R1) removes that ambiguity by requiring the trial to define, before unblinding, the exact treatment effect being estimated. The specification also tells the data-management team which data to chase and the monitoring team which completeness to watch, which is how a statistical definition becomes a data-integrity requirement. See ICH E8(R1) and E9 trial design and statistics.

FieldEntry
Document number<<FILL: DOC-ID>>
Protocol / SAP reference<<FILL>>
Estimand rolePrimary / Key secondary (<<FILL>>)
Version / date<<FILL>>

1. Objective (plain clinical language)

<<FILL: e.g. Does adding drug X to standard of care improve glycemic control in this population?>>

2. The five attributes

#AttributeSpecification
1Treatment<<FILL: intervention and comparator, dose, background therapy, duration>>
2Population<<FILL: the population by key eligibility criteria>>
3Variable (endpoint)<<FILL: the per-patient measurement, e.g. change from baseline in HbA1c at week 24>>
4Intercurrent event handlingSee the table in section 3 (one strategy per anticipated event)
5Population-level summary<<FILL: e.g. difference in means, odds ratio, hazard ratio>>

3. Intercurrent events and chosen strategy

List every anticipated intercurrent event (ICE) and the single strategy chosen for it, with a clinical justification. Strategies: treatment policy, hypothetical, composite, while on treatment, principal stratum.

Anticipated ICEStrategyClinical justificationData-collection consequence
<<FILL: e.g. discontinuation for adverse event>><<FILL>><<FILL>><<FILL: e.g. collect endpoint at week 24 regardless>>
<<FILL: e.g. use of rescue medication>><<FILL>><<FILL>><<FILL>>
<<FILL: e.g. death>><<FILL>><<FILL>><<FILL>>

4. Estimator and analysis

ItemSpecification
Primary estimator (method targeting the estimand)<<FILL: e.g. MMRM / multiple imputation with stated assumption>>
Missing-data assumption, aligned to ICE strategy<<FILL: e.g. missing at random, consistent with treatment policy>>
Analysis population<<FILL: e.g. Full Analysis Set>>
Multiplicity handling<<FILL: hierarchy / gatekeeping / alpha allocation>>

5. Sensitivity and supplementary analyses

TypeAnalysisWhat it tests
Sensitivity (same estimand, relaxed assumption)<<FILL: e.g. missing-not-at-random tipping-point>>Robustness of the primary estimate
Supplementary (additional question)<<FILL>><<FILL>>

6. Data-integrity consequences (hand-off to operations)

  • Data that are critical to this estimand: <<FILL>> (these become High CtQ data, see the CtQ factor register).
  • The EDC must not close the casebook on discontinuation where post-ICE data are required.
  • Monitoring watches completeness of the estimand-critical data against a numeric tolerance.

Sign-off

RoleNameSignatureDate
Clinical lead<<FILL>>
Biostatistician<<FILL>>
Clinical QA<<FILL>>

Filled specimen

Example primary estimand for a phase 3 glycemic-control trial.

Objective: Estimate the effect of drug X 50 mg once daily versus placebo, each added to standard of care, on glycemic control.

Five attributes:

#AttributeSpecification
1TreatmentDrug X 50 mg once daily plus standard of care vs placebo plus standard of care, over 24 weeks
2PopulationAdults with type 2 diabetes meeting eligibility, HbA1c 7.5 to 11.0 percent at screening
3VariableChange from baseline in HbA1c (percent) at week 24
4ICE handlingSee table below
5SummaryDifference between arms in mean change from baseline at week 24

Intercurrent events:

ICEStrategyJustificationData-collection consequence
Discontinuation of randomized treatmentTreatment policyEffect of the regimen as used in practiceCollect week-24 HbA1c regardless of discontinuation
Initiation of rescue antihyperglycemic therapyTreatment policyRescue is part of the real-world regimenCollect week-24 HbA1c regardless of rescue
DeathCompositeA meaningful bad outcome; counts as non-responseRecord; classified as non-responder

Estimator: MMRM on change from baseline, FAS, missing at random assumption consistent with treatment policy. Multiplicity: fixed hierarchy, primary then key secondary. Sensitivity: missing-not-at-random tipping-point. Data-integrity consequence: week-24 HbA1c after discontinuation is High CtQ data; the EDC keeps the casebook open past discontinuation; monitoring escalates if the missing rate exceeds 8 percent.

That single specification tells data management to chase week-24 HbA1c even after discontinuation, tells monitoring that week-24 completeness is critical, and tells the statistician exactly what to estimate. It is the line from statistics to data integrity made concrete.

Common inspection findings this template prevents

  • An objective stated (“demonstrate superiority”) with no estimand, leaving discontinuation, rescue, and death unhandled.
  • Intercurrent events treated as missing data by default, breaking a treatment-policy estimand.
  • A missing-data method that does not match the chosen ICE strategy, so the analysis answers a different question.
  • The EDC closing the casebook on discontinuation when the estimand needs post-discontinuation data.

How to adapt this template

  1. Write the objective in plain clinical language first, then derive the five attributes.
  2. List every anticipated ICE and pick one strategy per event, justified clinically.
  3. Choose an estimator that targets the estimand and a missing-data assumption that matches the ICE strategy.
  4. Hand the data-collection consequences to data management and monitoring, and link the CtQ register.
Use madhadi.com as an app Full screen, works offline, one tap from your home screen.