Rolling Forecast

A rolling forecast is continuously extended and updated on a fixed cadence (monthly or quarterly) rather than fixed to a calendar year, so finance always has a current view several periods out. A 12-month rolling forecast re-forecast in March covers April through the following March. Re-forecast in April, it moves one period forward again.

How a rolling forecast works

Pick a horizon and a cadence. Common combinations are 12 months rolled monthly, or six quarters rolled quarterly. Each cycle, actuals for the closed period replace the forecast for that period, the horizon extends by one, and the assumptions for the remaining periods get revisited. The forecast is not rebuilt. It is re-run.

That only holds if the model is built on inputs rather than typed values, which is why rolling forecasts pair naturally with driver-based planning. If updating the forecast means editing hundreds of cells, the cadence quietly slips from monthly to quarterly to whenever there is time.

Why teams move off the annual budget

The problem with an annual budget is that its useful life is shortest exactly when decisions matter most. By November, the plan approved the previous December has absorbed a year of drift, and everyone knows it. A rolling forecast keeps a consistent horizon in front of the business, so a hiring decision in Q3 is evaluated against the next four quarters rather than against the stub of a calendar year.

The trade-off is real: rolling forecasts add process load, and they can drift into constant re-forecasting that nobody trusts. Two guardrails help. Keep the budget as the fixed accountability baseline and use the rolling forecast as the operating view. And track forecast accuracy by period, so a forecast that consistently misses in one direction gets corrected rather than repeated.

What good looks like

A healthy rolling forecast closes in days rather than weeks, changes because an assumption changed rather than because someone renegotiated a number, and carries a record of what moved between versions.

Rexfin’s driver-based engine makes each roll a re-run rather than a rebuild: change the drivers for the new period and every dependent line recomputes deterministically, with each actual cited back to its source record.