Recursive vs Direct Multi-Horizon Forecasting
There are two fundamentally different ways to forecast 10 steps ahead: feed each prediction back in as the next input, or train a separate model for every horizon directly — and the choice trades error compounding against wasted structure.
Prerequisites: Sliding-Window Supervision for Time Series, Teacher Forcing and Exposure Bias
Forecasting one step ahead is straightforward: train a model that maps recent history to the next value. Forecasting ten steps ahead is not obviously the same problem, because there is no ground truth for steps 2 through 10 available at prediction time the way there is for step 1. Two genuinely different strategies exist for extending a one-step model into a multi-step one, and they aren't just implementation details — they trade off error compounding against structural mismatch, and the wrong choice quietly costs accuracy no amount of tuning fixes.
The analogy: dead reckoning versus pre-planned waypoints
A ship without GPS can navigate by dead reckoning: at each moment, use your current estimated position plus speed and heading to estimate the next position, then repeat from that new estimate. Simple, and it works — but any error in one estimate feeds the next one, so small errors compound the further you sail. Alternatively, a navigator could instead plan a fixed set of waypoints directly from the start — "in 2 hours here, in 4 hours here, in 6 hours here" — each computed independently from the current known position. That avoids compounding, but a waypoint 6 hours out is a much harder, noisier estimate to make directly, and the waypoints aren't guaranteed to be consistent with each other the way a dead-reckoned path automatically is.
The mechanics: recursive versus direct
Recursive (also called iterated) forecasting trains one model for one step ahead, then applies it repeatedly, feeding each output back in as if it were an observed input:
In words: the same one-step model is reused times, and from the second application onward it's fed its own previous predictions instead of real data — exactly the mechanism behind Teacher Forcing and Exposure Bias, so recursive forecasting inherits that compounding-error problem directly.
Direct forecasting instead trains a separate model for each horizon , each mapping the same known history straight to that specific future step, with no model's output feeding another model's input:
Every conditions only on real, observed history — no self-generated inputs, so no error compounding across horizons. The cost is that each must learn the harder, noisier task of predicting further into the future directly, and because the models are trained independently, nothing forces and to be mutually consistent (e.g. a monotonically rising true series could get a non-monotonic multi-horizon forecast).
Worked example 1: compounding error under recursive forecasting
Suppose a one-step model has RMSE of 2 units per prediction, and errors behave roughly independently step to step. Recursively forecasting 5 steps ahead means the 5th prediction is built on 4 previous predictions, each carrying its own error that feeds into the next. If errors added in quadrature (a simplification, but illustrative): — more than double the one-step error, purely from compounding, even though the same model with the same one-step accuracy is used throughout.
Worked example 2: direct forecasting's independent-horizon cost
Now suppose training data gives 10,000 examples total. A recursive approach uses essentially all 10,000 to train its single one-step model. A direct approach with a 5-step horizon must split effort across 5 separate models , and 's task (predicting 5 steps out from only currently-known data) is inherently harder to learn well with limited data — direct forecasting's later-horizon models can end up less accurate than a well-tuned recursive one, purely because each sees a harder mapping and gets no help from the others.
Watch how a single simulated path that updates its own state each step resembles recursive forecasting, while several independent snapshots at fixed future times resemble direct forecasting's lack of inherited error.
What this means in practice
Neither strategy dominates: recursive forecasting is preferred when the one-step model is highly accurate and horizons are short (error compounding stays small), direct forecasting is preferred when horizons are long or the underlying dynamics change with horizon (e.g. a demand model where the drivers of next-week versus next-quarter demand genuinely differ). Architectures like N-BEATS Interpretable Forecasting and DeepAR Probabilistic Forecasting actually offer a middle path — a single model producing an entire multi-step output block at once (sometimes called sequence-to-sequence or "multi-output" forecasting), sidestepping both pure recursion and fully independent per-horizon models.
Recursive forecasting reuses one model repeatedly, feeding each prediction back as input — simple but prone to compounding error over the horizon. Direct forecasting trains an independent model per horizon from real history only — no compounding, but a harder learning task per horizon and no guaranteed consistency across horizons.
Practice
- If a recursive model's one-step RMSE is 3 and you model error accumulation in quadrature over 4 steps, what is the approximate 4-step RMSE?
- Give one concrete forecasting scenario where direct forecasting's independence from compounding is worth its harder per-horizon learning task.
- Explain why a direct-forecasting approach's outputs across horizons are not guaranteed to be mutually consistent.
The common confusion is assuming direct forecasting is strictly "safer" because it avoids compounding error. It trades one problem for another: each direct model must learn a harder mapping with the same amount of data, and with limited training data the later-horizon direct models can end up less accurate overall than a well-behaved recursive model, despite having no compounding-error mechanism at all. The right choice depends on horizon length, data volume, and how much per-step error tends to compound for the specific series — it is an empirical question, not a rule to apply blindly.
Related concepts
Practice in interviews
Further reading
- Taieb & Hyndman, A gradient boosting approach to the Kaggle load forecasting competition (2014)
- Salinas et al., DeepAR: Probabilistic Forecasting with Autoregressive Recurrent Networks (2020)