What is driver-based planning?
Driver-based planning is an approach to budgeting and forecasting in which financial outcomes — revenue, cost, margin — are derived from operational assumptions. The "drivers" are the business activities and external conditions that cause the financials to move: volume, price, headcount, utilisation rate, conversion rate, yield.
Rather than entering a revenue number directly into the budget, a driver-based model derives it: revenue = volume × average selling price. Rather than entering a salary cost, it derives it: salary cost = headcount × average salary. Every financial line has an explicit, auditable cause — which makes the model both transparent and fast to update when assumptions change.
Why traditional line-item budgets fail
In a conventional line-item budget, each account has a number entered directly — typically derived from last year's actuals with a percentage adjustment applied. This approach has three fundamental weaknesses that compound as the business grows more complex.
No logic, no explanation
When revenue misses plan by £500k, the line-item budget contains no explanation of why the planned number was right in the first place — so variance analysis becomes forensic archaeology rather than management insight.
Inflexible to update
Updating a line-item model requires revising every affected line manually. In a driver-based model, changing one assumption propagates through the entire P&L automatically.
Disconnected from operations
The people who know what will actually drive revenue and cost — sales leaders, operations managers, HR directors — have no connection point to a line-item model. Driver-based models give them a home.
Guesswork at year-end
When the model has no explicit assumptions, next year's budget is built by staring at this year's actuals and making educated guesses. Driver-based models make next year's budget a disciplined update of explicit assumptions.
Identifying the right drivers for your business
The most important step in driver-based planning is identifying the right drivers — the 10–15 variables that explain 80% of the movement in the P&L. More complexity is added only when the business genuinely needs it. Starting with too many drivers produces a model that is technically sophisticated but practically unmaintainable.
Driver sets vary by business model. For a B2B professional services firm: consultant headcount, average utilisation rate, and average day rate. For a SaaS business: ARR, net revenue retention, and new logo bookings. For a manufacturer: production volume, yield rate, and input cost per unit. For a retail network: store count, average transaction value, and transactions per store per week.
The test of a good driver is whether someone in the business is already tracking it, already accountable for it, and already taking decisions that move it. If the driver is not connected to a management decision, it is a metric — not a driver.
How a driver model connects to rolling forecasts and scenario planning
Driver-based planning is the prerequisite for both rolling forecasts and scenario planning. Without a driver-based model, rolling the forecast forward requires rebuilding the numbers manually every month. With a driver-based model, rolling the forecast means updating the driver assumptions — and all financial outputs update automatically.
Scenario planning is also only meaningful with a driver-based structure. When you build a downside scenario by entering a lower revenue number directly, you get a result without a mechanism. When you build it by reducing volume and price drivers, you model a coherent business reality — and you can connect that financial outcome to the operational response the business would need to make.
The Metapraxis approach to driver-based models
- Start with the minimum viable driver set — the variables that explain most of the P&L movement
- Make every assumption explicit and visible — no black-box formulas
- Connect operational owners to their drivers — so the people closest to the business update the inputs
- Build scenario switching in from the start — not as an afterthought
- Produce board-ready outputs automatically — not through manual formatting
Building your driver model with Metapraxis
Metapraxis Empower is built around driver-based modelling. The platform makes driver hierarchies transparent, assumption sets auditable, and scenario switching effortless. Our FP&A as a Service engagements always begin with driver identification — working with your leadership team to map the business logic before a single number enters the model.
Most driver-based model implementations take 4–8 weeks from driver identification to a working model producing board-ready outputs. The resulting model becomes the foundation for your rolling forecast, your scenario planning, and your board reporting — all built on the same, consistent set of assumptions.
Want to go deeper? See our complete guide to driver-based forecasting — including a step-by-step model build tutorial and common mistakes to avoid.
Frequently asked questions
What is driver-based planning? +
Driver-based planning is a financial planning methodology in which all financial outcomes — revenue, costs, margin, cash flow — are derived from explicit operational assumptions called drivers. When a driver changes (headcount, volume, price, utilisation), every related financial line updates automatically through the model logic. It replaces line-item budgeting with cause-and-effect modelling.
How is driver-based planning different from traditional budgeting? +
Traditional budgeting works from line-item history — last year's spend plus a percentage adjustment. Driver-based planning works from cause and effect — the operational activities that create costs and revenues. Driver-based plans are faster to update, more transparent about assumptions, and more useful for scenario planning.
What are examples of business drivers in FP&A? +
Common drivers include: revenue drivers (units sold, average selling price, customer count, conversion rate), cost drivers (headcount, utilisation rate, cost per unit, occupancy), and operational drivers (locations, production runs, square footage). The right drivers are the ones that explain most of your financial variance and are connected to management decisions.
How long does it take to build a driver-based model? +
Most Metapraxis driver model implementations take 4–8 weeks from the initial driver workshop to a working model producing board-ready outputs. The timeline depends on data complexity, the number of business units, and the quality of existing source systems. See our complete driver-based forecasting guide for a step-by-step process.
