January: annual budget delivered. March: Q1 tracking off-plan, refresh required. June: full reforecast. September: board update needed. December: planning next year while managing out a budget that was out of date by February.
At some point the question has to be asked: when does the finance team actually run the business, rather than continuously re-planning it?
The Reforecast Addiction
Reforecasts exist because reality diverges from plan and that is reasonable. The problem is when frequent reforecasting becomes a substitute for managing to plan.
Business missing its numbers? Reforecast. Market conditions shifted? Reforecast. Leadership wants a more comfortable set of numbers for the board? Reforecast.
Before long, the team is spending more time updating forecasts than understanding why they are missing targets or figuring out what to do about it.
Set clear triggers for when a reforecast is warranted, material market changes, M&A activity, significant strategic pivots, or regulatory impacts. A 3% variance to plan in Q1 is normal variance. It should be managed operationally, not trigger a full corporate replanning exercise.
I have worked with a finance team that ran full reforecasts every month. They developed an increasingly precise picture of what they were going to miss. They had no capacity left to understand why or change it.
Proportionality
Every reforecast should not demand the same level of effort as the annual budget. Bottom-up builds, department reviews, consolidation sessions, and executive presentations conducted quarterly is not sustainable and is not necessary.
Update the key drivers. Adjust for confirmed changes. Leave detailed line items alone unless something material has genuinely shifted.
Create a tiered approach: a light refresh that updates top-line assumptions and lets models flow through, a medium refresh that addresses key expense areas, and a full rebuild reserved for situations where the business has materially changed. Use the heavy option only when it is genuinely warranted.
The Sandbagging Incentive
Sales misses budget in Q1. You reforecast downward and Sales beats the reforecast. Leadership asks why you lowered the number. Next time, you are reluctant to revise down even when the data supports it.
Reforecasting creates perverse incentives if it is not managed carefully. When beating a revised-down reforecast is rewarded the same as achieving the original budget, teams learn to sandbag reforecasts to create winnable targets.
Be explicit about how reforecasts are used in your accountability framework. Keep the original budget as the primary commitment baseline. Use the reforecast as a planning tool and an honest view of what you expect to happen. Track variance to both. Recognise the difference between the two clearly.
Connecting Reforecasts to Decisions
The most frustrating reforecast pattern is revenue is revised down, costs do not adjust, and nothing changes operationally. Leadership reviews a lower profitability outlook and the meeting ends.
A reforecast that does not trigger decisions is just an accounting exercise.
If you are going to reforecast, link it explicitly to decision rights. What cost actions are triggered if revenue drops by a defined amount? What recruitment activity pauses or accelerates? What investments get reconsidered? Make the connection between the updated numbers and the operational response explicit and pre-agreed.