NextConsensus
Start with one claim

NICE scheduled dates: plan for publication, a delay, or a suspension

A UK launch plan, an access milestone, and a first payer conversation are often dated from the expected publication date NICE shows on an appraisal's in-development page. That date is NICE's published expectation for when the final guidance appears, not a commitment, and it can move. Plan for each outcome the date can bring, and read the public documents that already bear on which one it will be.

For UK and European launch, market access, HEOR, and business development teams planning around a NICE publication date.

Read the scheduled date for what it is

The expected date comes from NICE's own in-development page for the appraisal (nice.org.uk/guidance/indevelopment/gid-ta#####), and each registered record below names the page and what it showed at its evidence cutoff. The date is an expectation, not a commitment: it moves for procedural reasons, and the frozen record keeps the date it was registered with.

What the records score is publication of the appraisal's final guidance by that date, whatever the guidance recommends. The recommendation itself is a different question and is not scored. A managed access review publishes new guidance from the review, and the original technology appraisal's publication date never counts; if NICE publishes the review by updating the earlier appraisal in place, the update entry that names the review is the publication date read.

  • The in-development page and the project ID (ID####, GID-TA#####)
  • A new technology appraisal or a managed access review
  • The expected date exactly as the page showed it at the cutoff
  • The population and treatment line the guidance will cover
  • The committee that appraises it, from the record

Plan for each outcome the date can bring

Publication on or before the date. The final guidance page shows a publication date ('Published: <date>'). Whatever the guidance recommends, publication by the date is the scored outcome; a narrower or different recommendation is a separate question for the access plan.

A revised date with nothing published. NICE can revise the expected date, and the record still resolves against the date frozen at registration. Nothing published by the frozen date resolves NO, and the archived date is not moved by a later revision.

A pause or a suspension. However NICE words it, an appraisal paused or suspended past the date resolves NO. A termination stays in the denominator and resolves NO as well.

Removed without publishing. If NICE removes the appraisal from its work programme without publishing anything, the record is resolved as cancelled by an outside event rather than scored as a miss.

Read what is already public about the date

The in-development page is the public source: it shows the expected date, the appraisal's status, and the project ID. The records below were registered from what that page showed at each cutoff, and each frozen rule names the page.

One record is a managed access review of an earlier appraisal (FF-018): the review's publication is the event the forecast scores, never the original appraisal's date.

  • The expected date on the in-development page, and whether it has moved since the cutoff
  • Whether the appraisal is a managed access review of an earlier appraisal
  • The project ID and the GID number the page shows
  • Where the frozen rule's answer comes from, and the earliest date it can be checked

The registered scheduled dates

Each row is a registered estimate that NICE publishes the appraisal's final guidance by the expected date shown on its in-development page at the cutoff, frozen before that date. Beside it is the record's calendar-cycle baseline, a model that knows only the clock. A baseline is a competing estimate frozen at the same cutoff, not an observed result. The record page carries the proposition, the sources, and the rule an adjudicator will read.

NICE guidance by scheduled date: 11 registered · 11 unresolved · 0 resolved. Registry snapshot 2026-10-06.

FF-016NICECalendar cycle baseline 55% Epcoritamab combination · guidance publication Scheduled dateUnresolved FF-017NICECalendar cycle baseline 60% Inavolisib combination · guidance publication Scheduled dateUnresolved FF-019NICECalendar cycle baseline 55% Nivolumab + ipilimumab · guidance publication Scheduled dateUnresolved FF-022NICECalendar cycle baseline 60% Zuranolone · guidance publication Scheduled dateUnresolved FF-014NICE · STACalendar cycle baseline 60% Beremagene geperpavec · guidance publication Scheduled dateUnresolved FF-015NICE · STACalendar cycle baseline 60% Efgartigimod · CIDP guidance publication Scheduled dateUnresolved FF-018NICECalendar cycle baseline 60% Larotrectinib · guidance publication Scheduled dateUnresolved FF-020NICECalendar cycle baseline 25% Orforglipron · guidance publication Scheduled dateUnresolved FF-021NICECalendar cycle baseline 60% Pembrolizumab combination · guidance publication Scheduled dateUnresolved FF-028NICECalendar cycle baseline 55% Obicetrapib · hypercholesterolaemia guidance publication Scheduled dateUnresolved FF-029NICECalendar cycle baseline 55% Polihexanide · acanthamoeba keratitis guidance publication Scheduled dateUnresolved

Technology appraisal (NICE): offered on judgment, with no calibration figure until 15 in the class have resolved.

Confirm the action in NICE's record

The in-development page links to or redirects to the published guidance, or a search of nice.org.uk for the project ID finds it. The publication date is the 'Published: <date>' line on the final guidance page. For a managed access review published as an update to the earlier appraisal, the update entry naming the review is the publication date read.

The public pages can trail the event: each record's rule names a date it may be read from, a week or more after the scheduled date. The recommendation is read from the final guidance, but it is a different question from publication and is not what the forecast scores.

Who needs to prepare if the date moves?

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

Launch and supply

If the decision is earlier
Prepare the steps that start on publication of the final guidance: the funding-window clock, recommendation-dependent materials, and the field plan tied to the approved wording.
If the decision is later
If the date moves or the appraisal is suspended, hold recommendation-dependent commitments and re-date the plan to NICE's revised expectation.

Business development and licensing

If the decision is earlier
Check whether milestones and option windows run from publication of the final guidance or from the recommendation's wording.
If the decision is later
Read what a suspension or a termination does to milestones and access assumptions; publication by a date and a recommendation at all are different conditions.

Market access and HEOR

If the decision is earlier
Bring the evidence package and the funding-window preparation forward; the funding window after publication is on the decision-windows guide.
If the decision is later
Re-date implementation to the revised publication, and keep the recommendation's population requirement separate from the publication date.

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