The reason scenario planning gets a bad name in operating companies is that most of it is theater. A big deck, four quadrants, colorful icons, a story about how the future could unfold. Nobody reads it twice. Nobody makes a decision from it. Six months later the scenarios look silly because reality did not pick any of the four quadrants.

Operating CFOs need something different. They need a scenario view that (a) the CEO can hold in their head, (b) the board can absorb in 90 seconds, and (c) FP&A can update in a day. That is the version below.

Why the 4-quadrant version fails at the operating level

The classic scenario-planning workshop produces four futures along two axes (say, demand and regulation). The output is a 40-page slide deck with narratives. It is useful for a 10-year strategy off-site. It is useless for running Q3.

Operating scenarios are narrower. You are not asking “what does the industry look like in 2030.” You are asking “what should we do if revenue lands 12 percent below plan by September.” That question needs a number, a decision tree, and a trigger point. Not a narrative.

The three-scenario approach that actually gets used

Three scenarios. Not two, not five. Two feels binary, five feels like nobody committed. Three forces a real base case and honest brackets.

• Base (60 percent probability). Your best current forecast. What you expect to happen given what you know today.
• Upside (20 percent probability). Not “everything goes right.” A specific, named tailwind that is plausible. A pricing move sticks. A pipeline conversion improves. A cost initiative lands early.
• Downside (20 percent probability). Not “everything goes wrong.” A specific, named headwind. Top customer delays a renewal. Wage inflation hits mid-year. A regulatory change eats 3 points of margin.

Every scenario has one anchoring story. Not five. The anchoring story is what makes the number defensible.

Variables that always matter

Do not sensitize 30 variables. Sensitize 3 to 5. The rest is noise.

Variable	Why it matters	Typical range base to downside
Volume / units sold	Drives revenue and gross margin absorption	Minus 8 to 15 percent
Price realization	Direct P&L, no cost offset	Minus 2 to 5 percent
Wage cost per FTE	Biggest opex line in most businesses	Plus 3 to 8 percent
Top 5 customer retention	Concentration risk lives here	Loss of 1 top-5 account
Working capital days (DSO or inventory)	Cash timing, credit line usage	Plus 5 to 15 days

For most businesses the first three are enough. Add the fourth if you have real customer concentration. Add the fifth if cash is tight or credit facility usage is a live topic.

How to present it: one page, side by side

The output is one page. Three columns (base, upside, downside), P&L rolled up to about 10 lines, cash summary below, and a variance-to-base column for each scenario. That is it.

If your scenario output is a workbook with 40 tabs, nobody outside FP&A will read it. The workbook is fine as source material. The published output is one page.

Below the numbers, add three short blocks (two sentences each): the anchoring story for upside, the anchoring story for downside, and the trigger points that would move the base case into either.

How to update after actuals land

Do not rebuild scenarios every month. Rebuild the base case monthly (that is the rolling forecast). Refresh the upside and downside quarterly, or immediately if a named trigger fires.

Named triggers to update off-cycle: a top-5 customer signals churn, a covenant test gets tight, a new tariff or regulation lands, or a fundraise timeline shifts. Anything else can wait for the quarterly refresh.

What sponsors and boards actually do with it

Here is the honest version. Boards and sponsors do three things with scenario output:

1. Sanity-check management. If the downside scenario is 5 percent below base, they do not believe you. If it is 40 percent below base, they do not believe you either. A credible downside is usually 10 to 18 percent below base.
2. Pressure-test liquidity. They look at cash in the downside case. If cash goes negative in month 7 of the downside, they want to know what you would do in month 3 to prevent it.
3. Set covenant math. If the downside case breaks a covenant, that is a real conversation with the lender before the covenant actually breaks. Scenario work is often the trigger for a proactive covenant amendment.

Notice what they do not do: they do not memorize the upside narrative and they do not challenge the base case line by line. Scenario output is a risk tool, not a target-setting tool.

The scenario question that stumps most FP&A analysts

Sponsor asks: “What would have to be true for the downside case to actually happen?”

Most analysts answer with a number (“revenue would have to be 12 percent lower”). That is the wrong answer. The sponsor already sees the number. They want the causal story.

The right answer sounds like: “Our downside assumes we lose our second-largest customer at renewal in Q3 and cannot replace 60 percent of the revenue in the same year. It also assumes wage inflation runs at 6 percent, which is 3 points above our current run-rate. If both of those happen, we land at the downside number. If only one happens, we land roughly halfway between base and downside.”

That is scenario planning as an operator uses it. Numbers plus a story plus a trigger.

Common failure modes

• The downside is not down enough. If your downside is 3 percent below base, you have not tested anything. A real downside is 10 to 20 percent below base.
• The upside is a wishlist. “Sales team overachieves quota by 20 percent” is not a scenario. It is a hope. A real upside has one named change and traceable math.
• No cash view. Scenarios that stop at operating income are half-done. The board cares about cash and covenants, so the scenarios have to run through to cash.
• Static probabilities. If your probabilities have not moved in three quarters, you are not paying attention. Probabilities should shift as the year progresses and information arrives.

How to build the three-scenario model in a week

Do not treat scenarios as a separate model. They are three runs of the same driver-based P&L, with different inputs.

1. Day 1: Confirm the drivers. Pick the 3 to 5 variables from the table above. Confirm base-case values with the owners. Do not skip this step. If sales, ops, and HR do not agree the base values are right, the scenario work will be argued into the ground later.
2. Day 2: Define the upside and downside stories. One page each. What is the causal event, what changes on the P&L, and over what months does it hit. If you cannot write it in one page, the scenario is not sharp enough.
3. Day 3: Set the driver values. For each of the 3 to 5 drivers, set a base value, an upside value, and a downside value. Ranges should tie to the causal story, not to round-number percentage moves.
4. Day 4: Run the model three times. Cash flow, not just P&L. If the model cannot flex from a driver change to a full cash statement in under a minute per run, you have a build problem.
5. Day 5: Draft the one-pager and pressure test. Walk it with the CEO before the board sees it. If the CEO cannot defend the downside story in three sentences, revise the story.

A week is plenty. Anything longer means you are polishing.

FAQ

How is a scenario different from a sensitivity analysis?

Sensitivity moves one variable at a time. Scenarios move multiple variables together in a way that reflects a real state of the world. Both are useful. Sensitivities help you find the variable that moves the number most. Scenarios help you decide what to do.

How often should we refresh scenarios?

Base case every month (that is your rolling forecast). Upside and downside every quarter, plus immediately when a named trigger fires.

Should scenarios include a fundraise or exit assumption?

Only if the fundraise or exit meaningfully changes the operating plan in the horizon you are modeling. If it is a “someday” event, keep it out. Scenarios are for decisions in the next 12 months.

How do I set probabilities?

60 / 20 / 20 is the honest starting point for most businesses. Adjust if you have real information. If your business is under structural pressure, the downside probability should rise. If a specific tailwind is likely, the upside probability should rise. Do not use probabilities to send a message. Use them to describe reality.

What if my board wants a 5-scenario view?

Give them three, and offer to add a “stress” case (below downside) if they need it for covenant work. Five scenarios almost always collapse back to three in conversation.

Related reading

• The FP&A Budget Cycle That Actually Works
• Rolling Forecasts vs Annual Budgets
• The PE-Backed CFO Board Reporting Package
• Rolling 13-Week Cash Flow with Claude
• CFO Prompt Library

Sources

• AFP FP&A Guide, Scenario Planning. afponline.org
• AICPA Corporate Finance Insights. aicpa-cima.com
• McKinsey research on scenario-based planning. mckinsey.com

Written by The Pragmatic CFO. 15+ years running FP&A and building AI-native finance workflows across portfolio companies.