Cash Flow Scenario Planning: Base, Downside, and Upside Cases

Cash flow scenario planning is the practice of forecasting cash under more than one set of assumptions, usually a base case, a downside case and an upside case, so that you know in advance what each future would do to your liquidity and what you would do about it. A single forecast tells you what you expect. Scenarios tell you what you can survive, and when to act. This guide shows how to design the cases, build them and attach triggers and actions, as part of the wider discipline of cash flow management.

Why one forecast is not enough

Every forecast is wrong in some way. The question is how wrong, and whether you can absorb it. A company with a $200,000 cushion can tolerate a missed month. One with a $20,000 cushion cannot. Scenarios let you quantify that difference before it matters.

They also change behavior. When a finance team can say "if our largest customer pays 30 days late and sales fall 15 percent, we hit our minimum cash line in month five," leaders can agree on actions in advance, instead of arguing during the crisis.

The three standard cases

The upside case is often neglected. Faster growth consumes cash: more inventory, more receivables and earlier hiring. Many companies get into trouble during good times for exactly this reason.

Step 1: Pick the drivers that matter

Do not flex every line. Choose the three to five drivers that move cash the most in your business. Common choices:

• Sales volume or revenue, by the largest customers or channels.
• Days to collect, particularly for the largest accounts.
• Supplier payment terms and any deposits required.
• Cost of goods or key input prices, including freight.
• Inventory purchases, which follow the demand forecast.
• Headcount and payroll timing.
• Capital spending and debt service.

To pick, run a quick sensitivity check: change each driver by 10 percent in the forecast and note how much the minimum cash balance changes. The drivers with the largest effects get scenario treatment. For product businesses, sales and inventory are often at the top of the list, so the link to the demand plan matters. See demand planning and inventory optimization.

Step 2: Define the cases with specific numbers

Write each case as a short list of assumption changes, not a narrative.

Downside example: Sales are 15 percent below base from month 2. Payments fall more slowly than receipts, because many costs are fixed or committed.

Upside example: Sales are 10 percent above base from month 2. Costs rise 5 percent as variable costs and expedited purchases increase.

Keep the cases plausible. A downside that assumes the business loses half its revenue is a crisis plan, not a scenario. A good downside is the kind of thing that has happened, or could happen, in your industry: a customer loss, a bad quarter, a supplier problem.

Step 3: Build and compare the cases

A hypothetical company starts the half-year with $200,000 in cash. The base case has monthly receipts of $520,000 and payments of $500,000. The table below sets out the three cases in thousands of dollars.

Ending cash by month, in thousands:

The base case adds $20,000 a month and ends at $320,000. The downside, with the sales decline of 15 percent and payments that adjust slowly, loses $58,000 in month 2 and continues to decline, reaching $80,000 at month 6. If the minimum cash policy is $100,000, the downside crosses the line in month 5. The upside ends at $455,000, which looks fine but depends on the company being able to fund the additional inventory and receivables the sales growth demands, a point to verify in the working capital detail.

Step 4: Set triggers

A scenario is useful only if it tells you when to act. A trigger is an observable signal that you are moving toward a case. Triggers should be simple and measured regularly.

Review triggers at the same time as your weekly or monthly forecast update, and record which case the business is tracking.

Step 5: Attach actions with amounts and timing

For each downside trigger, list the specific actions, the cash each would release and how long it takes. This turns the scenario into a plan.

Applying the first action to the downside case above, with $20,000 of monthly savings starting in month 3, adds $20,000 in month 3, $40,000 by month 4, $60,000 by month 5 and $80,000 by month 6. Ending cash by month: 154, 156, 158 and 160 for months 3 to 6, so the company stays above its $100,000 minimum through month 6. The earlier the trigger fires, the more months of savings accrue.

Step 6: Include a reverse stress test

A reverse stress test asks the opposite question: how bad would things have to get to breach your minimum cash or a loan covenant? Start from the failure point and work back to the combination of drivers that gets you there.

In the example above, the base case has $220,000 of headroom over a $100,000 minimum at month 6 ($320,000 less $100,000). Assume payments stay unchanged and receipts fall by the same percentage in every one of the six months. A 7 percent decline is $36,400 a month ($520,000 × 0.07), or $218,400 over six months, which uses up almost all of the headroom. So a sustained 7 percent shortfall in receipts, with no change in spending, brings the company to its minimum cash line. Knowing that figure helps you judge how close the danger is.

Step 7: Review and update

Scenarios decay quickly. Update them whenever the base forecast changes materially, and at least quarterly. After each period, compare actual results to the cases. If actuals track the downside, act on the plan. If they track the base, confirm your assumptions. Keep the comparison in your forecast record so you can see how well you anticipated reality, a practice described in how to measure and improve cash forecast accuracy.

Seasonal and project businesses

Where cash swings are built into the business model, scenarios should reflect the timing risks directly: a late season, a weak peak or a delayed project payment. The seasonal case is developed in cash flow forecasting for seasonal businesses.

Tools and governance

Scenario planning needs little more than a spreadsheet with a scenario selector: one cell where you choose base, downside or upside, and formulas that pull the matching assumptions. Some software offers built-in scenario features, which can help if you run many cases. See cash flow forecasting software for what to look for.

Assign ownership. The finance lead maintains the cases, the owner or CFO signs off on the triggers and actions, and operations and sales supply the driver assumptions. Agree on who can invoke each action. If cost cuts need the owner's approval, decide in advance how quickly that approval can happen.

Common mistakes

• Too many scenarios. Three are enough. More cases hide the message.
• Unrealistic downside. If it cannot happen, nobody acts on it.
• No triggers. A scenario without a trigger is an academic exercise.
• Ignoring upside funding needs. Growth consumes cash.
• Static assumptions. Update drivers as conditions change.
• Hidden assumptions. List every change in a visible table so reviewers can challenge it.

FAQs

What are the three cash flow scenarios?

A base case (your best estimate), a downside case (a plausible adverse outcome) and an upside case (a favorable outcome that still tests cash needs for growth).

How many drivers should I flex?

Usually three to five: the ones that move your cash balance most, such as sales volume, collection days, supplier terms and key costs.

What is a trigger in scenario planning?

A measurable signal, such as receipts below a set level for two months, that tells you the business is moving toward a particular scenario and that planned actions should start.

How often should scenarios be updated?

Whenever the base forecast changes materially, and at least quarterly. During a tight period, review them weekly alongside the 13-week forecast.

Is scenario planning only for large companies?

No. A small business can run three cases in a spreadsheet in an hour. The value is highest for companies with thin cash cushions.