Your CEO asks: "How are we going to close the year?" It's August. The budget you built in October of last year says $80M. Year-to-date through July says $42M and the trend isn't great.
Here's the moment that defines a CFO: do you answer with the budget number, with your best current projection, or do you tell them you're defending two different numbers at the same time?
The rolling forecast is the discipline that prevents that question from having two answers. Instead of a budget that dies after three months, you have a forecast that updates every month and always reflects the most recent reality.
By the end of this module you'll have it down. Let's go.
It's March. Your CEO asks how you'll close the year. What number do you give?
In plain language
Before the mechanics, the four basic questions.
Why do this at all?
To make decisions with current data. A static budget reflects what you knew 14 months ago. A rolling forecast reflects what you know today. When the CEO asks "how are we going to close?" the answer should be based on the best information you have now, not on a promise you made before the world changed.
Who uses it?
The FP&A team builds it in collaboration with each function's leaders. It's used by: the CEO and the board for resource allocation decisions, the CFO for cash planning and bank covenants, operating leaders for hiring, spending, and production planning.
When does it show up?
Ideally every month (or every quarter). At each period close: update actuals, recalibrate the projection, add one more period at the far end of the horizon. Cadence matters more than model sophistication.
What if we skip it?
You defend a budget nobody believes anymore. Decisions get made by gut because the official plan doesn't apply. By Q3, the whole team operates with an unofficial parallel number — and nobody is aligned. You lose three quarters of clarity by not updating one.
Meet Andina S.A. (again)
Same Andina from Module 2.6 — the LATAM coffee company, $200M in revenue, based in Chile. The FP&A team closed the AOP in October of last year. FY plan: $80M in one business line (premium capsules). Monthly budget: $6.67M.
Three months in, in March, a key aluminum supplier raises prices 12%. Margin compromised. In June, a competitor launches a cheaper compatible capsule. Volume compromised. In September, the Chilean peso drops 8% against the dollar. Imported costs compromised.
Three hits. None forecasted in the AOP. Each meaningful on its own. Together, a different story.
And yet, in every monthly review, the team defends the original budget. "We're $2M below plan." "We're $4M below plan." "We're $6M below plan." Month after month, measuring against a number nobody believes anymore.
This is where rolling forecast comes in. The visual below shows it: drag the slider and watch the static budget stay anchored while the rolling forecast learns from the real world every month.
Plan vs reality: the visual that makes it obvious
Three lines. Three models of how Andina could have tracked the year:
Static budget (gray, dashed): $6.67M per month, every month. Set in October. Doesn't move.
Rolling forecast (blue): starts equal to the budget, then learns. Each month, the projection for future months adjusts based on the recent actual trend.
Actual (green): the truth. Revealed month by month as you advance the slider.
Interactive visual
The plan vs reality: 12 months of Andina S.A.
Budget FY
$80.0M
+8.1%
Rolling FY
$75.6M
+2.2%
Actual to date
$38.2M
6/12
What you're looking at
The static budget doesn't move. It was set in October of the prior year. The rolling forecast learns every month: incorporates actuals and projects forward. Look at the year-end gap — rolling got you close to truth; static left you defending a promise from 14 months ago.
If you dragged to December: the static budget left you $6M above actual ($80M vs $74M, 7.5% gap). The rolling forecast got you close to actual (around 1%).
That 6.5-point gap isn't a modeling error. It's information. The rolling forecast captured three hits — supplier, competitor, FX — because it had the discipline to look at reality every month. The static budget couldn't capture anything because it closed its contract with reality in October.
This doesn't mean the static budget is useless. It serves as a reference, as initial commitment, as a starting point for understanding why the business deviated. But it shouldn't be the number you defend every month.
The mechanics: how to build a rolling forecast
- Define the horizon. Most common: 12-18 months forward. Some companies use 5 or 6 quarters (rolling 5Q or 6Q). The horizon should cover your longest decisions (capex, hiring, annual contracts).
- Define the cadence. Monthly or quarterly. Monthly gives more control but consumes more team time. Quarterly is lighter but you lose resolution. Most mid-market companies work well with monthly cadence for the next 3 months, quarterly for the rest.
- Define the anchor periods. Not the whole horizon has the same authority. Typical convention: the next quarter is committed (the team puts skin in the game), the next 2-3 quarters are reference (the best current projection), the rest is directional (base scenario). This prevents the trap of treating month 18 like month 1.
- Define the calibration. Each month, after closing actuals, measure forecast accuracy: how close did last month's forecast come to actual? Track MAPE (Mean Absolute Percentage Error) by line, by team, by period. That's what turns forecast into discipline instead of opinion.
- Define the process. Who updates which line, in what order, with what deadline. The forecast doesn't update itself: it needs line owners (Commercial owns revenue, each function owns its OPEX), a consolidator (FP&A), and a final reviewer (CFO).
- Is next quarter's number a single number? If the organization operates with two numbers (one official from the AOP, another real "that we all know"), you don't have a rolling forecast — you have politics. The success signal is that next quarter's forecast is the number that the board, the CFO, and the operating team defend jointly.
- Is accuracy improving? Track MAPE month by month. If the team is learning, the error drops. If it doesn't drop, you're not forecasting — you're doing wishful thinking with monthly cadence.
- Do decisions change when the forecast changes? If you update the forecast but the hiring plan doesn't move, spending plans don't adjust, and bank commitments don't renegotiate — the forecast is theater. It has to drive action.
Adversarial check
Adversarial check
1.Your CEO shows you the September close dashboard. Says: "We're $6M below budget. I need the team to put it on the line and recover." Your updated rolling forecast says we'll close at $74M (not the $80M from the budget). What do you tell them?
2.You're implementing rolling forecast for the first time at a company that always operated with static budgets. What's the biggest risk of failure in the first 6 months?
3.You join a new company as CFO. They operate with annual static budget. You want to move to rolling forecast. What do you do first?
Exit checklist
Suggested re-review: 6 months. If you implement a new rolling forecast, come back to this module after the first complete cycle to calibrate your own experience against the 3 test questions.
Optional
Go deeper
Sources and books to dig into the original material