| Vose Software

Industry: Biotech
Product: Tamara
Application: Product launch uncertainties


How Many Days of Contingency Buys an 80% Chance of Shipping On Time? +190

A gene-therapy commercial launch — dossier assembly through first commercial shipment — was scheduled the orthodox way: eleven workstreams, each with a most-likely duration, chained through the network and read off the end as a clean January 2028 first shipment the company carried to its commercial leadership and its revenue model. The board's real question was never "is the date right?" — every experienced launch team knows a single-point date is optimistic. The question is the operational one: how much contingency do we commit to, and what level of confidence does it buy? A point estimate cannot answer that. A distribution can.

Rebuild the launch in Tamara, Vose Software's Monte Carlo project risk tool, with Beta-PERT durations and six discrete risk events, and the contingency ladder answers the board's question directly — each rung is the schedule reserve required to reach a given confidence level:

Contingency ladder showing days of schedule slack required for P50 through P95 confidence

Against the 605-day deterministic plan, a P50 commitment needs +120 days (finishing day 725), an P80 commitment needs +190 days (day 795 — roughly 6.2 months of contingency), and a near-certain P95 needs +264 days (day 869). Read top-down, the ladder is a menu the board can choose from on the record: pick a confidence level, read the committed reserve, and the rolling-promise cycle is over before it starts. The January 2028 plan, by contrast, carries just a 4% chance of being met — it is the bottom of a ladder, not a rung anyone should stand on.

The contingency is a budget decision too

Every day to launch carries program-team burn, idle CMO reservation and the carrying cost of deferred revenue, so the schedule reserve the board picks is also a budget reserve. Plotting each simulated run in the finish-date / total-cost plane shows the two are one risk on two axes:

Joint density of launch finish date versus total cost split into quadrants by the plan and budget lines

The cloud runs diagonally — late runs are over-budget runs — and in 18% of simulations the launch finishes both late AND over the $66M budget, in the dangerous upper-right quadrant. Pricing three mitigations together (pre-submission scientific-advice meetings with FDA and EMA that shorten response cycles, an at-risk CMO scale-up started before approval with a confirmation run, and an early payer dossier with dual cold-chain lanes) cuts the P80 finish by 49 days (795 to 746 days) and, because schedule drives cost, takes the overrun probability from 18% to 7% — the $2.5M package pays for itself in avoided carrying cost. Choosing a rung on the ladder and pricing this package are the same decision viewed twice.

Where the schedule risk actually lives

To know which reserve to attack first, Tamara ranks each workstream by its cruciality — the rank-correlation between its duration and the launch finish:

Schedule tornado ranking workstreams by correlation with the launch date

The tech-transfer rework loop leads (cruciality 0.52), followed by process validation and release (0.40) and CMO tech transfer and scale-up (0.38). This is the action list, and it is not where leadership expected it: the launch date is governed more by the manufacturing-readiness chain at the contract manufacturer than by any single regulatory review. Duration certainty on tech transfer and validation buys more end-date — and shrinks the ladder more — than anything else.

The discrete risks that drive the tail

Six events were modelled as Bernoulli risks — each may or may not occur, but if it does it adds delay and cost. Ranking them by expected schedule impact (probability x delay) gives a clean Pareto:

Pareto of discrete risk events by expected schedule impact

Four of the six events carry roughly 80% of the expected discrete-event delay — an EU / Japan procedural delay (6.0 weeks expected), an FDA complete-response / questions cycle (5.0), a CMO tech-transfer failure (4.2) and a reimbursement / payer holdout (3.3). Regulatory cycles and the CMO failure together dominate, which tells leadership exactly where the response budget belongs — and explains the height of the upper rungs on the ladder.

The full shipment-date distribution

Collapsing the schedule onto its shipment-date axis shows the shape behind every rung of the ladder:

Distribution of simulated first-shipment dates with the deterministic plan and P50/P90 marked

The deterministic January 2028 plan sits at the extreme left edge of the body — a near-best case, not a central estimate — with the bulk of outcomes between P50 May 2028 and P90 September 2028 and a long right tail. The mean simulated finish is 730 days against the 605-day plan. The histogram is the ladder's raw material: every percentile the board commits against is read straight off this distribution.

What Tamara changed

  • The board chose a contingency level from the ladder (+190 days for P80) instead of defending a single-point date, ending the rolling-promise cycle with commercial leadership and the revenue model.
  • That schedule reserve was simultaneously set as a budget reserve, after the joint density showed an 18% chance of finishing both late and over budget.
  • Risk-reduction effort was redirected to the CMO tech-transfer and validation chain — the highest-cruciality workstreams — rather than assumed to live in regulatory review alone.
  • A $2.5M mitigation package was approved on its tail-clipping effect, cutting budget-overrun probability from 18% to 7% and the P80 finish by 49 days.

Tamara Functionality Used

  • Monte Carlo schedule simulation over the full launch network, with Beta-PERT durations and parallel-path logic across regulatory, manufacturing and access workstreams.
  • Contingency ladder translating each confidence level into the committed days of schedule reserve the board signs against.
  • Joint cost-schedule density showing, per simulated run, that finish-date and cost overruns occur together, plus scenario comparison of the mitigation package.
  • Cruciality analysis ranking workstreams by how much their variability moves the launch date.
  • Discrete risk-event Pareto (Bernoulli occurrence x Triangular impact) ranking regulatory cycles, tech-transfer failure and cold-chain disruption by expected schedule impact.
  • Finish-date distribution for communicating schedule uncertainty to non-technical stakeholders.

A product launch is not a date; it is a distribution the board commits against one confidence level at a time. Tamara is what turns "when do we ship?" into a ladder of fundable choices the commercial team, the board and the supply chain can all sign.