Interpret sensitivity, scenarios, simulation, and risk-return evidence before recommending a finance option.
Sensitivity and scenario analysis answer a risk question: what could change the decision? A base-case projection is useful only if management understands which assumptions drive the outcome and whether the downside case remains acceptable.
In Finance elective writing, sensitivity work should not stop at changing one input. The response should identify the key driver, interpret the downside, compare alternatives, and connect the result to strategy, liquidity, risk tolerance, and implementation.
Sensitivity, scenario, simulation, and risk-return analysis are related but different.
| Tool | What it tests | Better use |
|---|---|---|
| Sensitivity analysis | Effect of changing one assumption at a time. | Identifying the variable that most changes value, cash flow, or return. |
| Scenario analysis | Combined effect of a coherent set of assumptions. | Comparing base, downside, and upside outcomes. |
| Simulation | Many possible outcomes based on probability assumptions. | Understanding a range of results when uncertainty is high and inputs interact. |
| Risk-return analysis | Whether expected return compensates for risk, liquidity, and downside. | Ranking alternatives with different risk profiles. |
| Strategic fit analysis | Whether the option supports the entity’s objectives and constraints. | Preventing a financially attractive option from conflicting with strategy or capacity. |
Sensitivity work asks which assumption changes the answer:
[ \text{Sensitivity impact} = \text{Revised outcome} - \text{Base-case outcome} ]
[ \text{Downside gap} = \text{Required threshold} - \text{Downside outcome} ]
The recommendation should state whether the downside case still fits the entity’s risk tolerance, liquidity, financing capacity, and strategic objective.
Sensitivity analysis isolates the effect of one variable. It is useful when management needs to know which assumption deserves the most attention.
| Variable | Why it may drive the result |
|---|---|
| Sales volume | Affects revenue, contribution, working capital, and capacity use. |
| Price | Can materially affect margin and demand. |
| Input cost | Affects gross margin and cash requirements. |
| Discount rate | Changes present value and project attractiveness. |
| Terminal value | Can dominate valuation conclusions. |
| Exchange rate | Changes foreign purchase cost, foreign revenue, or debt service. |
| Interest rate | Changes debt cost, covenant headroom, and refinancing risk. |
| Capital cost | Changes funding need, payback, NPV, and liquidity. |
The conclusion should name the most sensitive assumption and explain what management should verify or monitor.
Scenario analysis combines assumptions into a story. A downside scenario should not be a random set of pessimistic numbers. It should reflect a plausible operating condition.
| Scenario | Typical purpose |
|---|---|
| Base case | Management’s expected outcome. |
| Downside case | Tests whether the entity can tolerate weaker demand, higher costs, delayed launch, or tighter financing. |
| Upside case | Shows potential benefit if assumptions improve. |
| Stress case | Tests survival under severe but plausible conditions. |
| Strategic alternative case | Compares different courses of action under the same assumptions. |
If the downside case produces a cash shortfall, covenant breach, negative NPV, or unacceptable service impact, the recommendation should be conditional or modified.
Simulation is useful when multiple uncertain variables interact. A case may not require a full simulation calculation, but it may ask whether a single-point forecast is enough.
Simulation may provide better support when:
Do not recommend simulation just because it sounds advanced. It requires reliable input distributions, relevant data, and users who can interpret the output.
Higher expected return is not automatically better. The entity may prefer a lower-return option if it preserves liquidity, reduces downside, or fits strategic constraints.
| Factor | What to assess |
|---|---|
| Expected return | Is the return high enough for the risk and effort? |
| Downside exposure | What happens if the main assumption fails? |
| Volatility | How variable are outcomes across scenarios? |
| Liquidity | Can the entity fund the option and survive delays? |
| Reversibility | Can management exit, delay, scale, or abandon the option? |
| Strategic fit | Does the option support the entity’s objectives? |
| Operational capacity | Can people, systems, suppliers, and controls execute it? |
| Stakeholder tolerance | Will lenders, owners, members, customers, or regulators accept the risk? |
The best recommendation may be to stage the project, reduce size, secure financing, hedge exposure, renegotiate terms, or defer until a key assumption is confirmed.
Sensitivity analysis should not be separated from strategy. An option can have an acceptable downside but poor strategic fit, or strong strategic fit but excessive financial risk.
| Result pattern | Recommendation implication |
|---|---|
| High return and tolerable downside. | Recommend if implementation and strategic fit are also strong. |
| High return but severe downside. | Modify, stage, hedge, secure financing, or reject depending on tolerance. |
| Low return but strong strategic value. | Consider non-financial benefits and funding limits before rejecting. |
| Strong base case but weak sensitivity support. | Require further evidence before approval. |
| Financially attractive but poor strategic fit. | Reject or redesign unless strategy changes. |
| Strategically necessary but cash-constrained. | Seek phased implementation, financing, partnership, or lower-risk alternative. |
A complete recommendation connects assumptions, sensitivity, scenarios, risk-return, and strategy. It should answer:
For example, a project may have positive base-case NPV, but if a 10% sales shortfall causes a covenant breach, the recommendation should not be unconditional. Management may need staged approval, committed financing, revised pricing, or a smaller launch.
Use this order for sensitivity and scenario questions:
| Pitfall | Correction |
|---|---|
Treating 1.4 Sensitivity as a spreadsheet exercise. |
Explain what the result means for the decision and what evidence limits reliance. |
| Changing one assumption without interpreting risk. | State whether the revised outcome changes the recommendation. |
| Treating the base case as expected truth. | Test downside and support the assumptions. |
| Ignoring liquidity. | Check whether the entity can survive the downside timing. |
| Ranking by return only. | Include volatility, downside, strategic fit, and stakeholder tolerance. |
| Recommending simulation without useful inputs. | Use simulation only when uncertainty and data quality justify it. |