Skip to content
Assyro AI
Back to Glossary
Clinical Development

Master Protocol

Master Protocol is a single overarching clinical trial protocol under which multiple sub-studies run simultaneously, evaluating several investigational products, several populations, or both within one shared infrastructure, control group, and statistical framework.

Usage Examples

  • Each new arm added to the master protocol still goes in as a protocol amendment before we enroll anyone.
  • The master protocol lets all five arms share one control group, which is where the sample-size saving comes from.
  • Our master protocol spans three sponsors, so safety reporting responsibilities had to be mapped arm by arm.

What is Master Protocol?

Master Protocol is a single overarching clinical trial protocol under which multiple sub-studies run simultaneously, evaluating several investigational products, several populations, or both within one shared infrastructure, control group, and statistical framework.

Master protocols exist because running one trial per product per indication is slow and wasteful. Each separate study rebuilds the same sites, the same control group, and the same infrastructure, then competes for the same patients. A master protocol amortizes that overhead across many questions at once, and lets a shared control arm serve several experimental arms instead of one.

A master protocol covers the shared machinery: eligibility backbone, randomization, the common control, safety monitoring, and the statistical analysis plan governing comparisons across arms. Individual sub-studies sit beneath it. The master protocol does not replace the per-study protocol obligation in the IND, and it is not itself an adaptive design; adaptations are a feature some master protocols use, not a definition.

In practice, master protocols take one of three shapes: basket (one therapy, many diseases), umbrella (many therapies, one disease), or platform (arms opened and closed over time). Whichever shape, the master protocol lives or dies on change control: adding, dropping, or re-randomizing an arm changes the scope of the investigation and triggers a protocol amendment that must reach FDA and the IRB before it takes effect.

Not to be confused with

Basket trial
a basket trial is one shape a master protocol can take (one therapy, many diseases), not an alternative to it. Every basket trial runs under a master protocol; not every master protocol is a basket trial.
Platform trial
a platform trial is a master protocol operated as a standing programme, opening and closing arms indefinitely against a common control. The master protocol is the document; the platform is the operating model built on it.
Adaptive trial design
adaptive design is a set of prespecified rules for modifying a trial based on accumulating data. A master protocol is an organizational container. The two often appear together, but neither implies the other.
Protocol amendment
an amendment is the regulatory filing that changes a protocol already on file. A master protocol is the standing document being amended; adding an arm produces an amendment, not a new master protocol.

The master protocol itself is a design choice, not a regulatory category. The binding obligations come from the IND regulations that apply to every study underneath it.

What you must do

  1. 1File a protocol for each planned study in the IND, including every sub-study running under the master protocol21 CFR 312.23(a)(6)
  2. 2Submit a protocol amendment for any change that significantly affects subject safety, and for any Phase 2 or 3 change that significantly affects the scope of the investigation or the scientific quality of the study, which is what adding or dropping an arm does21 CFR 312.30(b)(1)
  3. 3Make the change only after it has been submitted to FDA for review and approved by the IRB responsible for the study21 CFR 312.30(b)(2)(i)
  4. 4Notify FDA and all participating investigators of potential serious risks as soon as possible and no later than 15 calendar days after determining the information qualifies, regardless of which arm generated it21 CFR 312.32(c)(1)
  5. 5Treat FDA's master protocol recommendations as nonbinding draft and confirm design choices with the review division; the revised draft published 24 June 2026 replaced the 22 December 2023 draft and has not been finalized91 FR 37991

Common mistakes

  • Treating the master protocol as the only protocol

    the IND regulations still require a protocol for each planned study. Sponsors who file only the master document leave every sub-study without a protocol on file, and the gap surfaces as an IND deficiency at exactly the moment an arm is ready to enroll.

  • Adding arms informally

    an arm approved by steering-committee minutes is not an amendment. The change must be submitted to FDA and approved by the responsible IRB before it is made, and subjects enrolled before both conditions are met produce data you will have to explain rather than analyze.

  • Assuming FDA's master protocol guidance is settled

    it is not. The June 2026 revised draft replaced the December 2023 draft of the same name and remains nonbinding. Designing to a draft and reading the review division's silence as agreement is how a design problem surfaces after the data is in rather than before enrollment.

When This Matters

  • Each new arm added to the master protocol still goes in as a protocol amendment before we enroll anyone.
  • The master protocol lets all five arms share one control group, which is where the sample-size saving comes from.
  • Our master protocol spans three sponsors, so safety reporting responsibilities had to be mapped arm by arm.

Frequently Asked Questions

A basket trial tests one therapy across several diseases sharing a molecular target; an umbrella trial tests several therapies within one disease, usually assigned by biomarker; a platform trial adds and drops arms over time against a common control. All three are master protocol structures, differing in what is held constant.

Related Use Cases

Related Regulatory Intelligence

Related Actions

Sources & References

Share this page
Agent CTA Background

Simplify Master Protocol compliance