Concourse Series A — read the announcement
Finance Automation

Rolling Forecast: What It Is and How to Build One

A rolling forecast continuously projects a fixed number of periods ahead, re-forecast every month or quarter, instead of a static annual budget that drifts. Here is what a rolling forecast is, how it differs from a budget, how to build one, and where AI fits.

Logan Hine
Logan Hine
Growth
Published September 29, 2026 · 9 min read
Concourse "Rolling Forecast" cover graphic: the Concourse wordmark and title in white on a dark background.

Most finance teams build a budget once a year, then spend the next twelve months watching reality drift away from it. By Q3 the plan set last fall bears little resemblance to the business, and decisions get made against numbers everyone quietly knows are stale. The rolling forecast is the fix: instead of forecasting to a fixed year-end, you continuously project a set number of periods ahead and refresh the numbers every month or quarter, so the forecast always reflects where the business actually is.

This guide explains what a rolling forecast is, how it differs from a traditional budget, why teams adopt it, how to build one without drowning in manual work, and where AI agents change the economics of keeping it current.

What is a rolling forecast?

A rolling forecast is a forecast that always looks a constant number of periods into the future, adding a new period as each one closes, so the horizon "rolls" forward. If you run a 12-month rolling forecast, then at the end of January you drop January and add the following January, always keeping twelve months of forward view. Common horizons are 12, 18, or 24 months, re-forecast monthly or quarterly.

A traditional budget answers "how will we do against the plan we set for this fiscal year?" A rolling forecast answers "given what we know today, where are we headed over the next N months?" One is a fixed target; the other is a living view that never runs out of runway.

Rolling forecast vs. static budget

A rolling forecast does not necessarily replace the annual budget; many teams keep the budget as the fixed accountability target and run a rolling forecast alongside it for decision-making. The difference is in what each is for.

DimensionStatic annual budgetRolling forecast
HorizonFixed to fiscal year-endConstant window (e.g. next 12 months)
FrequencySet once, revised rarelyRe-forecast monthly or quarterly
PurposeAccountability targetForward-looking decision-making
Late in the yearLittle runway left to plan againstAlways a full horizon ahead
Reflects realityDrifts as the year progressesUpdated with the latest actuals

Why use a rolling forecast?

  • It stays current. Because it refreshes with each period's actuals, the forecast reflects the business as it is now, not as it looked when the budget was set.
  • It never runs out of runway. You always have a full planning horizon ahead, instead of a shrinking view as year-end approaches.
  • It supports faster decisions. A living forecast makes it easy to answer "what happens if" as conditions change, rather than waiting for the next annual cycle.
  • It catches problems earlier. Continuous re-forecasting surfaces variances and trend changes while there is still time to act.
  • It reduces the annual-budget scramble. When forecasting is continuous, the once-a-year planning marathon gets lighter.

How to build a rolling forecast

The mechanics are straightforward; the discipline is in keeping it lean enough to sustain.

1. Set the horizon and cadence

Decide how far ahead to forecast (12 and 18 months are common) and how often to refresh (monthly or quarterly). Match both to how fast your business moves; a volatile business benefits from a longer horizon and a monthly cadence.

2. Forecast on drivers, not every line

Build the forecast from the key drivers that actually move the numbers, headcount, pipeline, units, price, rather than trying to project every GL account. Driver-based forecasting is what keeps a rolling forecast maintainable; if re-forecasting means rebuilding hundreds of line items each month, no team will keep it up.

3. Connect actuals

Wire the forecast to your source systems, ERP, data warehouse, billing, so each period's actuals flow in automatically. The value of a rolling forecast collapses if refreshing it means manually re-keying actuals every month.

4. Re-forecast and review

Each cycle, roll the window forward, update the drivers, and review the forecast against the budget and the prior forecast. Focus the review on what changed and why, the variance and the story behind it, not on re-deriving the whole model.

Common rolling forecast mistakes

  • Too much detail. Forecasting every line item makes the process unsustainable. Keep it driver-based.
  • Manual data pulls. If refreshing means hand-collecting actuals, the cadence will slip. Automate the data flow.
  • Treating it like a second budget. A rolling forecast is a best-current-estimate, not a target to negotiate. Keep it honest.
  • No link to action. A forecast no one acts on is wasted effort. Tie it to decisions, hiring, spend, cash.

Rolling forecast software and tools

The reason many teams struggle to sustain a rolling forecast is effort: done in spreadsheets, it means pulling actuals, rebuilding models, and reconciling versions every single cycle. Dedicated FP&A and forecasting platforms reduce that by connecting to source data and automating the refresh; see our guide to the best financial forecasting software for the options. The newest approach removes even more of the manual work by having AI agents produce and refresh the forecast directly.

Where AI agents fit

A rolling forecast is, by definition, recurring work: the same re-forecast, every period, forever. That is exactly the profile AI agents handle well. Instead of an analyst rebuilding the model each month, an agent connects to your systems, pulls the latest actuals, refreshes the drivers, rolls the window forward, and produces the updated forecast and the variance story, with a human reviewing and approving.

The hardest part of a rolling forecast is not the concept; it is sustaining the cadence. AI agents change that, because refreshing the forecast every month stops being a project and becomes something that just happens, with every number traceable back to source.

That is how Concourse approaches it: agents that build and refresh forecasts from your live data, so a rolling forecast stays current without an analyst driving each cycle. See how it works across FP&A workflows.

Frequently asked questions

What is a rolling forecast?

A rolling forecast is a forecast that always projects a constant number of periods into the future, adding a new period as each one closes so the horizon continuously rolls forward. It is refreshed monthly or quarterly with the latest actuals, so it always reflects the current state of the business rather than a fixed year-end plan.

What is the difference between a rolling forecast and a budget?

A budget is a fixed annual target set once and held as an accountability benchmark. A rolling forecast is a living, best-current-estimate that always looks a set horizon ahead and updates each period. Many teams run both: the budget as the target and the rolling forecast for decision-making.

How far ahead should a rolling forecast go?

Common horizons are 12, 18, or 24 months, chosen to match how far ahead your business needs to make decisions and how predictable it is. A fast-moving business often uses a longer horizon with a monthly refresh; a stable one may use 12 months refreshed quarterly.

How often should you update a rolling forecast?

Most teams re-forecast monthly or quarterly. Monthly gives the most current view but requires the refresh to be efficient, which is why connecting actuals automatically, or using AI agents to produce the update, makes a monthly cadence sustainable.

The bottom line

A rolling forecast keeps finance looking forward with a view that never goes stale, updated each period with real actuals instead of drifting from a plan set a year ago. The concept is simple; the challenge is sustaining the cadence without burning out the team, which is why driver-based models, connected data, and increasingly AI agents are what make it work in practice.

If you want a rolling forecast that refreshes itself, built and updated by AI agents from your live data, with every number traceable to source, talk to our team and put an agent on your next forecast cycle.

Built for the teams that can’t afford to get it wrong