Driver-Based Planning

What is Driver-Based Planning?

Driver-based planning is a budgeting and forecasting method that calculates costs from the operational factors that cause them, such as headcount, users or transactions, rather than adjusting last year's figures.

Updated November 2026 · 5 min read


Driver-based planning builds budgets and forecasts from the activities that cause costs, rather than from historical spending. Instead of assuming software costs will rise by 5% next year, a driver-based plan calculates them from the number of employees who need licenses, multiplied by the price per license. When the hiring plan changes, the software budget changes with it automatically.

The approach makes plans easier to explain, faster to update and more closely connected to business decisions. For IT financial management, driver-based planning is particularly useful because many technology costs scale with clear operational measures, such as employees, customers, transactions, storage or compute usage. It allows IT to show business leaders how their own plans affect technology costs.

Definition of Driver-Based Planning

Driver-based planning is a method of planning in which costs, and sometimes revenue, are calculated from a set of business drivers and the rates that link them to costs. A cost driver is any factor whose change causes a change in cost.

The basic formula is cost equals driver volume multiplied by the rate per unit, plus any fixed costs. A plan is made up of many such calculations, each linking a cost category to the drivers that explain it.

Common IT Drivers

Headcount drives many technology costs, including laptops, collaboration licenses, service desk demand and identity management. Customer or transaction volumes drive the cost of customer-facing applications and infrastructure.

Usage measures, such as compute hours, storage volumes and data transfer, drive cloud costs. Project plans drive labor and contractor costs for development work.

Not every cost has a useful driver, and forcing one onto a cost that does not vary adds complexity without improving accuracy. Some, such as certain enterprise licenses and core infrastructure, are largely fixed over the planning period and are planned as fixed amounts.

Driver-Based vs Incremental Planning

Incremental budgeting starts from last year's budget and adjusts it by a percentage. It is quick, but it carries forward past inefficiencies and does not explain why costs change.

Driver-based planning starts from the activities that cause costs. It requires more setup but makes the reasons for cost changes clear and allows the plan to be updated quickly when assumptions change.

Many organizations combine the two, using drivers for the largest and most variable cost categories and simpler methods for small or stable ones.

Importance of Driver-Based Planning in IT Financial Management

Driver-based planning connects technology costs to business decisions, which changes the conversation between IT and the business.

It also makes forecasting faster and more accurate. When business plans change, as they often do during the year, the effect on technology costs can be recalculated in minutes rather than rebuilt from scratch.

Because the logic is visible, finance and business leaders can see how a plan was built and challenge the assumptions rather than the totals.

Linking Costs to Business Plans

When IT costs are calculated from business drivers, business leaders can see the technology cost of their plans. A plan to hire 500 people or double transaction volumes comes with a clear estimate of the IT cost involved.

This shifts discussions from whether IT is spending too much to whether the business wants the activity that drives the spending. It also supports unit economics, such as IT cost per employee or per transaction.

For variable costs such as cloud, driver-based plans help set expectations that spending will rise with growth, rather than treating every increase as an overrun.

Faster Scenario Planning

Because the plan is built from drivers, scenarios can be created by changing a few inputs. Leaders can see the effect of a hiring freeze, a new product launch or a change in cloud pricing without rebuilding the plan.

This is valuable during the annual planning cycle, when finance often asks for multiple versions, and during the year, when rolling forecasts need to be updated quickly.

It also supports sensitivity analysis, showing which drivers have the largest effect on costs.

How to Implement Driver-Based Planning

Implementing driver-based planning involves identifying the main cost drivers, establishing rates and building a model that connects them.

Starting with a few large cost categories keeps the effort manageable. Workplace technology, cloud infrastructure and major business applications are common starting points, since their costs usually have clear drivers and represent a large share of spending. Once these are working, the approach can be extended to other categories.

Identifying Drivers and Rates

Analyze the largest cost categories to find the drivers that explain most of their variation. Good drivers are measurable, forecastable by the business and clearly linked to cost.

Calculate the rate for each driver from historical data and contracts, such as the cost per employee for collaboration software or the cost per thousand transactions for a payment platform.

Agree on the source of each driver forecast, such as HR for headcount and product teams for transaction volumes, so that IT is not forecasting business activity on its own.

Building and Maintaining the Model

The model combines driver forecasts with rates and fixed costs to produce the plan by cost category and period. It should be simple enough for others to understand and review.

Rates should be reviewed regularly as prices, contracts and efficiency change. Comparing actual costs with driver-based expectations shows whether rates are still accurate.

Keeping the number of drivers small, focused on the ones that matter most, prevents the model from becoming hard to maintain.

Examples of Driver-Based Planning in IT Financial Management

The examples below show driver-based planning in practice.

Both use illustrative figures.

In each, the plan updated automatically when a driver changed, without the need to rebuild the budget by hand.

Planning Workplace Technology

An IT organization plans workplace technology costs at $2,600 per employee a year, covering collaboration licenses, device depreciation and support. With 4,000 employees planned on average, the budget is $10.4 million.

Midway through planning, the company lowers its average headcount plan to 3,700. The workplace technology budget falls to $9.62 million without any manual rework. The same change flows through to service desk staffing and identity management costs, which are also driven by headcount, so the whole IT plan stays consistent with the company's hiring plan.

Planning a Customer Platform

A payments company plans the infrastructure cost of its transaction platform at $0.40 per thousand transactions, plus $1.2 million of fixed costs. With 6 billion transactions forecast, the variable cost is $2.4 million, for a total of $3.6 million.

When the business raises its transaction forecast by 25%, to 7.5 billion, the variable cost rises to $3 million and the platform budget to $4.2 million, and business leaders can see that the increase reflects growth rather than inefficiency. The cost per thousand transactions stays the same, which is the measure the platform team is held to.

Conclusion

Driver-based planning calculates costs from the business activities that cause them, using drivers, rates and fixed costs. It replaces percentage adjustments to last year's budget with a model that explains why costs change.

In IT financial management, driver-based planning links technology costs to business plans, speeds up forecasting and scenario planning, and makes conversations about spending more productive. Focusing on a few significant drivers, agreeing on their sources and keeping rates current help organizations make it work.