Label expansion readiness: planning for a new indication

A possible new indication changes the questions a team needs answered before launch. It does not change the approved label. Anchor readiness work to the precise population, treatment setting, and regulatory action being considered.

For regulatory strategy, launch operations, market access, and competitive intelligence teams.

Separate the indication question from the review clock

Upstream trial evidence on rungs 1–4 can support a question about regulatory action on rung 6. Record the application or supplement, the proposed indication, and the source for each procedural milestone. A submission, an acceptance, a review target, and an approval are distinct facts.

Use the agency's published record for an action already taken. Attribute sponsor statements about a submission to the sponsor. Where an agency date is unavailable, say that it is unavailable; an estimated date should not acquire the appearance of an official schedule.

  • Which population or treatment line would be added?
  • Which document establishes the current approved indication?
  • Is the milestone a submission, acceptance, target date, or completed action?
  • Which dependencies remain with guideline panels, payers, and local implementation teams?

Work backward from the date your team needs

For a decision potentially months away, identify work that can be prepared while the outcome remains uncertain: evidence comparisons, an indication-specific dossier outline, internal review ownership, and payer questions. Scientific and commercial materials need the reviews appropriate to their intended use.

Keep a second plan for a later decision. Identify which work remains useful, which assumptions need revision, and which commitments depend on the actual approved wording. A narrower population or a different treatment line may require a different plan even when an approval occurs.

Make the question scorable

Define the named regulator, indication, action, deadline, and document that settles the outcome. A probability of an action by March and a probability of the same action by July answer different planning questions. Neither date should be presented as an agency commitment.

Who needs to prepare if the date moves?

What each team changes if the decision comes earlier or later than planned.

Regulatory and launch operations

If the decision is earlier
Bring document review and operational dependencies forward.
If the decision is later
Reassess sequencing and preserve resources needed for the eventual wording.

Market access and HEOR

If the decision is earlier
Prioritize the evidence package for the proposed population.
If the decision is later
Use available time to address a defined evidence gap, where feasible.

Competing manufacturers

If the decision is earlier
Review whether the relevant comparator and access assumptions change.
If the decision is later
Retain the existing scenario with a dated reason for revisiting it.

Bring the action and your deadline

Which decision matters to your team, and by what date? Include the population and the plan it would inform.

Start with one claim