One forecast tells you what you expect. Scenarios tell you what you would do if you're wrong.
Cash flow scenario planning runs the same forecast under different assumptions, usually base, downside and upside, to see how low cash could fall and when. Put the key drivers, such as sales growth, collection days and cost changes, in an input table with one column per scenario, select the active scenario with a switch cell, and agree in advance the actions you will take if cash heads towards the downside.
A scenario is only as useful as the assumptions it changes. Most businesses only need four to six drivers:
On an Inputs sheet, list the drivers down column A and put one column per scenario:
| Driver | Base (B) | Downside (C) | Upside (D) | Live (E) |
|---|---|---|---|---|
| Sales vs plan | 100% | 85% | 110% | formula |
| Days to collect | 40 | 55 | 35 | formula |
| Days to pay suppliers | 30 | 20 | 30 | formula |
| Gross margin | 45% | 40% | 46% | formula |
The figures above are illustrations only; use your own. Put the scenario number (1, 2 or 3) in a cell named Scenario, and in the Live column:
=CHOOSE(Scenario,B2,C2,D2)
Every formula in the forecast reads from the Live column only. Change the switch and the whole forecast moves. Add data validation on the switch cell (a list of 1, 2, 3) so nobody types a 4. See data validation for finance templates.
Switching is good for exploring, but the people reading the forecast want one view. Copy the closing cash line for each scenario into a summary table (paste values, or use a data table) and chart the three lines with the minimum cash buffer as a fourth line. The month where the downside line crosses the buffer is the most important date on the page.
Use Excel's one-variable data table to see how the lowest closing cash changes as one driver changes:
=MIN(Forecast!B21:M21).Repeat for each driver. The one that moves lowest cash the most is where you should spend management time, and usually where collection effort pays off. See DSO for how collection days translate into cash.
Instead of asking what happens in the downside, ask what would have to happen for cash to fall below the buffer or a covenant to break. Use Data > What-If Analysis > Goal Seek: with the switch set to 1, set the lowest-cash cell to the buffer amount by changing the Base sales cell. Note the result, then put the original value back. If a modest fall in sales is enough, the business is more fragile than the base case suggests. Check covenant tests in the same way: see debt covenant monitoring.
Scenarios earn their keep when they come with a plan. For the downside, write down:
The method is the same in the UK and US. Lenders on both sides commonly ask for a downside case when reviewing a facility, and some covenant definitions differ by agreement, so test each covenant exactly as your facility agreement defines it rather than using a standard formula.
AI software that turns a bank statement into a cash flow dashboard on your own computer: balance day by day, money in and out, recurring payments and a 13-week forecast. $1,997 once-off; see it on the built-in example first.
The Cash Flow Forecasting & Liquidity Control System tests every week of a rolling cash forecast against your minimum cash buffer and lending covenants, and flags a breach before it lands. Excel, no macros, one-time price.
Three is usually enough: base, a realistic downside and an upside. Add a severe stress case if you have borrowing or covenants to protect.
Yes. Problems tend to arrive together, so a downside that changes only one driver understates the risk.
Each time the forecast is updated. Re-check the driver values against actual results at least quarterly.
Last updated 08 November 2026. General guidance for finance teams; check it against your own policies, systems and local rules.