1. The Assumption the Business Case Rests On
The Gate 4 business case assumes 62% of covered lives and 38% preferred-tier placement at peak. Those two numbers carry more of the program's value than any clinical parameter, and neither is decided by anything in the clinical program.
| Position at 15 October 2026 | |
|---|---|
| Covered-lives target in the business case | 62% |
| Preferred-tier target | 38% |
| Advisory boards held against plan | 3 of 5 |
| Evidence items on plan | 3 of 6 |
| Function size | 4 people — joint-smallest on the roster |
| Governance | ⚠ Gate condition GC-03, issued at Gate 4 |
4 people, against a working pool of 102. That is not an oversight anyone made deliberately — it is what happens when resourcing follows the visible work, and clinical operations, CMC and regulatory all have visible work from Stage 1 while market access has none until somebody asks what a payer will require.
By the time the question is visible, the evidence that answers it needed to have started two years earlier. That is the shape of this entire document.
2. Who Actually Decides
| Payer segment | Covered lives | Decision cycle | What actually decides it |
|---|---|---|---|
| National PBMs (3) | 58% | Annual, decisions Jul–Sep for a 1 Jan effective date | ⚠ Rebate economics against incumbents already contracted. Clinical differentiation matters only if it changes the rebate a plan can demand. |
| Regional health plans | 19% | Annual, staggered through the year | Follow the national formularies more often than they lead, but move faster when a local employer group pushes. |
| Integrated delivery networks | 13% | Continuous, via P&T committee | Total cost of care rather than drug cost. ⚠ The only segment where a health-economic argument outperforms a rebate. |
| Medicare Part D | 10% | Annual bid cycle, submitted the preceding June | Formulary tiering under plan-specific rules. Long lead, low flexibility. |
That is the uncomfortable finding a clinical program tends to resist. A national pharmacy benefit manager choosing between comparable products in a well-characterized class is running a procurement, not a scientific evaluation. Clinical differentiation matters to them only insofar as it changes the rebate a plan can extract — a genuinely better-tolerated product has leverage, and a marginally different one has none.
Which is why the labeling outcome and the access outcome are one problem arriving twice. Without a differentiating claim there is nothing to negotiate with except price.
The exception is worth noting because it is the only one. Integrated delivery networks buy total cost of care rather than drug cost, which is the single segment where a health-economic argument outperforms a rebate. They are 13% of covered lives — real, and not enough to carry a business case built on 62%.
3. What Payers Require, and When
| What a payer asks for | Where it comes from | When it must exist | Position |
|---|---|---|---|
| Pivotal efficacy and safety | From the CSRs | At launch | Necessary and nowhere near sufficient. Every competitor has it. |
| Comparative effectiveness vs the incumbent | Head-to-head trial, or indirect comparison | ⚠ 18–24 months before launch | ⚠⚠ NOT GENERATED. No head-to-head trial was run. An indirect comparison is weaker and a payer knows it. |
| Budget impact model | Health economics, from trial and epidemiological data | 12 months before launch | Buildable from what exists. On plan. |
| Cost-effectiveness / QALY analysis | Modelled from trial outcomes | 12 months before launch | Buildable. Matters most to integrated delivery networks. |
| Real-world evidence | Post-launch registries and claims data | ⚠ Only after launch | ⚠ Structurally unavailable at the decision that matters most — the first formulary cycle. This is the gap no plan can close. |
| Patient-reported outcomes | Collected in the pivotals | At launch | Collected, and sits below the testing hierarchy cut. Supportive, not claimable. |
Comparative effectiveness requires a head-to-head trial, which was assessed and not run — it sits in the scope baseline as an explicit exclusion. An indirect comparison can be constructed instead, and every payer knows it is weaker.
Real-world evidence is structurally unavailable before launch. It comes from claims data and registries that require the product to be in use. ⚠ It is the evidence most persuasive at the formulary decision that matters most, and it cannot exist at that decision. No amount of planning closes that gap; it is a property of the sequence.
Everything else on the list is buildable from data the program already generates, and is on plan. That is the trap in reporting this function green — three of six items on track looks like a program managing a workstream, and the three that are not on track are the two that cannot be and one that is behind. A completion percentage would conceal exactly the wrong thing.
4. The Cycle Collision
Payer formularies are set on payers' calendars. Those dates are published, they do not move for a product launch, and the program's own dates can be laid against them today.
| When | What happens | Consequence |
|---|---|---|
| Jun 2029 | Part D bids submitted for the following plan year | ⚠ Before approval. A product not yet approved cannot be bid. |
| Jul–Sep 2029 | National PBM formulary decisions for 1 Jan 2030 | ⚠⚠ Approval is 5 Oct 2029. THE PRODUCT MISSES THIS CYCLE ENTIRELY. |
| Nov 2029 | Launch | Into plans whose formularies were set before approval existed. |
| Jan 2030 | Formularies take effect | Without the product on them, except by exception. |
| Jul–Sep 2030 | The first cycle the product can actually contest | ⚠ Eight months after launch, and after the program has closed. |
National PBM decisions for the 1 January 2030 plan year are taken between July and September 2029. The action date is 11 October 2029. A product without an approval cannot be added to a formulary, so the first cycle this product can genuinely contest is July–September 2030 — eight months after launch, and after the program has closed.
This is visible today, twenty-four months in advance, and it is not fixable by the program. The filing date cannot move earlier; it is already gated by 68 weeks of treatment on the last participant. And the formulary calendar belongs to somebody else.
What the launch period therefore buys is exception-based access — prior authorizations, medical exceptions, and whatever a field team can negotiate plan by plan. It is real revenue and it is nothing like formulary placement. The business case's 62% assumption implicitly requires the product to be on formulary from launch, and the calendar says it will not be.
5. GC-03 — What Governance Could and Could Not Do
Gate condition GC-03 was issued at Gate 4, requiring a market access evidence plan approved and executed. It is the direct governance response to everything above.
| GC-03 can | GC-03 cannot |
|---|---|
| Require the evidence plan to exist and be approved | ⚠ Create the years of payer evidence collection that should have begun in Stage 2 |
| Require the advisory board program to be completed | Make 2 outstanding boards produce evidence that needed collecting before the pivotals were designed |
| Require a budget impact and cost-effectiveness model | Produce a head-to-head comparison from trials that were never run |
| Force the exposure to be reported at every gate | Move the formulary calendar, or the approval date |
The Committee detected the weakness. It issued a condition with a named owner, a due date and a fixed verification method. The Chief Financial Officer recorded an abstention against the underlying assumption. All of that is correct governance and all of it is on the record.
And none of it can retroactively create evidence, or reposition an endpoint in a testing hierarchy fixed before the first participant was randomized. Acting on a known problem is a management decision; governance guarantees only that the outcome was chosen rather than suffered.
The honest reading of GC-03 is that it converts an invisible assumption into a tracked one. That is worth doing — the alternative is discovering the access position at launch — but it should not be mistaken for a fix. A condition that requires evidence be built two years too late produces a well-documented shortfall rather than no shortfall.
6. What Should Have Happened
Recorded now rather than in the closure report, because the program can still act on part of it.
| Decision point | What was done | What would have been better |
|---|---|---|
| Stage 2, protocol design | Pivotals designed for regulatory approval | ⚠ Payer evidence requirements consulted before the protocol was fixed. The endpoints a payer wants and the endpoints a regulator requires are not the same list, and only one of them was asked. |
| Stage 2, comparator decision | No head-to-head trial; scope exclusion recorded | The exclusion was reasoned and it is the single largest access constraint. A defensible decision can still be the expensive one. |
| Stage 2, resourcing | Market access staffed last and smallest | Staffed early, at the point the evidence had to start. ⚠ The cost of two more people in 2024 is trivial against a 20-point coverage miss. |
| Stage 3, advisory boards | Program begun 2026, behind plan | Begun 2024. Payer input shapes evidence generation only if it arrives while evidence is still being designed. |
That is what a longest-lead assumption means. The window in which market access could have been made solid closed roughly eighteen months before anyone was looking at it, and the artifacts that detect it now — the risk report, the gate condition, this plan — are all instruments for managing a shortfall rather than preventing one.
The transferable lesson is not “resource market access better.” It is: identify which assumption has the longest lead time, and staff that one first, before the work that is visible and urgent crowds it out.
What remains actionable: complete the 2 outstanding advisory boards, build the budget impact and cost-effectiveness models on schedule, construct the strongest defensible indirect comparison, and plan the launch for exception-based access rather than formulary placement — which is a materially different commercial operating model and needs deciding now rather than in 2029.