Rolling Forecast
What is Rolling Forecast?
A rolling forecast is a financial forecast that is updated at regular intervals, usually monthly or quarterly, and always extends a fixed period ahead, such as the next 12 or 18 months.
Updated November 2026 · 5 min read
A rolling forecast is a forecast that moves forward with time. Each month or quarter, the organization updates its projections using the latest actual results and adds a new period at the end, so the forecast always looks the same distance ahead. A 12-month rolling forecast prepared in March covers March through the following February; the one prepared in April covers April through the following March.
Rolling forecasts address a common weakness of the annual budget: it is set once, often months before the year begins, and becomes less accurate as conditions change. For IT financial management, rolling forecasts help technology leaders see where spending is heading, respond to changes in cloud usage, hiring and vendor costs, and give finance a current view of technology spending beyond the end of the fiscal year.
Definition of Rolling Forecast
A rolling forecast is a forward-looking projection of revenue, costs or cash that is refreshed on a fixed cycle and extended by one period each time, so that it always covers a constant horizon. Common horizons are 12, 18 or 24 months, updated monthly or quarterly.
It is a form of financial forecasting that replaces or supplements a static forecast tied to the fiscal year. Unlike a budget, a rolling forecast is not usually a spending limit; it is a best estimate of what will happen.
Rolling Forecast vs Annual Budget
The annual budget sets targets and spending limits for a fiscal year and is usually fixed once approved. Its horizon shrinks as the year goes on, so by the third quarter it says little about the months ahead.
The rolling forecast keeps a constant horizon and is updated as conditions change. It shows the expected outcome rather than the target, and highlights gaps between the two early enough to act.
Most organizations use both. The annual operating plan sets commitments and accountability, while the rolling forecast tracks how actual results are likely to compare and informs the next plan.
Level of Detail
Rolling forecasts are usually prepared at a higher level than the annual budget. Forecasting every cost center and account line every month takes too much effort and adds false precision.
Instead, organizations forecast the main cost categories and the drivers behind them, such as headcount, cloud consumption, license counts and major projects. This keeps the process fast enough to repeat every cycle.
Many organizations use driver-based planning for this purpose, so that a change in a driver, such as a hiring delay, flows through the forecast automatically.
Importance of Rolling Forecasts in IT Financial Management
Technology costs change quickly. Cloud usage grows month to month, vendor prices rise at renewal, projects start late and hiring plans shift. A forecast set once a year cannot reflect these changes.
Rolling forecasts give IT and finance a shared, current view of where technology spending is heading. Instead of explaining variances against a plan made many months earlier, teams can discuss what is likely to happen next and what to do about it.
They also make conversations about reallocating funds easier, since both sides are working from the same expected outcome rather than an outdated plan.
Earlier Decisions
Because the forecast is updated frequently, gaps between expected spending and the budget appear months earlier. If cloud costs are trending above plan in the second quarter, leaders can act then, rather than discovering the overrun at year-end.
Similarly, underspending from delayed projects becomes visible early, allowing funds to be redirected to other priorities instead of being lost or spent hastily at the end of the year.
This supports IT cost management by turning the forecast into a tool for decisions rather than a reporting exercise.
Planning Beyond the Fiscal Year
A rolling forecast always looks the same distance ahead, so in the last quarter of the fiscal year it still shows the next 9 to 12 months. This gives a useful starting point for the next annual plan.
For technology, where contracts, renewals and projects often cross fiscal years, this longer view helps leaders see commitments that will affect next year's spending before the planning cycle begins.
It also reduces the effort of annual planning, since much of the information needed is already in the forecast.
How to Implement a Rolling Forecast
Implementing a rolling forecast involves choosing the horizon and frequency, deciding the level of detail and building a repeatable process.
The aim is a forecast that is accurate enough to support decisions and light enough to update every cycle. Organizations that try to forecast at the same level of detail as the annual budget often find the process too slow to sustain, and the forecast falls out of date.
Setting Horizon and Frequency
The horizon should cover the period over which decisions are made. For many IT organizations, 12 to 18 months is enough to cover major renewals and projects. Longer horizons may be useful for capital planning.
Monthly updates suit fast-changing costs such as cloud, while quarterly updates are often enough for stable costs and smaller organizations. Some organizations update high-variability categories monthly and others quarterly.
The schedule should align with the financial close, so each forecast starts from the latest actual results.
Building the Process
The forecast should be owned by the people closest to the costs, such as service owners and budget holders, with IT finance coordinating, reviewing and consolidating.
Each cycle, the forecast is compared with the previous forecast, the budget and actual results. Large changes are explained, and variance analysis identifies the causes.
Tracking forecast accuracy over time shows where the process needs improvement and builds confidence in the numbers.
Examples of Rolling Forecasts in IT Financial Management
The examples below show how rolling forecasts support decisions.
Both use illustrative figures.
In each, the forecast revealed a change months before year-end, while there was still time to respond.
Catching a Cloud Overrun
An IT organization has an annual cloud budget of $6 million, or $500,000 a month. In April, the rolling forecast shows usage growing 3% a month, putting the remaining nine months at about $5.2 million against $4.5 million budgeted.
Leaders respond by committing to reserved capacity and removing idle resources, bringing the forecast back within budget. Without the rolling forecast, the gap would have been discovered much later in the year, when the options for closing it were far more limited.
Redirecting Underspend
Another organization's rolling forecast in July shows that a $2 million project will not start until the next fiscal year because of vendor delays.
The CIO redirects $1.2 million of the freed funds to a security upgrade that was waiting for funding, and the forecast for the following year is updated to include the delayed project. The remaining $800,000 is held as a contingency for the rest of the year.
Conclusion
A rolling forecast is a financial forecast that is updated regularly and always extends a fixed period ahead. It complements the annual budget by showing the expected outcome as conditions change.
In IT financial management, rolling forecasts help leaders spot overruns and underspending early, plan across fiscal years and respond to fast-changing costs. Choosing the right horizon and frequency, forecasting at the driver level and building a repeatable process help organizations get the most value from them.
Related terms
Financial Forecasting
Financial forecasting is the process of estimating future financial results, such as revenue, costs and cash flow, based on historical data, current trends and planned changes. It is updated regularly through the year.
Annual Operating Plan (AOP)
An annual operating plan (AOP) is a company's plan for the coming fiscal year, setting targets for revenue, costs, headcount and key initiatives, and the budgets each team will work within.
Driver-Based Planning
Driver-based planning is a budgeting and forecasting method that calculates costs from the operational factors that cause them, such as headcount, users or transactions, rather than adjusting last year's figures.
IT Cost Management
IT cost management is the ongoing practice of planning, monitoring and controlling technology spending so that it stays within budget and delivers value. It combines visibility, accountability and optimization.