A forecast is never a guaranteed number. It is an estimate based on historical patterns, selected forecast methods, and the data available at the time the forecast is generated. In a planning process, the forecast value is important, but it is not the full story. Finance teams also need to understand the level of uncertainty around that forecast.
Workday Adaptive Planning Predictive Forecaster includes a Forecast Range option to help with that review. Instead of producing only one forecast value, Forecast Range generates an upper and lower boundary around the primary forecast. This gives planners a broader view of the possible outcome and helps them understand whether the forecast is narrow, stable, or more uncertain.
What Forecast Range Does
Forecast Range is an optional setting that can be enabled during forecast setup in Predictive Forecaster. When it is enabled, the forecast run produces three related outputs: the main forecast value, an upper forecast value, and a lower forecast value.
The main forecast represents the expected value generated by Predictive Forecaster. The upper and lower values represent the forecast boundaries based on the selected probability level. Together, these outputs give the user a range rather than a single point estimate.
This is useful because a single forecast number can create a false sense of precision. In real planning work, there is always some level of uncertainty, especially as the forecast extends further into future periods.
How Forecast Range Is Stored
When Forecast Range is configured, the forecast output is stored across separate versions. The primary forecast values are written to the selected Forecast Version. The upper range values are written to the Upper Forecast Version. The lower range values are written to the Lower Forecast Version.
This version-based design is important because it keeps the forecast outputs clear and reportable. Users can compare the base forecast, upper range, and lower range in sheets, reports, dashboards, or forecast visualizations.
Before running the forecast, the required versions should already exist and be selected correctly in the forecast setup. If the upper and lower versions are not created or not assigned properly, the forecast range output cannot be stored as expected.
Probability Level
The Probability Level controls the confidence interval used to generate the forecast range. In practical terms, it influences how wide or narrow the upper and lower boundaries are.
A higher probability level generally creates a wider range because the forecast is allowing for a broader set of possible outcomes. A lower probability level generally creates a narrower range. The right setting depends on how the finance team wants to review forecast uncertainty and how much variability exists in the historical data.
This should not be treated as only a technical setting. FP&A users need to understand what the selected probability level means because it directly affects how the forecast range is interpreted in planning discussions.
Upper and Lower Forecast Versions
Forecast Range requires users to define where the upper and lower forecast values will be stored. The Upper Forecast Version receives the upper boundary values generated by the forecast run. The Lower Forecast Version receives the lower boundary values.
These versions should be named clearly so users understand their purpose. For example, a planning team may use one version for the main predictive forecast, one version for the upper forecast range, and one version for the lower forecast range.
Clear version naming matters because these outputs may later be used in reports, dashboards, variance views, or planning review meetings. If the versions are not named properly, users may confuse the forecast range with manually entered scenarios or other planning versions.
Reviewing Forecast Range Results
After the forecast is executed, users can review the main forecast version alongside the upper and lower versions. This allows finance teams to see the expected forecast and the range of possible outcomes.
Forecast Range can also be visualized through forecast range charts, including fan chart-style views. These views are helpful because they show uncertainty visually. As forecast periods move further into the future, the range may expand, which reflects the normal increase in uncertainty over time.
This type of visualization is useful in planning conversations. It helps users see that near-term periods may have a tighter forecast range, while later periods may have more variability.
Why Forecast Range Is Useful for FP&A
Forecast Range is useful because it gives more context than a single forecast value. A single number may be enough for loading a forecast into a planning version, but it does not explain how much confidence the team should have in that number.
With Forecast Range, FP&A teams can review the expected forecast, the upper boundary, and the lower boundary together. This supports better discussion around risk, upside, downside, and forecast confidence.
For example, if the range is narrow, the forecast may be relatively stable based on historical patterns. If the range is wide, the team may need to review the data, business drivers, seasonality, or recent changes more closely.
The range does not replace business judgment. It gives planners another view to support that judgment.
Configuration Checks Before Running Forecast Range
Before enabling Forecast Range, the setup should be reviewed carefully. The forecast version must exist. The upper and lower forecast versions must also exist. The selected forecasting method must support Forecast Range. Historical data requirements should be met, and the forecast setup should be tested before users rely on the output.
It is also important to confirm how the forecast range will be used after it is generated. If the output will be included in reports or dashboards, the reporting structure should be prepared in advance. If the output will support forecast review meetings, users should understand what the upper and lower values represent.
Implementation Considerations
From an implementation perspective, Forecast Range should be designed as part of the broader forecasting process, not as an isolated feature. Teams should define which accounts, levels, or dimensions will use Predictive Forecaster, which versions will store the forecast output, and how the forecast range will be reviewed.
Version security and access should also be considered. If users can view the forecast range but should not edit those versions, version permissions should be aligned with the process. The same applies to reporting. Users should clearly understand which version is the main forecast, which version is the upper range, and which version is the lower range.
The forecast range output should also be reviewed over time. If the range is consistently too wide, too narrow, or not useful for decision-making, the forecast setup and source data may need to be revisited.
Final Observation
Forecast Range in Workday Adaptive Planning Predictive Forecaster is a practical feature for showing uncertainty around forecasted values. It allows users to review the expected forecast together with upper and lower boundaries, all stored in separate versions.
For FP&A teams, this is useful because forecasting is not only about producing one number. It is about understanding the possible range of outcomes and using that information in planning discussions.
The feature should be configured carefully, named clearly, and explained properly to users. When implemented well, Forecast Range can make predictive forecasting more useful because it gives finance teams a better view of both the forecast and the uncertainty behind it.