Forecasting is not a one-time activity. As new actuals are loaded, finance teams usually need to refresh assumptions, extend the forecast period, and update the planning view. A forecast that was useful last month may already be outdated once the next period of actuals is available.
Workday Adaptive Planning includes a Rolling Forecast option within Predictive Forecaster to help keep forecast definitions aligned with the latest actuals data. Instead of manually changing forecast periods after every actuals load, the forecast window can move forward based on the Completed Values Through date of the selected actuals version.
This is useful for organizations that run regular monthly or quarterly forecasts and want the predictive forecast setup to stay aligned with the planning cycle.
What Rolling Forecast Does
Rolling Forecast is an option available when creating or configuring a forecast in Predictive Forecaster. When enabled, it allows the forecast period to shift forward as actuals are updated.
In a fixed forecast setup, the forecast start and end periods are manually defined. That works when the forecast period does not change often. But in a rolling forecast process, the forecast period changes as the business moves through the year.
Rolling Forecast reduces that maintenance. As actuals are loaded and the actuals version is updated, Predictive Forecaster can adjust the forecast start period and related reference periods automatically.
How Rolling Forecast Uses Actuals
Rolling Forecast depends on the Completed Values Through date in the selected actuals version. This date tells Adaptive Planning the latest period for which actuals are considered complete.
When new actuals are loaded and the Completed Values Through date is updated, Predictive Forecaster can use that information to shift the forecast period. The forecast starts after the latest completed actuals period, and the historical reference data extends through the most recent actuals.
For example, if actuals are complete through June 2026, the rolling forecast can start in July 2026. After July actuals are loaded and the Completed Values Through date is updated to July 2026, the forecast can move forward and start in August 2026.
This keeps the forecast aligned with the latest closed or completed actuals period.
Rolling Forecast Options
When Rolling Forecast is enabled, users can choose how the forecast periods shift.
One option is to shift both the forecast start period and forecast end period. This moves the entire forecast window forward while keeping the forecast horizon the same length. For example, a 12-month forecast remains a 12-month forecast, but the start and end periods move forward as actuals are updated.
Another option is to shift only the forecast start period. This can be useful in some cases, but it needs to be reviewed carefully. If only the start period moves forward and the end period stays fixed, the forecast window becomes shorter over time. Eventually, the forecast start period can move beyond the forecast end period. When that happens, Adaptive Planning displays a warning.
From a process design perspective, shifting both the start and end periods is usually easier for users to understand because the forecast horizon remains consistent.
Example of a Rolling Forecast
Assume the actuals version is loaded through June 2026 and the Completed Values Through date is set to June 2026. In that case, the forecast start period becomes July 2026, and the historical actuals reference period includes data through June 2026.
After July actuals are loaded and the Completed Values Through date is updated to July 2026, the forecast start period moves to August 2026. The reference data now includes July 2026 actuals.
This pattern continues as each new actuals period is loaded and completed. The forecast rolls forward with the planning cycle instead of staying fixed to the original setup period.
Why Scheduling Matters
Rolling Forecast becomes more useful when it is combined with scheduled forecast runs. Predictive Forecaster supports scheduled runs on daily, weekly, or monthly frequencies.
For most FP&A teams, the schedule should align with the actuals load and close process. For example, if actuals are loaded and validated monthly, the forecast schedule should run after that process is complete. Running the forecast too early may cause it to use incomplete actuals data.
A scheduled rolling forecast can pick up newly loaded actuals, shift the forecast periods, and generate updated forecast values without requiring a user to manually adjust the forecast setup each time.
This can reduce administration effort, but it also requires process discipline. The schedule should run only when actuals are ready and the forecast version is prepared to receive updated data.
Data Requirements
Rolling Forecast follows the same core requirements as other Predictive Forecaster forecasts. Actuals data must exist in the selected sheet, the selected algorithm must have enough historical data, and the historical-to-forecast data ratio must be met.
A key requirement is the minimum 3:2 ratio of actuals data points to forecasted data points. For example, a two-year forecast requires at least three years of actuals data. Some forecasting algorithms may require more history depending on the method selected and the pattern in the data.
This should be reviewed before enabling Rolling Forecast. If the historical data is limited, inconsistent, or incomplete, the forecast output may not be useful.
Configuration Checks
Before enabling Rolling Forecast, the team should confirm that the Completed Values Through date is maintained correctly. This is one of the most important controls because the rolling logic depends on that date.
Actuals should also be loaded consistently, and the forecast schedule should align with the actuals load timing. The target forecast version should be available and not locked. Historical data requirements should be met for the selected algorithm.
It is also important to confirm what happens to existing forecast data when the forecast runs. Predictive Forecaster writes forecast values into the selected forecast version, so teams should understand whether the run will overwrite values that users have already reviewed or adjusted.
Implementation Considerations
From an implementation perspective, Rolling Forecast should be designed as part of the broader forecast process. It is not only a configuration setting.
The team should define when actuals are loaded, who updates the Completed Values Through date, when the forecast should run, which version receives the output, and how users review the updated forecast.
Version naming and access are also important. Users should clearly understand which version contains the predictive forecast output and whether that version is intended for review, adjustment, reporting, or downstream planning.
If the forecast is scheduled, ownership should be clear. Someone should monitor whether the scheduled runs are successful, whether the output looks reasonable, and whether any exceptions need attention.
Final Observation
Rolling Forecast in Workday Adaptive Planning Predictive Forecaster helps keep forecast definitions aligned with the latest actuals data. Instead of manually redefining forecast periods after each actuals load, the forecast window can move forward based on the Completed Values Through date.
For organizations with regular forecast cycles, this can reduce manual maintenance and keep predictive forecast runs closer to the current business period.
The feature is most useful when the actuals load process, version design, forecast schedule, and review workflow are clearly defined. Rolling Forecast can automate part of the setup maintenance, but the forecast output still needs finance review, data validation, and process ownership.