The annual plan tells you what you committed to. A rolling forecast tells you where you're actually headed. Most teams only trust one of them.
Budget season is in full swing. If you're in the middle of it, you may be asking a question most business and finance leaders I know have asked at least once: is the annual budget worth the effort? Why spend months building a plan that's out of date by February, when a rolling forecast could keep pace with the business?
I understand the frustration. I've sat through plenty of budget cycles that felt more like negotiation than planning. But after more than 20 years across commercial finance, sales operations and analytics, I've landed somewhere different. The annual plan and the rolling forecast do different jobs. Drop either one and you lose something you'll miss.
Here's how I think about each, and how to run them together without doubling the workload.
The annual plan is a commitment
The annual plan is where the company decides what it's trying to do: revenue targets, headcount, investment priorities, quotas. It's an agreement between leadership, the board and the teams who have to deliver.
That's why it needs to hold still. If the target moves every time the outlook moves, nobody is accountable for anything. Sales comp is built on it. Hiring plans are built on it. The board measures you against it.
The mistake isn't having an annual plan. The mistake is asking it to do a job it was never built for: telling you, in July, what's actually going to happen in Q4.
A rolling forecast is a steering tool
A rolling forecast looks ahead over a fixed window, often the next four to six quarters, and updates on a set cadence, monthly or quarterly. When a month closes, you add one at the far end. The horizon never shrinks to nothing at year-end the way a calendar-year view does.
Its job is to answer a different question: given what we know today, where will we land, and what should we do about it?
That means a good rolling forecast is honest, not aspirational. It should absorb pipeline changes, pricing moves, hiring delays and churn as soon as they show up, along with shifts in the economy, the market and the competition. If it just restates the plan with a few tweaks, it isn't a forecast. It's the plan with a new date on it.
I wrote earlier about what it takes to turn sales forecasts into more than educated guesses. The same discipline applies here. A forecast is only useful if people believe it reflects reality.
Where teams go wrong with both
A few patterns I see again and again:
Re-forecasting the plan instead of the business. Teams start from the budget and adjust it, rather than starting from current drivers. The result stays anchored to assumptions that are already months old.
Too much detail. A rolling forecast built at the same line-item depth as the budget turns into a second budget cycle every month. People burn out and quality drops. Forecast at the level of the drivers that actually move the number, the same ones the plan is built on.
No link back to the plan. If the forecast lives in one model and the plan in another, the variance conversation becomes an argument about whose spreadsheet is right.
Quietly moving the target. When the forecast drifts below plan, some teams lower the plan to match. It feels practical, but it erases the signal. The gap is the point.
How to run a rolling forecast alongside the annual plan
Here's the operating model I recommend.
Set the annual plan once, and hold it. Build it from capacity and drivers, not last year plus a percentage. Lock it as the accountability baseline.
Build the rolling forecast on the same drivers. Internal drivers such as headcount, ramp, productivity, pipeline conversion, pricing and retention. External drivers too: macro conditions, market trends and competitive moves. Same definitions, so the two compare driver by driver. You don't need the budget's line-item detail to do that.
Report the gap every cycle. Plan, latest forecast and variance, side by side. Explain the variance in drivers, not just dollars.
Decide, don't just describe. Every forecast cycle should end with actions: shift investment, adjust hiring timing, change coverage. A forecast that doesn't change a decision is reporting, not planning.
Let the forecast seed next year's plan. By the time annual planning starts, the rolling forecast already holds a credible view of next year. Start there. The budget cycle gets shorter and the starting point is grounded.
That last step is where the two really earn their keep. The rolling forecast makes the annual plan faster and more realistic. The annual plan gives the forecast something meaningful to measure against.
Expect this to be iterative. The first few rolling forecasts will be rough. Some drivers will matter more than you assumed, others less, and a few definitions will need tightening. That's normal. Each cycle, compare what you forecast with what actually happened, find the drivers that missed, and fix them. Accuracy improves over a few cycles, not on the first try.
The takeaway
If you do one thing this quarter, put your plan and your latest forecast on the same page, built from the same drivers, and make the gap the first item in your monthly business review. You'll learn more from that one view than from either number on its own.
The plan is the promise. The forecast is the honest read on where you're headed. Leaders need both, side by side.
This is also faster and more efficient than it used to be. AI-led planning and insights tools can pick up driver changes sooner, take much of the manual work out of each cycle, and point to where the forecast is drifting from plan. That's the work we do at 108 Performance Partners: helping business and finance teams build this rhythm so it's practical, driver-based and owned by the people who run the business.