Scenario Planning vs. Sensitivity Analysis: What Your Board Is Actually Asking For

When a board member asks "what happens if we lose the top customer," most finance teams open the model, cut revenue 15%, and send back the new EBITDA number. That's not scenario planning. That's sensitivity analysis, and the difference matters more than it sounds.

The 2026 AFP FP&A Benchmarking Survey found that only 38% of finance teams use structured scenario planning, even though the ones that do report meaningfully better outcomes: 14% higher strategic alignment with the business, and budgets built in 8.1 weeks instead of 9.2, an 11% faster cycle (AFP, 2026). Almost everyone keeps a risk list. Very few build actual scenarios. The gap between those two things is where boards lose confidence in their finance function.

The one-line difference

Sensitivity analysis changes one variable and holds everything else constant. Revenue down 10%, what happens to EBITDA?

Scenario planning changes the world and asks how the whole business responds. The top customer leaves, so revenue drops, but so does the variable cost tied to serving them, and you'd cut two open roles, delay the warehouse buildout, and draw on the revolver in month four. What does that look like?

Sensitivity is arithmetic. A scenario is a story with numbers attached, and the numbers have to move together the way they would in real life.

That's why sensitivity analysis alone tends to mislead. Cut revenue 15% in a spreadsheet and the model still shows you hiring on schedule and spending the full marketing budget. No real company operates that way. The model says you're fine when you're not, or says you're dead when you'd actually be fine after obvious cuts.

Why PE boards keep asking for this

If you're PE-backed, your sponsor lives in scenarios. Their whole underwriting model was a base case, a downside case, and a management case. So when they ask "what's your downside plan," they're not being difficult. They're asking whether you've done the same work on your own business that they did before buying it.

The downside case matters most, and not for the reason people think. A board rarely expects the downside to happen. What they want to know is whether management has already decided what it would do. Which costs go first. Where the covenant gets tight. How many months of runway the plan protects. A team that answers those questions in the meeting looks in control. A team that says "we'd have to look at it" doesn't.

Your lender reads it the same way. If there's a leverage or fixed-charge covenant in your credit agreement, the downside scenario is the covenant math done in advance, before a bad quarter forces the conversation.

The three scenarios worth building

More than three and nobody reads them. These earn their place:

1. Base case

This is your rolling forecast, the plan you actually expect. It should already reflect current pipeline, current churn, current hiring. If your base case is just the annual budget from last October, start there first, because a stale base makes every other scenario meaningless.

2. Downside case

Not the apocalypse. A plausible bad year: your largest customer leaves, or bookings come in 20% light, or gross margin gives back two points because input costs move against you. Pick the version that's most credible for your business, then, and this is the whole point, model the response. Cost actions with dates and dollar amounts. The hiring freeze. The capex you'd push. Show the covenant calculation in each quarter of the scenario, not just at year end.

3. Stretch case

What has to be true to beat plan by a real margin, and what breaks first when you do. Growth stresses cash before it prints profit. If sales land 30% over plan, do you have the working capital to fund it? The stretch case is where you find out that success requires a bigger revolver, and it's much cheaper to learn that in a planning meeting than in a cash crunch.

What makes a scenario "structured"

AFP defines structured scenario planning as considering a range of circumstances and projecting potential outcomes to prepare for multiple futures. In practice, structured means three things.

The scenarios use the same model and the same drivers. If your downside case lives in a separate spreadsheet with different formulas, comparisons are fiction. Same engine, different assumptions. The same AFP survey found only 47% of teams use consistent variables across their planning, which explains a lot of board meetings where the numbers don't reconcile.

Each scenario has named triggers. A downside case is far more useful when it says "if Q3 bookings fall below $2.1M, we start the cost plan" than when it just shows a sad P&L. Triggers turn a document into a decision.

They get refreshed. A scenario built in January describes January's world. Tie the refresh to your monthly close or your rolling forecast update, so the base moves and the scenarios move with it.

Q: How is a scenario different from a contingency plan? A contingency plan says what you'd do. A scenario shows what the numbers look like while you do it, including the lag. Cost actions take a quarter to show up in the P&L, and severance costs money before it saves money. The scenario captures the timing; the contingency plan usually doesn't.

Why so few teams do it

Not because finance leaders disagree with any of the above. It's capacity. Structured scenarios require a driver-based model, a current rolling forecast, and someone with the time to maintain three versions of the future while also closing the books. The AFP survey found only 43% of organizations even use rolling forecasts, and you can't realistically run scenarios on top of a static annual budget. The prerequisite is missing.

That's also why the fix usually isn't a heroic effort before the next board meeting. It's building the model once, properly, with drivers instead of hardcoded line items, so that a new scenario is a half-day of assumption changes instead of two weeks of spreadsheet surgery.

Build the downside case before anyone asks for it. The week your biggest customer wobbles is the worst possible week to start modeling what losing them means.

Plametrix builds and maintains this as an outsourced FP&A service: the driver-based model, the rolling forecast underneath it, and board-ready base, downside, and stretch cases refreshed every month, for PE-backed and growth companies in the $5M–$50M range.