The general narrative around reforecasting is that more is better: higher frequency, greater detail, broader participation. The underlying assumption is that finance teams should be chasing the holy grail of real-time visibility. Sounds right. Mostly isn't.
There is a cost to producing forecasts that rarely gets acknowledged. Every hour spent rebuilding bottom-up assumptions is an hour not spent on execution. Every time sales managers update pipeline forecasts instead of working pipeline, you have made a trade-off — you just haven't made it consciously.
The default should not be to add forecasting. The default should be to question every forecasting process you have and require it to justify its existence.
Forecast vs. Budget
Before anything else: a reforecast is not a rebudget. These are frequently confused, and the confusion is costly.
The budget is the performance contract. It sets targets, drives accountability, and aligns incentives. You do not rewrite it because the year is going differently than expected. If you do, you destroy accountability — there is no longer a stable reference point against which performance can be measured.
A reforecast updates your best estimate of the full-year outcome. It tells you where you are likely to end up given current trajectories. It does not change what you are being held to. It changes what you expect.
If you find yourself reforecasting so frequently that the budget feels irrelevant, you have probably crossed into re-budgeting without admitting it.
Forecast Approaches
The Risks & Opportunities Tracker
The R&O tracker deserves more attention than it typically gets. It is the most underused tool in the FP&A toolkit.
The approach: instead of rebuilding a full three-statement forecast every quarter, maintain a live tracker of the specific items that are causing you to deviate from the budget. Risks are the things pulling the full-year outcome below budget; opportunities are the things pushing it above.
Each item has an owner, an expected financial impact, a probability weighting, and a set of mitigating actions. The CFO reviews this monthly alongside the performance review. The total gives you a view of the expected year-end outcome without requiring a full reforecast cycle.
This approach preserves accountability to the budget while providing the forward-looking visibility leadership needs. It is action-oriented in a way that a full re-model rarely is — it is much easier to attach names and deadlines to a list of specific risks than to a P&L line that has moved.
When Rolling Forecasts Are Non-Negotiable
There are environments where frequent reforecasting is not a choice. If the business has a material liquidity risk, a rolling 13-week cash flow forecast is essential. If there are bank covenant obligations that need monitoring, an 18-month rolling view is required. If you are a startup managing to a burn rate ahead of a fundraise, the forecast is your primary financial instrument.
In these situations, the forecasting cost is justified because the downside of not forecasting is an existential event.
But these are specific, known conditions. They are not an argument for extending high-frequency forecasting to every other part of the business where the urgency does not exist.
Designing Your Forecast Process
When setting the forecasting approach for your business, work through four questions:
Who is it for? Performance management (internal accountability), cash and covenant monitoring (treasury), external communication (board, investors), or decision support (specific strategic decisions). Different purposes require different approaches.
What is the cost? Not just the finance team's time — the operational time consumed updating pipeline, replanning headcount, and re-phasing initiatives. This cost is almost always underestimated.
What decision does it inform? "It is nice to have the latest view" is not a sufficient answer. There needs to be a specific decision that is made differently because of the forecast output.
What is the alternative? Often the R&O tracker or a light quarterly update achieves 80% of the benefit at 20% of the cost. The right question is not what the forecast can do — it is whether a lighter approach would be sufficient.
Start with no reforecasting, and reason up from there. The processes that survive that scrutiny are the ones worth running.