Build a Driver Based Forecast
This guide explains how to construct a forecast driven by explicit drivers rather than hard coded values. Drivers live in the Data Library and feed variables across the model.
Before you start
Have a view on:
The operational levers that drive the business (units, headcount, conversion, utilisation).
The economic levers (prices, inflation, FX, wage growth, tax rates).
How you want to structure scenarios (for example Base, Downside, Upside).
What you will build
A set of drivers in the Data Library for key assumptions.
Variables that reference those drivers via formulas.
A forecast that responds instantly to driver changes.
Scenario variants that use different driver values.
Steps
Identify your core drivers
Categorise drivers into:
Operational Units sold, customers, active users, capacity, utilisation, headcount.
Economic Prices, wage inflation, CPI, FX, commodity prices, tax rates.
Modifier drivers Growth rates, discount factors, seasonality factors, allocation percentages.
List them explicitly to avoid missing anything important.
Create drivers in the Data Library
Open the Data Library.
For each driver:
Create a new entry with a clear name, for example:
Driver - Units - OnlineDriver - Price - OnlineDriver - Wage Inflation
Set:
Type as Driver or Modifier.
Frequency (usually aligned with model frequency).
Values for each period, either:
Manual entries.
Growth based.
Based on imported series.
Save the entry.
These drivers now act as reusable time series across the model.
Link drivers to variables via formulas
For each variable you want to make driver based:
Open the variable modal.
Switch to formula or driver mode if available.
Build formulas using driver references, for example:
Revenue = Units × PriceCOGS = Units × Cost_per_unitStaff Cost = Headcount × Salary_per_head
Validate:
Check the preview chart or table in the modal.
Confirm the shape and magnitude are correct.
Use modifiers for growth and seasonality
Modifiers help avoid rewriting complex formulas.
Create growth rate drivers:
Driver - Revenue GrowthDriver - Cost Growth
Use these drivers as multipliers:
Revenue in period t = Revenue in period t minus 1 × (1 + growth_rate_t).
For seasonality:
Create a
Seasonalitydriver that sums to 1 across a year.Multiply base levels by the seasonal factor.
This keeps logic consistent and easy to tune.
Build scenario ready drivers
To make driver based forecasts scenario friendly:
Use one model per scenario (Base, Downside, Upside).
In each scenario model:
Start with a copy of the Base model’s Data Library.
Adjust driver values to represent that scenario:
Higher growth in Upside.
Lower growth, higher costs in Downside.
Compare scenario outputs:
Use dashboards to compare revenue, EBITDA, cash and valuation across models.
Check your work
Drivers live in the Data Library with clear names and documented intent.
Variables reference drivers rather than embedding hard coded assumptions.
Updating a driver changes all related variables and outputs.
Different models with different drivers produce logically different scenarios.
Troubleshooting
Related guides
Last updated