Skip to content
FrameworkReviewed

F0292: Liquidity Contingency Runway Framework

Name variants

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

Quality / Updated / COI

Quality
Reviewed
Updated
COI
none

TL;DR

Liquidity Contingency Runway Framework is a decision framework for defining liquidity runway tiers and contingencies. It aligns cash runway months, burn rate, and committed liquidity with revenue scenarios, cost reduction levers, and funding options, makes the survival runway versus growth momentum tradeoff explicit, and produces a decision record that can be reused and audited.

Applicability

Use when defining liquidity runway tiers and contingencies requires cross-team agreement and the interpretation of cash runway months, burn rate, and committed liquidity or revenue scenarios, cost reduction levers, and funding options is fragmented. The framework clarifies survival runway versus growth momentum, assigns owners, and sets refresh cadence so later reviews can validate the decision without rework. It is especially helpful when auditability or rapid escalation matters.

Steps

  1. Define scope, horizon, and decision owner, then standardize definitions for cash runway months, burn rate, and committed liquidity so comparisons remain consistent.
  2. Gather inputs for revenue scenarios, cost reduction levers, and funding options, document data quality gaps, and align timing and units with the metrics.
  3. Model scenarios to test how survival runway versus growth momentum shifts under plausible ranges; record trigger thresholds.
  4. Select the preferred option, capture constraints and approvals, and summarize the decision criteria in one place.
  5. Publish monitoring cadence and review triggers tied to changes in cash runway months, burn rate, and committed liquidity and revenue scenarios, cost reduction levers, and funding options.

Template

Template: Objective and decision question; Scope and horizon; Metrics (cash runway months, burn rate, and committed liquidity); Key inputs (revenue scenarios, cost reduction levers, and funding options); Scenario ranges and trigger points; Options A/B/C with survival runway versus growth momentum implications; runway tiers and action playbook; Risks and mitigations; Decision criteria; Recommendation; Owner and timeline; Review triggers; Evidence log and data refresh plan.

Pitfalls

  • Treating cash runway months, burn rate, and committed liquidity as sufficient without validating revenue scenarios, cost reduction levers, and funding options creates false confidence and weakens the decision.
  • Overweighting one side of survival runway versus growth momentum leads to policies that break when conditions shift.
  • late activation of contingency measures if data ownership or refresh cadence is unclear.

Case

Case: In a biotech startup, leaders faced trial delays that threaten funding timelines and needed to decide defining liquidity runway tiers and contingencies. Using the Liquidity Contingency Runway Framework, they aligned cash runway months, burn rate, and committed liquidity with revenue scenarios, cost reduction levers, and funding options, mapped where survival runway versus growth momentum flipped, and documented trigger points and guardrails. The decision record shortened escalation cycles, improved cross-functional alignment, and was reused in the next planning review. They also defined a review calendar and contingency actions to keep the policy resilient.

Citations & Trust

  • Principles of Finance (OpenStax)