Rolling forecast vs annual budget: the plan you approved in January is already out of date

Every annual budget is wrong by March. Not because it was built badly, but because the business it describes will not sit still.

A customer churns in February. A hire slips to May. A supplier raises prices in the summer. The plan carries on describing a year that stopped happening, and by September it has become a document everyone reports against and nobody quite believes.

A rolling forecast is the fix. Not a replacement for the budget, but an answer to its one built-in flaw: a budget cannot move.

Budget or forecast: what each is actually for

An annual budget is a fixed plan for the financial year. Built once, usually from last year's numbers plus a growth assumption, then locked. It sets the targets, frames the board conversation, and gives everyone a line to be measured against. Its job is governance, and it is good at it.

A rolling forecast is a live view of that same future that never stops the same distance ahead. As each month closes, the actual result replaces the forecast for that month and a new month is added at the far end, so the horizon keeps sliding forward. A twelve-month rolling forecast in March looks at April through the following March. In April it looks at May through the April after. The window never shrinks.

That single mechanical difference is the whole argument.

The horizon problem nobody mentions

A budget's forward view collapses as the year runs. In January it sees twelve months. By September, three. By December, almost nothing, right at the point you are trying to plan the next year. The tool you lean on to look ahead has the least to say exactly when you need it most.

A rolling forecast holds a constant forward view because it refuses to stop at the year end. December is not a cliff edge, just another month where actuals land and a fresh month appears. You are always looking roughly the same distance ahead, which is the difference between steering and reacting.

You do not have to choose

"Budget versus forecast" sounds like a decision. In practice, almost nobody picks a side.

Around 40% of finance teams run a rolling forecast. Most of them keep the annual budget too.

The two answer different questions. The budget answers what you committed to. The forecast answers where you are actually heading. Throw the budget away and you lose your accountability frame. Keep only the budget and you are flying on instruments that stopped updating in the first quarter. The mature setup runs both, and is clear about which question each one is there to answer.

What makes a rolling forecast actually work

Adopting one is easy. Sustaining it is where most attempts fall over, and the failure is nearly always the same. A team tries to run its three-hundred-line annual budget every single month. The refresh takes the best part of a week. Nobody has a week. Within a quarter, the rolling forecast has quietly stopped rolling.

The forecast has to be lighter than the budget by design: fewer line items, and a model built on drivers rather than hand-keyed cells, so a refresh is a data update, not a rebuild. Get the handful of things that genuinely move the numbers right, headcount, pricing, volume and collection timing, and let the rest follow. We made the driver-based case in full in Know the number, and know why it moved. A forecast you can refresh in an afternoon survives. One that needs a full re-key does not.

Where Dash AI fits

This is the problem Dash AI is built around, and it is worth being specific rather than claiming it does everything.

Actuals arrive on their own. Dash connects to Xero, QuickBooks or Sage, so each period's real numbers flow into the model without an export and paste. The "actualise and roll forward" step that makes rolling forecasts heavy is the part that happens automatically.

The model is driver-based by design. Because the structure sits on the drivers rather than a wall of static cells, extending the horizon or changing an assumption is a tweak to a few inputs, not a rebuild of the sheet.

One live forward view, not twelve saved versions. The forecast rolls in place. No folder of near-identical monthly spreadsheets to reconcile, which is usually where the discipline dies.

None of this decides your assumptions for you. Choosing the growth rate, sense-checking the shape and having the conversation about what to do remain the job, and remain the part worth charging for. What changes is that keeping the forward view alive stops eating the week.

The honest version

A rolling forecast will not save a business that has not decided what it is forecasting for. If the numbers never drive a decision, updating them more often just produces a fresher report nobody reads. And if your chart of accounts has never been mapped properly, rolling it forward every month gives you output that is consistently wrong, only faster.

The budget is not the enemy here. For target-setting, board governance and holding a line, a fixed annual plan is still the right tool. The mistake is asking it to also be your live view of the future, a job it was never built for, and then wondering in September why it has so little left to say.

If the plan you approved in January no longer describes the year you are in, that is not a budgeting failure. It is a budget doing exactly what a budget does. The forward view is a different job, and it wants a different tool.

Common questions

What is a rolling forecast?

A financial forecast that never stops the same distance ahead. As each month closes, the actual figure replaces that month's forecast and a fresh month is added at the far end, so the view keeps sliding forward instead of running out at the year end.

Is a rolling forecast better than an annual budget?

Neither is better. They answer different questions. The budget sets the target you are held to; the rolling forecast shows where you are actually heading. Most finance teams keep both.

How often should you update a rolling forecast?

Monthly or quarterly is the norm. Monthly suits businesses where cash and demand move quickly; quarterly is enough for steadier ones. The rule that matters more is that the refresh has to be light enough to actually happen.

Do you still need an annual budget if you run a rolling forecast?

Usually, yes. The budget still does the governance job: setting targets, framing the board conversation, and giving a fixed line to measure against. The forecast sits alongside it, not in place of it.

Why do rolling forecasts fail?

Weight. Teams try to run the full annual budget every month, it takes a week nobody has, and it quietly stops rolling. A rolling forecast has to be driver-based and lighter than the budget to survive.

Sources

• Association for Financial Professionals (AFP), FP&A surveys on rolling forecast adoption.
• FP&A Trends Survey, on rolling forecast usage and forecast turnaround times.
• Dash AI platform and pricing pages