The rolling forecast vs annual budget decision is not binary — most mature mid-market organisations achieve the best results with a hybrid model that preserves the annual budget for accountability, target-setting, and board governance while layering a rolling forecast for continuous forward visibility. AFP reports 42% adoption of rolling forecasts, yet Deloitte finds only 25% actual sustained use, confirming that most companies are mid-transition rather than fully converted. Rolling forecasts must be structurally simpler than the annual budget — driver-based models with fewer line items updated monthly or quarterly — otherwise the process collapses under its own weight. The practical path is to streamline the annual budget first to free capacity, introduce the rolling forecast alongside it, and evolve the balance as forecast credibility builds with stakeholders.
The board expects an annual budget . The CFO knows the budget is disconnected from reality by Q2. Operations wants a view that reflects what is actually happening. The finance team barely has capacity to maintain the annual budget, let alone add another planning process on top.
This tension is real in every mid-market company that has outgrown the usefulness of a static annual plan but has not yet adopted a rolling forecast . The question finance leaders most often ask is not “what is a rolling forecast?” — it is “how do I add a rolling forecast when the board still wants an annual budget and I don’t have more time?”
The answer, for most organisations, is neither replacement nor addition. It is redesign: simplify the annual budget to free capacity, layer a rolling forecast alongside it, and evolve the balance as credibility builds.
Two Instruments, Different Purposes
The annual budget and the rolling forecast answer different questions. Treating them as competitors misframes the decision.
| Dimension | Annual budget | Rolling forecast |
|---|---|---|
| Core question | “What are we committing to achieve?” | “What do we now expect will happen?” |
| Horizon | Fiscal year-end (fixed, shrinking) | 12–18 months ahead (constant, rolling) |
| Update cadence | Annual (with occasional reforecasts) | Monthly or quarterly |
| Granularity | High — line-item, cost centre, department | Medium — key drivers, top-level P&L and cash |
| Governance role | Target-setting, resource allocation, bonus benchmarks | Expectation management, early warning, decision readiness |
| Stakeholder audience | Board, investors, department heads | Management team, operational leaders |
| What happens when assumptions change | Budget becomes a historical reference point | Forecast updates to reflect current reality |
The budget says: “Here is what we planned.” The forecast says: “Here is where we are actually heading.” Variance analysis connects the two — explaining why the trajectory differs from the target and whether the difference requires action.
Neither instrument is sufficient alone. A budget without a forecast leaves the organisation blind between planning cycles. A forecast without a budget removes the accountability structure — targets, bonus benchmarks, resource commitments — that governance requires.
Why the Binary Framing Wastes Organisational Energy
Most companies approach the rolling forecast question as a replacement decision: “Should we replace the annual budget with a rolling forecast?” This framing creates unnecessary resistance and misses the pragmatic answer.
The annual budget serves functions that rolling forecasts do not naturally replace. Bonus targets need a fixed reference point. Board governance typically requires an approved annual plan. Resource allocation decisions — headcount authorisation, capex approvals — need a baseline that does not change every month. Removing the budget without addressing these needs creates a governance vacuum that organisational culture will not tolerate.
Rolling forecasts serve functions that the annual budget cannot. A budget approved in November becomes progressively disconnected from reality as the year unfolds. Deloitte research confirms that roughly 75% of organisations report their annual budget is significantly disconnected from actual business conditions by mid-year. A rolling forecast maintains a current forward view that the budget, by design, cannot.
The adoption data confirms hybrid dominance. AFP surveys report 42% rolling forecast adoption among larger organisations. Deloitte finds only about 25% actually use rolling forecasts as a primary planning instrument. The gap between these numbers tells the story: most organisations that adopt rolling forecasts do so alongside the annual budget, not instead of it.
When the Annual Budget Is Sufficient
Not every organisation needs a rolling forecast immediately. The annual budget is sufficient when:
- The business operates in a stable, predictable market with low revenue volatility
- The business model is simple, with few revenue streams and well-understood cost structures
- The annual planning cycle is short (less than eight weeks) and the budget remains relevant through mid-year
- Management decisions are primarily backward-looking — reacting to variance rather than anticipating change
If these conditions hold, the improvement priority is better variance analysis and structured reforecasting, not a rolling forecast.
When Rolling Forecasts Add Measurable Value
A rolling forecast adds value when:
- Revenue is volatile or seasonal, and assumptions shift materially within the fiscal year
- The business is growing rapidly or contracting, making the annual budget stale within months
- Management makes resource decisions (hiring, investment, capacity) on a quarterly or monthly basis
- The board or investors expect continuous visibility, not just annual updates
- The company operates in multiple markets or segments where conditions evolve at different speeds
McKinsey research identifies rolling forecast adoption as the single best predictor of CFO satisfaction with the planning process. The reason is straightforward: rolling forecasts keep the forward view current, which means management decisions are based on current expectations rather than historical assumptions.
Three Hybrid Model Designs
The question is not “budget or forecast?” but “what combination serves our decision-making needs?” Three hybrid models cover most mid-market situations:
Model A: Annual budget + quarterly rolling forecast
How it works. The annual budget is produced as usual — full detail, line-item, department-level. Each quarter, a simplified rolling forecast updates the 12-month forward view using five to ten key drivers . The budget remains the governance instrument. The forecast provides continuous visibility.
Best for. Companies starting the transition. The annual budget process does not change. The rolling forecast is layered on top with minimal additional effort because it operates at driver level, not line-item level.
Effort. Two to three days per quarter for the rolling forecast update. The annual budget process continues unchanged.
Model B: Streamlined annual budget + monthly rolling forecast
How it works. The annual budget is simplified — fewer line items, driver-based structure, shorter cycle time. The monthly rolling forecast provides the detailed forward view. Budget and forecast use the same driver model, reducing duplication.
Best for. Companies ready to shift effort from the budget to the forecast. The annual budget becomes a target-setting exercise (four to six weeks instead of twelve). The monthly forecast becomes the primary decision instrument.
Effort. One to two days per month for the rolling forecast. The annual budget cycle is shortened by 40–60%.
Model C: Rolling forecast with annual target extract
How it works. The rolling forecast is the primary planning instrument, updated monthly. Once a year, a snapshot of the rolling forecast is extracted, adjusted for targets and stretch goals, and presented to the board as the annual plan. The budget is derived from the forecast, not built separately.
Best for. Companies with mature forecasting capability, board openness to continuous planning, and a business model that changes rapidly. This is the closest to “pure rolling forecast” while maintaining the annual governance requirement.
Effort. The rolling forecast absorbs most of the effort formerly spent on budgeting. The annual target extract is a two-week exercise, not a three-month process.
Choosing a model
| Decision factor | Model A | Model B | Model C |
|---|---|---|---|
| Current maturity | Level 2–3 (static budget) | Level 3–4 (budget with reforecasts) | Level 4–5 (established rolling forecast) |
| Board flexibility | Board expects traditional budget | Board open to streamlined budget | Board accepts forecast-derived targets |
| Finance team capacity | Minimal spare capacity | Some capacity freed from budget simplification | Forecasting is the primary planning activity |
| Business volatility | Moderate | High | Very high or rapid growth |
The Transition Roadmap
Moving from a pure annual budget to a hybrid model follows a predictable sequence:
Phase 1 — Add without changing (3–6 months). Produce the annual budget as normal. Add a quarterly rolling forecast at driver level (five to ten drivers, top-level P&L). Run both processes in parallel. Use the forecast internally for decision discussions; use the budget for board governance. This phase builds credibility without disrupting existing processes.
Phase 2 — Simplify the budget (next annual cycle). Reduce budget granularity. Move from 500 line items to 50–100. Use driver-based structure for the budget itself. Shorten the budget cycle by four to six weeks. Redirect the freed capacity to the rolling forecast.
Phase 3 — Shift the centre of gravity (12–18 months). Make the rolling forecast the primary discussion document in management meetings. Use the budget for target-setting and governance only. Increase forecast cadence to monthly if capacity permits. Begin reporting forecast accuracy alongside budget variance.
Phase 4 — Evolve the governance model (18–24 months). Explore whether the board accepts a forecast-derived annual plan (Model C). Align bonus structures to a combination of budget targets and forecast accuracy. Integrate scenario analysis into the rolling forecast process.
The timeline varies. Some organisations move from Phase 1 to Phase 3 in twelve months. Others spend two years in Phase 2. The key constraint is not technical — it is cultural. The annual budget is deeply embedded in management routines, compensation structures, and board expectations. Moving too fast creates resistance. Moving deliberately builds trust.
The Zero-Sum Time Equation
Every mid-market finance leader faces the same constraint: there is no spare capacity. Adding a rolling forecast without reducing something else means the forecast either fails or the team burns out.
The practical answer is the “simplify the budget to fund the forecast” principle. Time invested in the rolling forecast must come from time saved on the annual budget. This is achieved through:
- Fewer line items. Budget at driver level rather than general ledger level. Fifty lines updated thoughtfully are more useful than 500 lines extrapolated from last year.
- Shorter cycle. A driver-based budget can be completed in four to six weeks instead of ten to twelve. The saved weeks fund the rolling forecast cadence.
- Shared model. When the budget and forecast use the same driver model, maintaining both is not double the effort. The annual budget sets the driver targets. The rolling forecast updates the driver assumptions.
Common Pitfalls
Implementing rolling forecasts with budget-level granularity
The 500-line annual budget cannot be updated monthly. Attempting to do so collapses under the weight of data collection, validation, and consolidation. The rolling forecast must be simpler — five to fifteen drivers, not hundreds of line items. Simplification is not a compromise; it is a design requirement.
Removing the budget before establishing forecast credibility
Stakeholders need evidence that the new process produces useful forward views before the old process is retired. Running both in parallel for two to four quarters builds this evidence. Removing the budget in quarter one, before anyone trusts the forecast, triggers governance anxiety and political resistance.
Automating the wrong process
Acquiring a planning tool and automating the existing annual budget process does not create a rolling forecast. It creates a faster version of the same exercise. Process design precedes technology. The methodology — drivers, cadence, governance — must be defined before any tool is configured.
Presenting rolling forecasts as “replacing the budget”
This framing triggers resistance in every organisation where the budget is tied to compensation, governance, or board reporting. The effective framing is: “adding continuous visibility while streamlining the budget to reduce total effort.” The end state may be budget replacement, but the opening message must be budget evolution.
Ignoring the cultural dimension
The annual budget is not just a financial document. It is a management ritual — target negotiation, resource bargaining, commitment-making. Removing it without addressing these cultural functions creates a vacuum. The hybrid model preserves the ritual (annual target-setting) while adding the capability (continuous forward view).
Frequently Asked Questions
Does the board need to approve the rolling forecast? Not in most governance structures. The annual budget is the board-approved plan. The rolling forecast is a management instrument that shows current expectations. It can be presented to the board as information — “here is where we expect to land relative to the approved plan” — without requiring formal approval each cycle.
How do we handle bonuses if we move away from the annual budget? Keep bonus targets anchored to the annual budget or to specific KPIs that are set annually. The rolling forecast provides the expectation of whether targets will be met, but it does not replace the target itself. Some organisations introduce forecast accuracy as a supplementary metric — rewarding accurate forecasting alongside target achievement.
Can we start with a rolling forecast and skip the annual budget entirely? In theory, yes. In practice, very few mid-market organisations do this successfully. The annual budget provides a governance structure that most boards, investors, and management teams expect. Starting with a hybrid model (Model A) is lower risk and higher adoption probability.
What if we forecast quarterly but the business changes monthly? Quarterly cadence is a starting point, not a ceiling. If the business is volatile enough that quarterly forecasts are stale within weeks, move to monthly. But monthly cadence requires a simpler model — five to ten drivers, not fifty line items — to be sustainable.
How long before we see accuracy improvements from adding a rolling forecast? Aberdeen research reports a 14% improvement in revenue forecast accuracy with rolling forecast adoption. Most organisations see measurable accuracy improvement within three to four forecast cycles — enough time for the feedback loop (forecast → actuals → error analysis → adjustment) to produce results.
Related Reading
- Rolling Forecast — How to Implement Continuous Planning — the detailed implementation guide for rolling forecast processes
- How to Build an Annual Budget That Works — the target-setting framework that the hybrid model retains
- Building a Decision-Grade Forecast — the next maturity step beyond the hybrid model
- Variance Analysis — A Practical Guide — the analytical bridge between budget targets and forecast expectations
- Glossary: Rolling Forecast | Budget | Forecast Accuracy
Sources
- AFP — Rolling Forecast Adoption Survey — 42% enterprise adoption; mid-market adoption significantly lower
- Deloitte UK — Planning, Budgeting and Forecasting Survey — approximately 25% actual rolling forecast use; 75% of budgets disconnected from reality by mid-year
- McKinsey — Forecasting Best Practices — rolling forecast adoption as the single best predictor of CFO satisfaction
- Aberdeen — Driver-Based Planning Research — 14% improvement in revenue forecast accuracy with rolling forecast adoption
Martin Duben is managing director at Onetribe, where he works with mid-market finance teams on planning, forecasting, and performance analysis. He has spent over fifteen years helping companies design planning architectures that balance governance rigour with operational agility.