Sensitivity Analysis
What is Sensitivity Analysis?
Sensitivity analysis is a technique that tests how changes in key assumptions, such as costs, volumes or rates, affect the results of a financial model, showing which assumptions matter most.
Updated November 2026 · 5 min read
Sensitivity analysis examines how the output of a financial model changes when its inputs change. Every forecast, budget and business case rests on assumptions, such as how many users will adopt a system, how much a project will cost or how much savings it will produce. Sensitivity analysis varies these assumptions, one at a time or in combination, to see how much the result moves. It answers the question of what happens if an assumption turns out to be wrong.
For IT leaders, sensitivity analysis is a practical way to build more credible business cases and to understand the risks in technology plans. Technology projects are notorious for cost overruns, delays and benefits that take longer to arrive than expected. Showing how the case holds up under less favorable assumptions helps decision makers understand the risk they are taking and focuses attention on the assumptions that matter most.
Definition of Sensitivity Analysis
Sensitivity analysis is a method for assessing how sensitive the output of a model is to changes in its inputs. The output might be net present value, payback period, total cost or annual savings. The inputs are the assumptions used to calculate it.
The analysis typically changes one input at a time by a set amount, such as plus or minus 10 or 20 percent, while holding the others constant, and records the effect on the output. Inputs that cause large changes in the output are the most sensitive and deserve the most scrutiny.
One-Variable Sensitivity and Tornado Charts
The simplest form changes a single input and shows the result. For example, it might show net present value at implementation costs 20 percent below plan, at plan and 20 percent above plan.
When several inputs are tested this way, the results are often shown in a tornado chart, which ranks inputs by the size of their effect on the output. The widest bars at the top show the assumptions that matter most, making it easy to see where to focus.
Scenarios and Break-Even Analysis
Scenario analysis changes several inputs together to reflect a coherent situation, such as a pessimistic case with higher costs, slower adoption and lower savings. Comparing base, optimistic and pessimistic scenarios shows the range of likely outcomes.
Break-even analysis asks how far an input can move before the decision changes. For example, how much could implementation costs rise before net present value falls to zero? If the answer is a small percentage, the case is fragile. If it is large, the case is robust.
Importance of Sensitivity Analysis in IT Financial Management
Technology investments involve significant uncertainty about costs, timelines, adoption and benefits. Sensitivity analysis makes this uncertainty visible and helps leaders decide with a clear understanding of risk.
It also improves communication between IT and finance, since it shows that assumptions have been tested rather than simply asserted.
Stronger Business Cases
A business case that presents a single result can look precise but hide significant risk. Adding sensitivity analysis shows how the result depends on key assumptions and how much margin for error exists.
Finance teams and executives are more likely to approve investments when they can see that the case holds up under reasonable downside assumptions. When it does not, sensitivity analysis helps identify what would need to be true for the investment to succeed, which can inform how the project is structured. It is a standard part of rigorous capital budgeting.
Focusing Risk Management
Knowing which assumptions matter most helps teams focus their effort. If savings depend heavily on retiring an old system by a certain date, that milestone deserves close tracking. If cost is most sensitive to the price of a key contract, negotiating that price becomes a priority.
Sensitivity analysis also improves forecasts. Understanding which drivers have the biggest effect on technology costs, such as user growth or cloud usage, shows where better data and closer monitoring will improve financial forecasting accuracy most.
How to Perform Sensitivity Analysis
Performing sensitivity analysis requires a financial model with clearly separated inputs, a choice of which inputs to test and a consistent way of presenting results.
Spreadsheets are sufficient for most technology business cases, although planning tools can automate the process.
Building the Model and Selecting Inputs
The model should have its assumptions listed separately from calculations, so they can be changed easily. Each assumption should be documented with its source and rationale.
Inputs to test are those that are both uncertain and likely to have a significant effect. For technology investments, these typically include implementation cost, timeline, adoption rate, savings per user or per transaction, ongoing licensing and support costs and the discount rate. The discount rate usually reflects the organization's cost of capital, so finance should agree the range tested.
Presenting and Using Results
Results should be presented simply, using a table or tornado chart showing how the output changes with each input, along with scenarios and any break-even points. The base case should remain the main recommendation, with sensitivity analysis showing its robustness.
The results should influence decisions, not just accompany them. If a case is highly sensitive to one assumption, the organization might pilot the project first, negotiate risk-sharing with a vendor or set clear checkpoints before committing further funds. Comparing actual results with the original analysis afterward improves future models and supports IT financial planning.
Examples of Sensitivity Analysis in IT Financial Management
The examples below apply sensitivity analysis to technology decisions.
Both use illustrative figures, an 8 percent discount rate and end-of-year cash flows.
In each, testing the assumptions changed how the decision was made.
Testing an Automation Business Case
An automation project costs $2 million and is expected to save $700,000 a year for five years, giving a net present value of about $795,000. The team tests each assumption by 20 percent.
If savings are 20 percent lower, NPV falls to about $236,000. If costs are 20 percent higher, NPV falls to about $395,000. If savings start a year late and the existing platform is still retired on schedule, leaving four years of savings, NPV falls to about $147,000. Savings and timing matter most, so the team adds milestones for the process changes that deliver savings and tracks them closely.
Break-Even on a Cloud Migration
A cloud migration is expected to cost $3 million and reduce infrastructure costs by $1 million a year for five years, giving a net present value of about $993,000.
Break-even analysis shows that annual savings can fall to about $751,000, 25 percent below plan, before NPV reaches zero. Migration costs can rise to about $4 million, 33 percent above plan. The case is reasonably robust, and leadership approves it with a contingency for migration costs. The analysis also shows that the savings estimate deserves the closest tracking after the migration, when results are compared with the original total cost of ownership (TCO) estimate.
Conclusion
Sensitivity analysis tests how changes in assumptions affect the results of a financial model, showing which assumptions matter most and how robust a decision is. It uses techniques such as one-variable testing, tornado charts, scenarios and break-even analysis.
In IT financial management, sensitivity analysis strengthens business cases, focuses risk management and improves forecasts. Building models with clear assumptions, testing the most uncertain and influential inputs and acting on the results help organizations make better technology investment decisions.
Related terms
Capital Budgeting
Capital budgeting is the process organizations use to evaluate and select long-term investments, using measures such as net present value, internal rate of return and payback period to compare options.
Financial Forecasting
Financial forecasting is the process of estimating future financial results, such as revenue, costs and cash flow, based on historical data, current trends and planned changes. It is updated regularly through the year.
Cost of Capital
Cost of capital is the minimum return an organization must earn on an investment to satisfy its lenders and shareholders, often measured as the weighted average cost of capital (WACC).
IT Financial Planning
IT financial planning is the process of setting technology spending plans, budgets and forecasts over annual and multi-year horizons, aligning them with business strategy and expected demand.