Rolling Forecast

Rolling Forecast is a continuously updated financial projection that adds new periods as completed ones drop off, keeping the forecast horizon constant instead of shrinking toward year-end. A rolling forecast keeps the horizon constant, commonly 12 or 18 months, so the planning view never shortens as the fiscal year runs out.

Category: Forecasting SoftwareBest Forecasting Software

It's October. Your annual budget was set last December. Six of the twelve months in it are already history, with actual results that look nothing like the plan. The other six are projections built on assumptions that changed in February. The rolling forecast exists because a static annual budget gets less useful the further you get from the date it was built. A rolling forecast is a planning method in which the forecast horizon extends forward by a fixed period each time a new actual period is added, keeping a constant window into the future instead of anchoring to a fixed fiscal year-end. A 12-month rolling forecast, updated monthly, always shows the next 12 months regardless of where you are in the fiscal calendar. An 18-month rolling forecast updated quarterly always shows the next 18 months. It replaces the annual plan as the main forward-looking document for resource allocation and investor guidance. In most organizations it does not replace the annual budget for compensation or board approval, and that tension is one of the most common implementation problems.

How rolling forecasts work

The mechanics of a rolling forecast are simple: each period, the latest actual results are added to the model, the nearest future period is re-estimated with current information, and the far end of the horizon is extended by one period. A 12-month rolling forecast that runs January through December in January will run February through January after the January close. The forecast never shrinks; it always looks the same distance ahead. The horizon (12, 18, or 24 months) matters because it determines how useful the forecast is for capital allocation. A 12-month horizon is long enough for most operating decisions but short enough to miss the impact of multi-year investments. An 18-month horizon captures enough of the next fiscal year to be useful for annual planning while still working as a current-period decision tool. Update frequency (monthly versus quarterly) matters less than the horizon, because a quarterly update that looks 18 months forward gives more strategic visibility than a monthly update that only covers the next 6 months. Set the horizon by the lead time of the business's biggest resource allocation decisions: capital expenditure cycles, hiring timelines, and contract renewal windows.

Where rolling forecasts create new problems, cadence, grain

Rolling forecasts fix the stale-plan problem but create new operational ones. The first is cadence: if the forecast is updated monthly, finance spends a large share of every month updating a model instead of analyzing it. That is only sustainable if the update process is highly automated and the forecast's level of detail matches the data quality available. Building a monthly rolling forecast at the account-level granularity of an annual budget requires monthly data quality most companies don't have, and the result is a detailed but unreliable model that costs more time to maintain than it's worth. Rolling forecasts that work are usually built at a higher level of aggregation than annual budgets, using drivers rather than account-by-account estimates. The second problem is coexistence with the annual budget. Most organizations keep an annual budget for incentive compensation and board approval even after adopting rolling forecasts for operational planning. That creates two parallel processes, the annual budget cycle and the monthly or quarterly forecast update, and the relationship between them has to be defined explicitly. If the rolling forecast drifts materially from the annual budget and nobody acknowledges it, the forecast loses credibility. If the forecast is adjusted to stay close to the budget, it stops being a forward-looking view and becomes a justification of the plan.

How platforms handle it

FP&A platforms sold for rolling forecasts usually offer version management, driver-based input forms, and automated actuals integration. Adaptive Insights, Planful, Anaplan, and similar tools can manage rolling forecast versions without rebuilding the model each period. The automation claim deserves scrutiny. Actuals integration works well when the chart of accounts is stable and the ERP produces clean data, and both conditions often fail. Driver-based forecasting works well when the business's revenue and cost drivers are well understood and stable, which also changes over time. Before assuming a platform automates the rolling forecast process, ask the vendor to show what happens when an account mapping changes mid-year, what happens when a new product line is added, and how you bring in assumptions that aren't quantifiable drivers. The answers show where manual work is still required.

Evaluation questions for a rolling forecast implementation

What is the longest decision lead time in our business, and does the proposed forecast horizon exceed it?
How will the rolling forecast coexist with the annual budget? Which document governs compensation, and which governs operational decisions?
At what level of granularity will the forecast be built, and does our actuals data quality support that level of detail on a monthly basis?
How will the update process run: what is the expected time from close to updated forecast, and who owns each input?
How will the forecast be communicated to business unit leaders who are accustomed to managing against an annual budget?
What triggers a full model reforecast versus a standard rolling update?

Common rolling forecast failures

The most common failure is running a rolling forecast at too fine a grain for the organization's data quality. A monthly rolling forecast built at the sub-account level needs reliable, granular actuals within days of period close, a standard many mid-market businesses don't meet. The result is a forecast that rolls on paper but is just as stale in practice as the annual budget it replaced, because nobody trusts the inputs. The second failure is confusing 'rolling' with 'updated more often.' Organizations that keep their annual budget model and simply reforecast the remaining months each month have not implemented a rolling forecast. They have implemented a reforecast cadence. The distinction matters because a true rolling forecast always keeps the same future horizon. If the forecast shrinks toward fiscal year-end and then resets to 12 months in January, it never delivered the strategic visibility it was supposed to provide.

Comparing planning platforms

Planning platforms separate on who can maintain the model after go-live, which is a staffing question as much as a software one. Once rolling forecast is settled as a requirement, read the Forecasting Software category guide for how the market splits, then weigh the Anaplan profile against the Pigment profile on that requirement rather than on the feature list. Our Anaplan pricing breakdown records what the vendor publishes and what is quote-based. The Anaplan against Pigment comparison sets two of them side by side on the same criteria. Before you book demos, put your own numbers through the forecasting ROI calculator so the business case is written down before a vendor writes it for you.

Frequently asked questions

How is a rolling forecast different from a revised budget?

A revised budget updates the annual plan to reflect changed expectations but keeps the fixed fiscal year-end as the horizon. A rolling forecast keeps a constant forward window (always 12 or 18 months ahead) regardless of the fiscal calendar. A revised budget looks different in October than in March because October is closer to year-end; a rolling forecast looks the same in October and March because the horizon extends the same distance forward from either date.

Should rolling forecasts replace the annual budget?

In most organizations, no, at least not right away. The annual budget serves purposes that rolling forecasts don't fully cover: board approval, incentive compensation targets, and statutory planning requirements. The more practical approach is to use the rolling forecast as the main operational planning tool and keep the annual budget for governance, with a documented rule for when the rolling forecast overrides the annual budget in resource allocation decisions.

How detailed should a rolling forecast be?

Less detailed than most finance teams first want. Rolling forecasts work best at the level of business drivers (revenue per customer, headcount by department, variable costs as a percentage of revenue) rather than at a budget's account-level granularity. The further out a period is, the less granular the estimates need to be. Many effective rolling forecasts use high detail for the next quarter, medium detail for the following two quarters, and directional estimates beyond that.

Budget vs Actual Variance, Capital Expenditure (CapEx), and Cash Flow Forecasting come up in the same workflow as rolling forecast, and the rest of the planning platforms cluster is indexed in the finance operations glossary.