F0088: Liquidity Triage Sprint Framework

Quality / Updated / COI

Quality

Reviewed

Updated

02/14/2026

Source

Citations & Trust

COI

none

TL;DR

Liquidity Triage Sprint Framework helps teams decide short-term cash survival decisions by aligning daily cash balance, next-30-day payable coverage, and covenant headroom with collection timing, supplier deferrals, and revolver availability. It clarifies the survival liquidity versus vendor trust tradeoff and produces a weekly cash survival plan that can be reviewed and reused.

Applicability

Use when short-term cash survival decisions decisions stall because daily cash balance, next-30-day payable coverage, and covenant headroom and collection timing, supplier deferrals, and revolver availability are interpreted differently across functions. The framework makes the survival liquidity versus vendor trust tradeoff explicit, assigns owners for each input, and sets a refresh cadence for the weekly cash survival plan. It also specifies minimum vendor payment floor and breach alerts to prevent drift.

Steps

1. Define scope, horizon, and decision owner, then baseline daily cash balance, next-30-day payable coverage, and covenant headroom so comparisons are consistent.
2. Collect collection timing, supplier deferrals, and revolver availability, document data quality gaps, and record assumptions that could move the weekly cash survival plan.
3. Run scenarios to test how the survival liquidity versus vendor trust balance shifts and set thresholds tied to minimum vendor payment floor and breach alerts.
4. Select the preferred option, capture constraints and approvals, and finalize the weekly cash survival plan as the single source of truth.
5. Publish monitoring cadence and review triggers tied to changes in daily cash balance, next-30-day payable coverage, and covenant headroom and collection timing, supplier deferrals, and revolver availability.

Template

Template: Objective and decision question; Scope and horizon; Metrics (daily cash balance, next-30-day payable coverage, and covenant headroom); Key inputs (collection timing, supplier deferrals, and revolver availability); Baseline assumptions and data owners; Scenario ranges and trigger points; Options A/B/C with survival liquidity versus vendor trust implications; Guardrails (minimum vendor payment floor and breach alerts); Output artifact (weekly cash survival plan); Constraints and approvals; Risks and mitigations; Decision criteria; Owner and timeline; Review triggers; Evidence log and version history.

Pitfalls

• Treating daily cash balance, next-30-day payable coverage, and covenant headroom as sufficient without validating collection timing, supplier deferrals, and revolver availability creates false confidence and weakens the weekly cash survival plan.
• Overweighting one side of survival liquidity versus vendor trust leads to policies that fail when conditions shift and guardrails are not enforced.
• Missing owners for minimum vendor payment floor and breach alerts causes governance drift and repeated escalation cycles.

Case

Case: A cross-functional team faced conflicting priorities and needed to decide short-term cash survival decisions. Using the Liquidity Triage Sprint Framework, they aligned daily cash balance, next-30-day payable coverage, and covenant headroom with collection timing, supplier deferrals, and revolver availability, documented the survival liquidity versus vendor trust thresholds, and produced a weekly cash survival plan. The guardrails (minimum vendor payment floor and breach alerts) clarified when to pause or escalate, reducing rework in the next review cycle.

Citations & Trust

• Financial Accounting (OpenStax)