Forecast Driver
Executive Summary
Key Takeaways
- ✓ A forecast driver is a labelled input cell that a forecast formula references, such as a growth rate, a margin percentage, a unit count, or a price.
- ✓ It is structurally distinct from a hardcode, a value typed directly into a calculation cell with no traceable source, even when the two values are identical.
- ✓ A driver-based formula responds automatically and consistently when the driver cell changes; a hardcoded formula does not respond at all.
- ✓ Forecast drivers belong on a dedicated, clearly labelled assumptions tab, with units and a documented basis, not scattered inside individual calculation formulas.
- ✓ A structural audit can detect where a driver is missing, unused, or has been overridden by a typed value, but cannot assess whether the driver's own assumed value is commercially reasonable.
Definition¶
A forecast driver is a labelled input cell that a forecast formula references, rather than a value typed directly into the formula itself. Common examples include a revenue growth rate, a gross margin percentage, a unit volume, a unit price, a headcount count, or a retention rate. A forecast driver is typically located on a dedicated assumptions tab or block, clearly labelled with its units and, ideally, a stated basis or source for the assumed value.
A forecast driver is structurally distinct from a hardcode, a value typed directly into a calculation cell with no traceable source. The distinction is not about the number itself — a driver cell and a hardcode can hold an identical numeric value in a given period — but about traceability and responsiveness: a formula that references a driver cell updates automatically and consistently when that driver's value changes; a formula containing a typed value does not respond to anything.
Why It Matters¶
Nearly every forecast line in a financial model ultimately depends on a small number of driver assumptions — a growth rate, a margin, a price, a volume. Whether those assumptions are structured as labelled, referenced driver cells or buried as typed values inside individual formulas determines whether the forecast can actually be audited, sensitized, or defended in front of a reviewer.
A driver-based forecast makes three things possible that a forecast built on scattered hardcodes does not: a reader can identify, at a glance, every assumption behind a given output; a single driver change propagates consistently to every dependent calculation; and a scenario or sensitivity exercise can be run by changing a small number of driver cells rather than hunting through the model for every place a value was typed in directly. See Financial Forecasting in Financial Models for how driver design fits into the broader forecasting discipline.
Technical Background¶
Driver vs Hardcode, Structurally¶
Driver-based: =Prior_Period_Revenue * (1 + Assumptions!Growth_Rate)
Hardcoded: =Prior_Period_Revenue * 1.05
Both formulas produce the same output in the period shown. They are not equivalent as model structures. In the driver-based version, changing the value in Assumptions!Growth_Rate updates the output automatically, and the same cell reference can be reused consistently across every period column and, where relevant, across a scenario switch. In the hardcoded version, the 1.05 must be located and manually edited wherever it appears, with no guarantee every occurrence is found and updated consistently.
Where Drivers Belong¶
A driver's location in the model, not just its presence, affects auditability. A driver cell that sits on a dedicated, clearly labelled assumptions tab, with its unit stated and its basis documented, is materially more useful to a reader than the same value entered as an unlabelled input buried inside a calculation worksheet. See Assumption Design Best Practices for the full treatment of assumptions-tab design.
Drivers Across Forecasting Methods¶
The specific drivers used vary by forecasting method. A top-down revenue forecast is typically driven by a market-size figure and an assumed share; a bottom-up forecast by a unit volume and a unit price; a cost forecast by a headcount schedule or a cost ratio. See Forecast Methodologies Overview and Revenue Forecasting Methods for how driver selection maps onto method choice.
Driver Consistency Across Periods¶
A structurally sound forecast references its drivers consistently across every period column — the same driver cell, or the corresponding period's driver value where the driver itself varies by period, rather than a formula pattern that silently changes source partway through the forecast. This consistency is what allows a reader to scan a forecast row and confirm its logic without checking every individual cell.
Common Errors¶
| Error | Description | Risk |
|---|---|---|
| Growth rate or margin typed directly into a forecast formula | No labelled driver cell behind the assumption | Formula does not respond when the model's stated assumptions change |
| Driver cell present but not referenced by the live formula | Formula still contains a typed value alongside an unused driver cell | Assumptions tab misleadingly implies the model is driver-based when it is not |
| Driver value repeated by typing rather than referencing across periods | Same assumption re-typed in each period column instead of referenced once | Updating the assumption in one period does not propagate to the others |
| Undocumented driver | Driver cell has no stated unit or basis | Reader cannot assess whether the assumed value is reasonable |
| Driver orphaned after a model revision | Assumptions-tab cell no longer referenced by any live formula | Assumptions tab no longer reflects what the model actually calculates from |
Best Practices¶
Reference every forecast assumption from a single, labelled driver cell on a dedicated assumptions tab, rather than typing the value directly into the calculation formula. State the unit and, where practical, the basis for each driver alongside the cell itself. Apply each driver consistently across every period column and, where a scenario structure exists, through the same switch cell mechanism used elsewhere in the model. Periodically confirm that every driver cell on the assumptions tab is still referenced by a live formula, and that no formula has reverted to a typed value during a later revision.
Continue Reading¶
Prerequisites¶
- Financial Forecasting in Financial Models — the parent pillar
Related Glossary¶
Related Technical Guides¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
What is a forecast driver?
A labelled input cell, typically found on a dedicated assumptions tab, that a forecast formula references — a growth rate, a margin percentage, a unit count, or a price per unit. The formula reads the driver's value rather than containing that value typed directly inside it.
What is the difference between a forecast driver and a hardcode?
A forecast driver is a labelled, traceable input cell that a formula references. A hardcode, described on the Hardcode glossary entry, is a value typed directly into a calculation formula with no traceable source. The two can hold an identical numeric value in a given period and still be structurally different, because only the driver responds when the model's stated assumptions change.
Where should forecast drivers be located in a model?
On a dedicated, clearly labelled assumptions tab or block, separate from the calculation layer that references them, with units stated and a documented basis or source for each value, described further on the Assumption Design Best Practices guide.
Can a forecast driver be a formula rather than a typed value?
Yes. A driver can itself be calculated, for example a blended growth rate derived from sub-component assumptions, provided it remains on the assumptions layer and is referenced, rather than re-typed, by every downstream calculation formula that depends on it.
Why does it matter whether a growth rate is a driver or a hardcode?
Because a driver-based formula updates every dependent calculation automatically and consistently when the driver's value changes, while a hardcoded formula does not respond at all — the model's output silently stops reflecting its own stated assumptions, which is one of the most common structural failure modes a model audit is built to detect.
How does a structural audit test forecast drivers?
A structural audit can confirm whether a forecast calculation references a driver cell rather than containing a typed value, whether a dedicated assumptions tab exists, and whether a driver cell on that tab is actually referenced by any live formula. It cannot assess whether the specific value chosen for a driver, such as the assumed growth rate itself, is commercially reasonable.
What kinds of values are typically forecast drivers?
A growth rate, a margin or cost ratio, a unit price, a unit volume, a headcount count, a retention rate, and a discount rate are all common examples of forecast drivers across different parts of a financial model.
Related Articles
Financial Forecasting in Financial Models
Financial forecasting is the process of projecting a business's future financial performance from a defined set of operating drivers and assumptions, structured so that every forecast line traces back to a labelled, auditable input rather than a value typed directly into a calculation. It underpins every model built for valuation, budgeting, financing, or investment decision-making, and it is also one of the areas of a financial model most prone to silent structural failure, since a forecast that looks complete can still rest on drivers that are hardcoded, undocumented, or inconsistently applied from one period to the next. This page is the hub for the Knowledge Centre's forecasting content: what a forecast driver is, the major forecasting methodologies and when each applies, the governance distinction between a budget and a forecast, rolling forecasts, and how forecasting failure modes map onto FMAE's existing structural audit rule taxonomy.
Hardcode
A hardcode is a typed value, a number, date, or rate, entered directly into a formula cell rather than derived from a reference to an assumptions tab or another calculated cell. It is one of the most common and most consequential structural risks in Excel financial models, because a hardcoded value does not update when the model's stated assumptions change, silently disconnecting the model's output from its own inputs.
Assumption Design Best Practices
How a forecast's assumptions are designed determines whether the forecast can actually be audited, sensitized, and defended in front of a reviewer, independent of whether the assumed values themselves are reasonable. This guide sets out five construction disciplines for assumption design: separating input cells from calculation formulas, labelling every assumption clearly with its unit, consolidating assumptions onto a dedicated tab, entering each driver once at a single point rather than repeating it, and structuring input cells so they can be sensitized cleanly without breaking the calculations that depend on them.
Forecast Methodologies Overview
Before a forecast line is built, a methodology has to be chosen for how it will be projected. This guide compares the four principal forecasting methodologies used across a financial model's revenue and cost lines: top-down forecasting, which starts from a macro or market-level figure and works down; bottom-up forecasting, which builds up from granular unit economics; driver-based forecasting, which structures the model around a defined set of operating drivers regardless of direction; and the percent-of-sales method, which forecasts a line as a constant ratio of revenue. It sets out how the four relate to each other, when each is most defensible, and how they are applied to the revenue and cost sides of a forecast.
Revenue Forecasting Methods
Revenue can be forecast using several structurally different methods, and the choice of method has a direct effect on how defensible and auditable the resulting forecast is. This guide sets out the four principal methods used in institutional financial models — top-down forecasting from market size and share, bottom-up forecasting from unit economics, trend and growth-rate extrapolation from historical results, and cohort-based forecasting for subscription and other recurring-revenue businesses — with guidance on when each method is appropriate and how the methods can be combined within a single forecast.