Scenario Analysis

Scenario analysis compares financial results under coherent alternative assumptions, revealing downside exposure without treating cases as forecasts.

Scenario analysis compares financial outcomes under alternative sets of assumptions that describe different possible conditions. A scenario might combine weaker demand, slower cash collection, and higher input costs to show how a business plan behaves under pressure.

It answers “What would happen if these conditions occurred?” It does not, by itself, say how likely those conditions are.

Key Takeaways

  • A scenario is a coherent set of conditions, not just an optimistic or pessimistic label.
  • Scenarios can test cash flow, valuation, liquidity, financing needs, or other defined outcomes.
  • A base case, upside case, and downside case do not automatically have equal probabilities.
  • Stress scenarios test resilience; they need not represent the most likely forecast.

How to Build Useful Scenarios

Start with a specific question and horizon, such as whether a one-year project creates value or whether a company can meet payments during a downturn.

Then identify the linked drivers. Lower demand might reduce sales receipts while supplier prices rise. A delayed project opening might postpone receipts without postponing every cash payment. Explain those links rather than arbitrarily changing all inputs by the same percentage.

For each case, document the assumptions, calculate the result using the same model, and identify what would change the conclusion. NYU Stern’s probabilistic approaches to risk discusses scenario selection and the distinction between scenario analysis and simulation.

Worked Example: A One-Year Product Launch

Assume a hypothetical launch requires USD 100,000 today. For a simplified comparison, treat all subsequent receipts and payments as occurring at the end of year one, use a 10% annual discount rate, and assume no taxes, residual value, or other cash flows.

The rates and amounts are teaching assumptions, not market estimates.

CaseOperating assumptionsCash receiptsCash paymentsNet cash inflow
DownsideLower sales and higher input costsUSD 130,000USD 50,000USD 80,000
BasePlanned sales and input costsUSD 160,000USD 40,000USD 120,000
UpsideStronger sales with additional fulfillment costsUSD 200,000USD 50,000USD 150,000

For each case:

$$ \mathrm{NPV}=\frac{\text{year-end net cash inflow}}{1.10}-100{,}000 $$
CasePresent value of net cash inflowNPV
DownsideUSD 72,727.27-USD 27,272.73
BaseUSD 109,090.91USD 9,090.91
UpsideUSD 136,363.64USD 36,363.64

The base case has positive NPV, but the downside case destroys value under the assumptions. Management can now examine whether reducing the initial commitment, changing supplier terms, or staging the launch would alter that downside.

Holding the discount rate fixed isolates the operating cases here. In a fuller model, financing conditions and discount rates may also change, with care not to count the same risk inconsistently.

What the Results Do and Do Not Show

The downside NPV is not the cash balance or the largest possible loss. It is the difference between discounted project inflows and the initial cost for that particular case.

The example also cannot establish whether the project can make every interim payment: it deliberately places all subsequent cash flows at year-end. A liquidity review would need a dated cash-flow schedule and available funding.

Likewise, three calculated cases do not mean each has a one-third chance of occurring. Probability-weighted results need justified weights and cases that appropriately cover the modeled outcomes without double-counting them. When probabilities are too uncertain to defend, present conditional results without invented precision.

Scenario Analysis vs. Other Methods

MethodMain questionTypical approach
Sensitivity analysisWhich assumptions drive the result?Systematically vary one or more inputs
Scenario analysisWhat happens under a specified set of conditions?Recalculate a coherent alternative case
Stress testingHow vulnerable is the exposure to adverse conditions?Apply deliberately severe assumptions
Monte Carlo simulationWhat distribution follows from this probability model?Repeatedly sample inputs or paths

These methods overlap. A scenario can be explored with sensitivity tests, and a simulation can be run within a stressed environment. They are distinguished by the question and assumptions, not by the number of spreadsheet cells changed.

The Federal Reserve’s stress-testing explanation illustrates the difference between hypothetical adverse scenarios and economic forecasts. That banking application is not a rule that every business must follow.

Common Mistakes

  • Calling the downside case the worst possible outcome: More severe outcomes may have been omitted.
  • Combining incompatible assumptions: A case needs an explanation for how demand, prices, costs, and financing conditions interact.
  • Ignoring management constraints: Cost cuts, refinancing, and asset sales may take time or fail when needed.
  • Comparing inconsistent models: Keep horizons, currency, tax treatment, and output definitions comparable.
  • Using favorable average results to dismiss liquidity risk: A project can have positive expected value while experiencing an unaffordable cash shortfall.

Check Your Understanding

Loading quiz…

FAQs

Does scenario analysis always need three cases?

No. Choose cases that address the important uncertainties. A focused comparison of two outcomes or a larger set of distinct conditions can be more useful than mechanically adding base, upside, and downside labels.

Can a scenario include only one major change?

Yes. A disruption such as losing a major customer can define a scenario. Its effects may then flow through sales, costs, and liquidity. The key is a coherent conditional case, not a mandatory number of changed inputs.

This article provides general financial education, not a project approval, valuation opinion, or personalized investment recommendation.

Browse Valuation and Analysis