Beyond the Annual Budget: The Power of the Rolling Forecast

There is a running joke in FP&A that the annual budget is obsolete by the second week of February. Market conditions shift, supply chains delay, and suddenly a static 12-month plan is just a historical document we have to explain variances against.

Most finance teams know they should be moving to a rolling forecast, continuously forecasting four to six quarters out so leadership always has a clear line of sight. The roadblock is usually the administrative burden.

The Spreadsheet Nightmare

Managing a rolling forecast in a spreadsheet is a mechanical headache. Every time a month closes, someone has to go into the master template, hide the closed month, add a new month to the end of the horizon, update all the SUM formulas to capture the new range, and make sure they didn't accidentally break a cell reference. It is tedious, error-prone work that keeps analysts busy doing data entry instead of analysis.

The deeper problem is structural. A spreadsheet doesn't know the difference between a closed period with real actuals and an open period with assumptions. Every cell looks the same. Protecting closed periods from accidental edits requires manual locking. Extending the horizon requires structural changes to the file. And when assumptions need updating, there is no systematic way to reseed open periods from the latest actuals without rebuilding the model.

The Open/Closed Period Architecture

A rolling forecast built on a native planning platform works differently at the architectural level. Every period in the forecast is explicitly classified as either open or closed, and those two states behave completely differently:

• A closed period is locked. It reads directly from your actuals measure in the semantic model. Whatever Gross Revenue actually was in January is what appears in January, immutably. No planner can overwrite it. Variance analysis between plan and actuals calculates automatically because both live on the same sheet.
• An open period accepts input. It holds forecast assumptions entered by planners or generated by a statistical model, and those values remain editable until the period closes. The moment January closes, February through the end of the horizon remains open, and a new period is appended to the end to keep the forward window intact.

It is also worth noting that a closed period can reference a different measure from the open period ahead of it. This means actuals and forecast can live as separate, clean measures — Gross Revenue for closed periods, Forecast for open periods — while the series remains continuous without a break.

This distinction is what makes rolling forecasting operationally manageable. Closed periods are facts. Open periods are assumptions. The system knows which is which.

The Monthly Close Workflow for a Rolling Forecast

In Fabric Planning, closing a month is a three-step sequence rather than a manual restructuring exercise:

1. Close Period: On the Model ribbon, trigger Close Period. The system locks the closed month from any further data entry, replaces the forecasted values with finalized actuals from the semantic model, and updates downstream variances automatically. The close trigger is also configurable — organizations running a consistent monthly close can automate this step so the period locks without a manual ribbon action.
2. Extend Forecast Range: Use Extend Forecast Range to append the next period to the end of the timeline. A team running a 12-month rolling forecast always maintains exactly 12 months of forward visibility. In April they see May through April of next year; in October they see November through October of next year.
3. Reforecast: Rather than leaving the newly opened forward period blank or copying last year's values manually, Reforecast lets you specify a source period and a growth assumption—for example, seeding the newly added month from equivalent prior-year actuals and applying a 4% growth rate.

Statistical Forecasting: Letting the Model Do the Work

For teams with sufficient historical data, there is a more powerful alternative to manual assumption entry. Fabric Planning's built-in Predict engine uses historical actuals to infer trend and seasonality automatically, populating the full forecast horizon in a single run.

The minimum history window is 24 months, with two full years of actuals, the model can isolate genuine seasonal patterns rather than mistaking single-year anomalies for structural trends.

One practical note on access: Predict is available in both reading view and edit mode. Analysts reviewing the forecast can run a statistical prediction without switching to edit mode — useful in organizations where most users have read access and edit access is reserved for a smaller group of planners.

When the forecast runs, historical actuals render in grey and predicted values render in green, bounded by a confidence range showing the uncertainty band.  The default confidence interval is 90% — the model is 90% confident the actual will land within the shaded band. Adjusting this percentage doesn't change the central forecast line, only the width of the uncertainty band shown in the preview. You can also layer a discretionary growth factor on top of the output — for example, adding a 4% market growth assumption on top of what the model predicts from history alone.

Choosing the Right Algorithm

If you are not sure which algorithm fits your data, start with Auto ETS or Auto ARIMA. Both automatically test multiple configurations against your historical series and select the best-fitting one — no statistical expertise required. The table below is a simplified guide to the most common data patterns. For the complete algorithm reference, including all model orders and variants, see the Predict documentation.

Note: Auto ETS and Auto ARIMA are not limited to cases where you are unsure — they are valid choices for any dataset and a reliable default for most teams.

• Trend Decomposition with MSTL (a method that separately models several overlapping seasonal cycles — like month-of-year and quarter-end patterns — then adds them back together): The standard choice for most revenue planning data with multiple seasonal patterns.
• Exponential Smoothing (ETS) (a family of models that weight recent observations more heavily than older ones, with variants that handle trend and seasonality differently): Spans nine variants from Simple through Holt-Winters Multiplicative. Auto ETS tests all nine and selects the optimal fit. Once generated, smoothing parameters can be manually tuned — α (level) controls how quickly the model reacts to recent changes, β (trend) controls how much weight it gives to a detected trend, γ (seasonality) controls how strongly it responds to seasonal swings, and ϕ (damping) controls whether a trend is expected to slow down over time.
• ARIMA / SARIMA (models that capture how each value in a series relates to its own past values and past forecast errors): ARIMA handles non-seasonal time series, SARIMA models both seasonal and non-seasonal patterns simultaneously. Auto ARIMA automatically tests several configurations against your historical series and keeps the best-fitting one — no manual order selection required.

The Practical Implication

A finance team can move from a blank forecast horizon to a fully populated 12-month projection in a single step. When a period closes, the Reforecast action reseeds the newly opened month using the same statistical logic, keeping the rolling forecast active without a manual update cycle.

The monthly close transforms from a mechanical data-entry task into a review and judgment exercise, cutting forecast preparation from days to hours.

Next Steps

To see how to manage open/closed periods, run statistical predictions, and extend forecast range on a live dataset, work through Exercise E2 in the Fabric Planning training guide.

Frequently Asked Questions