Why a Holdout Changes the Forecasting Question
A fitted time-series model describes patterns in observations already available. Forecasting asks a different question: how well would a procedure predict values it had not yet seen? A holdout sample provides a direct, if necessarily limited, check. Its usefulness depends on preserving the time order: the model is selected and estimated using earlier months, and the later months are reserved for evaluation.
The examples use hypothetical monthly observations of an economic series measured in percentage points. The numbers are illustrative rather than real study results. The analysis assumes the series is suitable for a stationary ARMA model over the period considered. If the observed behavior instead indicates a trend or other nonstationarity, a stationary ARMA forecast should not be treated as adequate merely because it can be fitted.
Set Up the Forecasting Exercise
The training and holdout periods must be fixed before examining holdout outcomes. Candidate models, transformations, and tuning decisions are made using training data alone. Once the specification has been chosen, it is estimated on that training sample and used to forecast forward. Looking at holdout values to decide which model to report would make the holdout partly part of model selection and would generally give an overly favorable impression of performance.
An ARMA(\(p,q\)) model for a stationary series can be written as
Here \(\mu\) is the series mean, \(\varepsilon_t\) is a mean-zero innovation with variance \(\sigma^2\), and the autoregressive and moving-average terms describe dependence over time. For the usual Gaussian prediction intervals, assume the innovations are independent and normally distributed, and that the fitted model is an adequate representation over the forecast period. Stable, invertible specifications and residual diagnostics matter: a low information criterion does not by itself establish that the model is suitable.
A practical selection procedure compares a prespecified set of plausible candidate orders on the same training observations. AICc, for example, is AIC with a small-sample correction, \(AICc=AIC+2k(k+1)/(n-k-1)\), where \(k\) is the number of estimated parameters and \(n\) is the estimation sample size. Smaller values favor a better penalized fit among the candidates, but should be considered alongside residual autocorrelation and innovation checks. Those diagnostics should not show a systematic pattern left unexplained by the model.
Worked Example: Selecting an ARMA Specification on Training Data
Suppose a synthetic monthly series has 120 observations for training and six later observations reserved as a holdout. Three candidate models are fit to the same 120 training observations. The following illustrative AICc values and diagnostic summaries are obtained.
| Candidate | AICc | Residual portmanteau diagnostic p-value |
|---|---|---|
| ARMA(1,0) | 308.7 | 0.31 |
| ARMA(1,1) | 310.2 | 0.42 |
| ARMA(2,0) | 309.4 | 0.27 |
All three fits converge, and the residual checks show no flagged innovation outlier or strong departure from normality for this illustration. The AICc minimum is \(308.7\), so ARMA(1,0), equivalently AR(1), is the preferred candidate by this criterion. Its residual diagnostic p-value of \(0.31\) gives no evidence of remaining autocorrelation at the diagnostic's tested lags, though it does not prove the model is correct.
The choice is made before inspecting any of the six holdout outcomes. The selected model is then estimated on the 120 training observations and kept fixed for the holdout exercise. If the holdout were used to switch to ARMA(1,1), for instance, the reported holdout performance would no longer be a clean evaluation of a choice made independently of those outcomes.
Forecasts and Prediction Intervals
Forecasts are conditional expectations under the fitted model. For an AR(1) model with mean \(\mu\), the forecast recursively approaches \(\mu\) as the horizon grows. Prediction intervals describe uncertainty in a future observation, not uncertainty about the unknown mean alone. In a plug-in interval, estimated parameters are treated as fixed; such intervals therefore do not fully account for parameter-estimation uncertainty.
Worked Example: Forecasting Three Months Ahead
Suppose the selected synthetic model is AR(1), with fitted mean \(\hat{\mu}=0.500\) percentage points, autoregressive coefficient \(\hat{\phi}=0.600\), and innovation variance estimate \(\hat{\sigma}^2=0.160\) squared percentage points. The last training observation is \(y_T=0.900\) percentage points. For this calculation, assume the fitted AR(1) is stationary, the innovations are independent and normally distributed, and the plug-in forecast variances are appropriate.
The one-step forecast is
The next forecasts use the previous forecast in place of the unobserved future value:
For this AR(1), the forecast error variance at horizon \(h\) is \(\hat{\sigma}^2\sum_{j=0}^{h-1}\hat{\phi}^{2j}\). Thus the one-step standard error is \(\sqrt{0.160}=0.4000\) percentage points. A 95% normal prediction interval is the forecast plus or minus \(1.96\) standard errors:
At horizon three, the standard error is
The resulting interval is
The interval widens with the horizon because uncertainty accumulates from additional future innovations. Under the stated model and its assumptions, the 95% procedure is designed to cover the future observation in 95% of repeated forecast situations. It does not mean there is a 95% probability that this particular fixed interval contains the future value.
Evaluate Holdout Forecasts at Their Horizons
After the holdout outcomes become available, compute each forecast error as actual minus forecast. The sign indicates direction: a positive error means the forecast was too low, and a negative error means it was too high. Common summaries include mean absolute error (MAE) and root mean squared error (RMSE). For \(m\) forecast errors at a specified horizon, \(MAE=m^{-1}\sum |e_i|\) and \(RMSE=\sqrt{m^{-1}\sum e_i^2}\). Both are in the units of the series; RMSE gives relatively more weight to larger errors.
Accuracy should be reported by forecast horizon when the practical question distinguishes, for example, next-month forecasts from forecasts three months ahead. If there is just one holdout origin, there is only one error at each horizon. A collection of errors pooled across different horizons is not the same thing as an estimate of accuracy at any one horizon. Multiple forecast origins allow repeated errors to be summarized separately at each horizon.
Worked Example: Computing Holdout Errors
Continue the synthetic AR(1) example. Suppose the first three holdout observations are \(0.900\), \(0.500\), and \(0.200\) percentage points. The forecasts made at the original training endpoint were \(0.740\), \(0.644\), and \(0.5864\) percentage points. The errors are
The absolute errors are \(0.160\), \(0.144\), and \(0.3864\) percentage points. Across these three different horizons, their pooled MAE is
The pooled RMSE is
These two numbers summarize this particular three-error set, but they mix one-, two-, and three-month-ahead forecasts. They should not be presented as horizon-specific accuracy. For instance, the one-month-ahead absolute error here is \(0.160\) percentage points; it is not an estimate based on repeated one-month-ahead errors.
Worked Example: Comparing Accuracy Separately by Horizon
To illustrate horizon-specific summaries, suppose a second synthetic evaluation uses three rolling forecast origins. The table gives forecasts and actual observations for one- and three-month-ahead predictions. Each error is calculated as actual minus forecast, in percentage points.
| Horizon | Origin | Forecast | Actual | Error |
|---|---|---|---|---|
| 1 month | 1 | 0.70 | 0.90 | 0.20 |
| 1 month | 2 | 0.60 | 0.50 | -0.10 |
| 1 month | 3 | 0.55 | 0.45 | -0.10 |
| 3 months | 1 | 0.50 | 0.20 | -0.30 |
| 3 months | 2 | 0.40 | 0.60 | 0.20 |
| 3 months | 3 | 0.35 | 0.25 | -0.10 |
At one month, the absolute errors are \(0.20\), \(0.10\), and \(0.10\). Therefore,
At three months, the absolute errors are \(0.30\), \(0.20\), and \(0.10\), giving
For these hypothetical origins, errors are larger on average at the three-month horizon. This is a descriptive comparison on the specified evaluation sample, not proof that every future three-month forecast will be less accurate. The origins and holdout design should be representative of the forecasting task of interest.
Common Pitfalls and Reporting
A forecast evaluation is only as informative as its design. The training period should be long enough to estimate the candidate models, while the holdout should represent the future period the user cares about. If the economic process may change substantially over time, a single old holdout may be a poor guide to current performance. In that situation, rolling-origin evaluation can provide a more informative record, while still ensuring each forecast uses only information available at its origin.
- Using the holdout to select the winner. This turns evaluation data into training information. Choose the model on training data, then report its holdout performance, or explicitly describe a separate validation scheme.
- Reporting only an overall error. A pooled MAE or RMSE can hide that performance varies with the forecast horizon. Report horizon-specific measures when horizons matter.
- Treating a wide prediction interval as a poor point forecast. Point accuracy and uncertainty are different summaries. Assess forecast errors and interval coverage or width for their distinct purposes.
- Reading a diagnostic p-value as proof. A nonsignificant residual test does not establish that every assumption holds; it only fails to find evidence against the tested feature at the available sample size and lags.
- Changing the analysis after seeing the outcome. Any such change should be disclosed, since the reported performance is no longer an untouched holdout assessment.
Check Your Understanding
Answer these questions using the definitions and examples above.
- Why must model selection be completed without examining the holdout outcomes if the holdout is intended to evaluate predictive performance?
- For an AR(1) with \(\hat{\mu}=2\), \(\hat{\phi}=0.5\), and final training value \(y_T=4\), calculate the one-step forecast.
- What does a positive forecast error mean under the definition \(e=y-\hat{y}\)?
- Why is a pooled score across one-, two-, and three-month horizons not a horizon-specific accuracy measure?
- Give one reason a model with the lowest AICc might still be unsuitable for forecasting.