Shortfall Detection
Shortfall detection identifies a future point where a projected available-cash path falls below an explicitly defined threshold.
The result depends on the starting position, included inflows and outflows, obligation timing, forecast horizon, threshold, and treatment of uncertain inputs. Detection is not the same as explanation or advice.
Build a dated cash path, compare each point with the stated threshold, and identify the first crossing. Then trace the result to its contributing inputs before testing any response in a separate Scenario.
Trace the projected path to the first shortfall
A useful result shows both the crossing and the inputs that produced it.
- 01Starting position
Available cash under the selected definition and as-of date
- 02Scheduled movement
Supported inflows, payroll, commitments, tax, debt, and one-time costs
- 03Projected path
Dated balance after the included movements
- 04Threshold crossing
First period below the explicitly stated cash floor
- 05Contributing inputs
Traceable amounts and dates that shaped the crossing
What is Shortfall Detection?
Shortfall detection is the process of identifying when a modeled available-cash position falls below a defined threshold during a selected horizon. The threshold may be zero or another documented cash floor, depending on the analysis.
The projection begins with a stated cash position and carries included inflows and outflows through their dates or periods. Relevant inputs can include realized or explicitly modeled receipts, payroll, recurring commitments, taxes, debt payments, one-time costs, collection timing, and other supported movements.
Detection establishes that the path crosses the threshold. Causal explanation identifies the amounts and timing that contribute to the crossing. Mitigation or Scenario analysis tests a possible response. Those are three different steps and should remain visibly separate.
Detection, explanation, and response are separate
Detection
The modeled path falls below the stated threshold on a particular date or period.
Causal explanation
The result is traced to supported starting cash, receipts, obligations, and timing rather than a generated story.
Scenario analysis
A possible change is modeled separately to show its conditional effect without rewriting the baseline.
Human decision
Leadership decides whether and how to act, using operational, contractual, legal, and financing context.
The threshold and horizon must be named
There is no universal 60-day window and no universal cash floor. A short horizon can miss a later obligation; a long horizon can amplify uncertain assumptions. State the period, threshold, data freshness, and assumption policy whenever the result is presented.
Expected money needs an explicit state
A signed contract, invoice, weighted pipeline amount, expected receipt, and cash received are not interchangeable. If a projection includes an uncertain receipt, label the state and test the later or missing receipt separately.
Why it matters
A shortfall identified before the threshold crossing creates time to investigate the underlying assumptions, confirm payment and obligation dates, and prepare options. The value comes from traceability and lead time, not from declaring one automatic remedy.
A result can also be wrong if the opening cash, timing, or state of a receipt is wrong. The model should make those inputs reviewable before leadership relies on the alert.
What goes into it
- Starting available cash and as-of date
- Included inflows with state and expected timing
- Payroll, commitments, taxes, debt, and one-time outflows
- Forecast horizon and explicitly defined threshold
- Traceable source and review date for each material assumption
Illustrative threshold review
A 12-week path starts with $180,000 and includes recorded payroll, a tax payment, two commitments, and a customer receipt expected in week seven. The balance first falls below the stated $25,000 floor in week six. The team traces the crossing to payroll and tax timing, then tests a later receipt and a deferred discretionary commitment as separate Scenarios. The model does not choose an action.
How RunwayCal helps
RunwayCal Cash Position Forecast carries supported dated cash movements through a projected path. Scenarios can test a delayed receipt, changed commitment, financing assumption, or other hypothetical adjustment without silently changing recorded financial reality.
RunwayCal does not autonomously diagnose a root cause or recommend a mitigation.
Common mistakes
- 1Using a hard-coded horizon or threshold without stating it.
- 2Treating expected revenue, weighted pipeline, or an invoice as cash already received.
- 3Presenting an inferred cause as proven when the underlying inputs are not traceable.
- 4Calling a Scenario result the new financial baseline before the assumption becomes real.
- 5Treating detection as autonomous financial, legal, lending, or operational advice.
Get the Financial Clarity Newsletter
Practical tips on cash flow, runway, and financial decisions for founders, business owners, CFOs, investors, and board members. Free, weekly, no spam.
See the crossing and the inputs behind it.
Review the dated cash path, threshold, and contributing movements before testing a possible response.
Explore Cash Position Forecast