---
# === IDENTITY ===
id: finance/modeling/sensitivity-analysis/2026
canonical_question: "How do I build sensitivity analysis in a financial model — data tables, tornado charts?"
aliases:
  - "sensitivity analysis"
  - "what-if analysis"
  - "data table analysis"
  - "tornado chart analysis"
entity_type: concept
domain: finance > modeling > Sensitivity Analysis
region: global
jurisdiction: global
temporal_scope: 1960-2026

# === VERIFICATION ===
last_verified: 2026-02-28
confidence: 0.92
version: 1.0
first_published: 2026-02-28

# === TEMPORAL VALIDITY ===
temporal_validity:
  status: stable
  last_breaking_change: null
  next_review: 2026-08-27
  change_sensitivity: low

# === CONSTRAINTS ===
constraints:
  - "Tests one or two variables at a time while holding others constant — does not capture multi-variable interactions or correlated changes"
  - "Requires a working base model — sensitivity analysis is a layer on top, not a standalone framework"
  - "Range selection is subjective — if the tested range is too narrow, the analysis misses important dynamics; too wide, and it includes unrealistic values"
  - "Does not assign probabilities — shows what happens if an input changes, not how likely that change is"
  - "Prerequisite: must have a functioning financial model (DCF, three-statement, startup model) to apply sensitivity analysis to"

skip_this_unit_if:
  - condition: "User needs to test correlated multi-variable changes as coherent scenarios"
    use_instead: "finance/modeling/scenario-analysis-framework/2026"
  - condition: "User needs probability distributions of outcomes, not just ranges"
    use_instead: "finance/modeling/monte-carlo-simulation/2026"
  - condition: "User needs to build the underlying financial model first"
    use_instead: "finance/modeling/three-statement-model/2026"

inputs_needed:
  - key: "sensitivity_goal"
    question: "What does the user want to test?"
    type: choice
    options:
      - "Which inputs drive the most variance in model output"
      - "How valuation changes across a range of WACC and growth rates"
      - "Break-even points for key assumptions"
      - "Visual presentation of input sensitivity for stakeholders"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/finance/modeling/sensitivity-analysis/2026"
suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-02-28)"

# === RELATED UNITS ===
related_kos:
  related_to:
    - id: "finance/modeling/scenario-analysis-framework/2026"
      label: "Scenario Analysis Framework"
    - id: "finance/modeling/monte-carlo-simulation/2026"
      label: "Monte Carlo Simulation"
    - id: "finance/modeling/dcf-framework/2026"
      label: "DCF Framework"
  often_confused_with:
    - id: "finance/modeling/scenario-analysis-framework/2026"
      label: "Scenario Analysis (changes multiple variables together, not one at a time)"
  depends_on: []
  solves: []
  alternative_to: []

# === SOURCES ===
sources:
  - id: src1
    title: "What is Sensitivity Analysis?"
    author: Corporate Finance Institute
    url: https://corporatefinanceinstitute.com/resources/financial-modeling/what-is-sensitivity-analysis/
    type: technical_blog
    published: 2025-01-01
    reliability: high
  - id: src2
    title: "Sensitivity Analysis in Financial Modelling: How to Measure Impact and Risk"
    author: Private Equity Bro
    url: https://privateequitybro.com/sensitivity-analysis-in-financial-modelling-impact-and-risks/
    type: technical_blog
    published: 2025-01-01
    reliability: high
  - id: src3
    title: "Fundamentals of Creating a Tornado Diagram and Sensitivity Analysis"
    author: Edward Bodmer
    url: https://edbodmer.com/fundamentals-of-creating-a-tornado-diagram-and-creating-sensitivity-analysis/
    type: technical_blog
    published: 2024-01-01
    reliability: high
  - id: src4
    title: "Tornado Charts"
    author: SumProduct
    url: https://sumproduct.com/thought/tornado-charts/
    type: technical_blog
    published: 2024-01-01
    reliability: moderate_high
---

# Sensitivity Analysis

## Definition

Sensitivity analysis is a technique for measuring how changes in individual input variables affect a financial model's output, holding all other variables constant. It answers the question "what if this one assumption is wrong?" by systematically varying inputs across a defined range and observing the resulting change in key outputs (e.g., NPV, IRR, enterprise value). The two primary tools are data tables (one-way and two-way grids) and tornado charts (bar charts ranking variables by impact). [src1]

## Key Properties

- **One-way data table**: Varies one input across a range (e.g., WACC from 8% to 12%) and displays the output for each value — shows the shape of the input-output relationship [src1]
- **Two-way data table**: Varies two inputs simultaneously (e.g., WACC on one axis, terminal growth rate on the other) creating a matrix of output values — the standard DCF sensitivity output [src2]
- **Tornado chart**: Horizontal bar chart showing how much each input (varied by ±1 standard deviation or fixed range) changes the output, sorted from most to least impactful — identifies key value drivers [src3]
- **Break-even analysis**: Finds the input value at which the output crosses a critical threshold (e.g., NPV = 0 or IRR = hurdle rate) [src1]
- **Excel implementation**: DATA TABLE function (one-way/two-way), manual recalculation for tornado charts, or Goal Seek for break-even points [src2]

## Constraints

- **One-at-a-time limitation**: Classic sensitivity analysis varies one (or two) inputs while holding others constant. It cannot reveal interaction effects or correlated changes. For that, use scenario analysis or Monte Carlo. [src1]
- **No probability information**: Sensitivity shows what happens if an input changes, not how likely that change is. A variable with high sensitivity but low uncertainty matters less than one with moderate sensitivity and high uncertainty. [src2]
- **Range selection is subjective**: If the tested range (e.g., revenue growth from 5% to 25%) does not reflect realistic uncertainty, the analysis misses important dynamics or includes noise. Ground ranges in historical data or expert estimates. [src3]
- **Data table size constraints**: Excel two-way data tables are limited to two variables. Testing three or more inputs requires multiple tables or tornado charts. [src2]
- **Assumes linearity**: Many presentations imply that the input-output relationship is linear. For non-linear models (e.g., option pricing, leveraged structures), the shape of the relationship matters as much as the endpoints. [src3]

## Framework Selection Decision Tree

```
START — User needs to test model sensitivity
├── How many variables to test?
│   ├── 1 variable → One-way data table or spider chart
│   ├── 2 variables → Two-way data table (standard DCF output)
│   ├── 5-10 variables ranked by impact → Tornado chart
│   └── Many variables simultaneously with correlations → Monte Carlo Simulation
├── Does the user need probability information?
│   ├── YES → Monte Carlo Simulation
│   └── NO → ✅ Sensitivity Analysis (this unit)
├── Should variables change independently or together?
│   ├── Independently → ✅ Sensitivity Analysis
│   └── Together as coherent scenarios → Scenario Analysis
└── What output format?
    ├── Table/matrix → Data table
    ├── Ranked bar chart → Tornado chart
    └── Distribution curve → Monte Carlo Simulation
```

## Application Checklist

### Step 1: Identify key input variables
- **Inputs needed**: The financial model, list of all assumption inputs
- **Output**: Prioritized list of 5-10 inputs most likely to drive output variance (e.g., revenue growth, WACC, terminal growth, margins, capex)
- **Constraint**: Focus on inputs with both high sensitivity AND high uncertainty — a highly sensitive input that is well-known (e.g., tax rate) matters less than a moderately sensitive input that is speculative (e.g., market share growth) [src1]

### Step 2: Define realistic ranges for each variable
- **Inputs needed**: Historical data, industry benchmarks, expert estimates for each variable
- **Output**: Min/max range (or ±1 standard deviation) for each input
- **Constraint**: Ranges must be grounded in data — arbitrary ranges (±50%) produce misleading results. Use historical volatility for market-driven inputs and management guidance for operational inputs. [src3]

### Step 3: Build data tables and tornado charts
- **Inputs needed**: Model, identified variables, defined ranges
- **Output**: One-way tables for key variables, two-way table for the two most critical inputs (e.g., WACC vs. terminal growth), tornado chart ranking all inputs by impact
- **Constraint**: Two-way data tables must use Excel's DATA TABLE function (Data → What-If Analysis → Data Table) for accurate recalculation — manual formulas are error-prone for large tables [src2]

### Step 4: Identify break-even points and present results
- **Inputs needed**: Data tables, model threshold values (e.g., target IRR, minimum NPV)
- **Output**: Break-even values for key inputs (e.g., "Revenue growth must exceed 8% for positive NPV"), visual summary for stakeholders
- **Constraint**: Present sensitivity analysis alongside the base case — never show a tornado chart without the base case output as the reference point [src4]

## Anti-Patterns

### Wrong: Testing only upside sensitivity
An analyst shows how NPV improves with higher revenue growth and lower WACC but does not test the downside. This creates a false sense of confidence. [src1]

### Correct: Testing symmetric ranges
Vary each input both above and below the base case by the same amount. Tornado charts should show both positive and negative impact bars for each variable. [src3]

### Wrong: Using arbitrary ranges (±50%) for all variables
An analyst applies the same percentage range to all inputs regardless of their actual uncertainty, making a stable input (tax rate) look as uncertain as a speculative one (market growth). [src2]

### Correct: Calibrating ranges to actual uncertainty
Use historical standard deviations for market variables, management's confidence interval for operational variables, and expert judgment for novel assumptions. Each variable gets its own justified range. [src3]

### Wrong: Confusing sensitivity analysis with scenario analysis
An analyst changes revenue, margins, and growth simultaneously and calls it "sensitivity analysis." This is scenario analysis — sensitivity analysis changes one variable at a time. [src1]

### Correct: Keeping variables independent
In sensitivity analysis, change one variable while holding all others at base case values. Label the work correctly — if multiple correlated variables change together, call it scenario analysis. [src1]

## Common Misconceptions

- **Misconception**: The variable with the widest bar on a tornado chart is the biggest risk.
  **Reality**: A tornado chart shows sensitivity (impact of change), not risk (likelihood of change). A variable with high sensitivity but near-certain value (e.g., contracted revenue) is a low risk. Combine sensitivity with probability assessment for actual risk ranking. [src3]

- **Misconception**: Two-way data tables show all important interactions.
  **Reality**: Two-way tables show the interaction between exactly two variables. Real models have 10+ uncertain inputs with complex interactions. Data tables are a starting point; Monte Carlo simulation captures the full interaction space. [src2]

- **Misconception**: Sensitivity analysis validates a model.
  **Reality**: Sensitivity analysis tests how outputs change with inputs — it does not validate whether the model structure or base assumptions are correct. A structurally flawed model produces consistent but wrong sensitivity results. [src1]

## Comparison with Similar Concepts

| Concept | Key Difference | When to Use |
|---|---|---|
| Sensitivity Analysis | Varies 1-2 inputs at a time, others held constant | Identifying which inputs drive the most output variance |
| Scenario Analysis | Changes multiple correlated inputs simultaneously | Testing coherent alternative futures (recession, expansion) |
| Monte Carlo Simulation | Randomly samples all inputs from distributions | Generating probability distributions of outcomes |
| Stress Testing | Applies extreme but plausible shocks | Testing model survival under crisis conditions |

## When This Matters

Fetch this when a user asks about building sensitivity tables, creating tornado charts, running what-if analysis on a financial model, identifying key value drivers, or building two-way data tables for DCF output. Also relevant when someone needs to present model sensitivity to investors, boards, or lending committees, or when choosing between sensitivity analysis, scenario analysis, and Monte Carlo.

## Related Units

- [Scenario Analysis Framework](/finance/modeling/scenario-analysis-framework/2026)
- [Monte Carlo Simulation](/finance/modeling/monte-carlo-simulation/2026)
- [DCF Framework](/finance/modeling/dcf-framework/2026)