Skip to content
One-PagerReviewed

F0292: Liquidity Contingency Runway Framework

A decision-ready template derived from the framework.

Name variants

English
F0292: Liquidity Contingency Runway Framework
Katakana
コンティンジェンシー・ランウェイフレームワーク
Kanji
流動性

Quality / Updated / Source / COI

Quality
Reviewed
Updated
COI
none

Context

Context: trial delays that threaten funding timelines makes defining liquidity runway tiers and contingencies hard because teams interpret cash runway months, burn rate, and committed liquidity and revenue scenarios, cost reduction levers, and funding options differently. Without a shared frame, the survival runway versus growth momentum tradeoff stays implicit and accountability erodes. A structured decision record is required so future reviews can challenge assumptions without restarting the debate.

Options

  • Option A: Maintain the current approach to minimize disruption, accepting limited improvement in cash runway months, burn rate, and committed liquidity.
  • Option B: Pilot a phased change, validate against revenue scenarios, cost reduction levers, and funding options, and scale once the survival runway versus growth momentum criteria hold.
  • Option C: Redesign the approach end-to-end to pursue larger gains, with higher execution risk and change cost.

Decision

Decision: Choose Option B. Validate assumptions for revenue scenarios, cost reduction levers, and funding options, confirm cash runway months, burn rate, and committed liquidity baselines, and proceed only if the survival runway versus growth momentum tradeoff remains acceptable. Document runway thresholds and contingency actions, owners, constraints, and review dates to keep accountability clear.

Rationale

Rationale: Option B balances the survival runway versus growth momentum tradeoff while preserving flexibility. It tests whether cash runway months, burn rate, and committed liquidity respond as expected to revenue scenarios, cost reduction levers, and funding options before committing to a full rollout, reducing the risk of locking in a costly path based on weak evidence. The staged approach also creates learning loops and makes governance confidence easier to sustain over time.

Risks

  • Delayed data refresh can mask shifts in cash runway months, burn rate, and committed liquidity and cause late responses to emerging risks.
  • Execution slippage can erode confidence and widen survival runway versus growth momentum costs before corrective action is taken.

Next

Next: Assign owners for cash runway months, burn rate, and committed liquidity and revenue scenarios, cost reduction levers, and funding options, finalize baseline values, and publish trigger thresholds. Schedule the first review checkpoint, define escalation paths, and document stop conditions so the decision can be revisited quickly.