“The worst scenario in the library is the worst outcome that can occur.”
Not quite.A scenario library is finite; unmodeled combinations and feedback can produce more severe outcomes.
Risk
Scenario and Stress Engine
A scenario and stress engine applies coherent alternative assumptions to a system and measures how outcomes change.
Mental model
A stress engine turns one coherent shock story into a repeatable chain from assumptions to consequences.
A useful scenario has a base case, upside case, downside case and stress case rather than one unsupported forecast.
The shocks should be coherent: a demand slowdown may reduce volume, margins and asset values together.
Explore the mechanism
How do coherent changes in several assumptions propagate into value, liquidity, and viability?
This diagram applies a joint stress scenario to three risk factors (equity, rates, credit) and shows the resulting stressed P&L. Use the presets and sliders to see how coherent factor shocks propagate through exposures into total stress loss.
Total stress P&L ≈ +4.90m
Numbers
Equity: shock -8.0% · P&L ≈ 8.00m
Rates: shock 40 bps · P&L ≈ -1.60m
Credit: shock 60 bps · P&L ≈ -1.50m
Total scenario P&L ≈ +4.90m
Interpretation
A scenario is a vector of coherent shocks, not a pile of unrelated tweaks. The stress engine takes this vector, applies it to the market snapshot, and lets the pricing stack convert exposures into factor P&L and total loss.
The practitioner’s view: a good scenario engine makes it trivial to express regulatory and internal shocks as reusable objects and to run them across many portfolios. The key is consistency of factors (the axes) and deterministic wiring, so that “Equity crash” means the same thing everywhere and stress results can be compared across desks and time.
UNDERSTAND
What to notice
A stress engine turns assumptions into repeatable calculations so decisions can be compared rather than narrated after the fact.
Sensitivity analysis asks which assumption changes the result most; stress testing asks whether the system remains viable in a difficult state.
A small example
A coherent demand stress
A business starts with revenue 100, variable cost 40, and fixed cost 45. A stress assumes volume and revenue fall 20%, while variable cost falls proportionally and fixed cost remains.
- Base operating profit is 100 - 40 - 45 = 15.
- Stress revenue is 80 and variable cost is 32.
- Stress operating profit is 80 - 32 - 45 = 3.
ResultA 20% revenue shock reduces operating profit by 80%, exposing operating leverage.
Where it appears
- portfolio and balance-sheet stress testing
- capital and liquidity planning
- testing operational and market dependencies
Where the intuition breaks
What this view leaves out
- A stress result is conditional on the chosen scenario and propagation model; it is not a probability forecast or proof that untested shocks are safe.
Common mistakes
Where this concept sits
Follow the strongest prerequisites, applications, extensions, and contrasts.
Connections for Scenario and Stress Engine
Scenario and Stress EngineYOU ARE HERE
Used byRisk TransmissionA transmission map turns a scenario into a sequence of exposures, buffers and reactions across the system.
UsesMark-to-MarketScenario analysis repeatedly marks positions under shocked market states.
Supported byGreeks and Risk FactorsGreeks give local risk approximations, while scenario engines revalue under larger joint moves.
ValidatesNonlinear RiskStress revaluation tests whether losses accelerate around thresholds or change with the portfolio state.
Contrasts withValue at Risk (VaR)VaR summarises probabilistic loss under a model, whereas stress testing examines explicit adverse scenarios; both are core views of portfolio risk.
UsesCredit Intensity Models and Default CorrelationCredit stress scenarios use default intensities and dependence assumptions to translate shocks into portfolio losses.
Used by · Risk Transmission
A transmission map turns a scenario into a sequence of exposures, buffers and reactions across the system.
Explore concept →