Look-Ahead Bias

Look-ahead bias is time travel in a backtest. The simulation, at some historical decision point, consults information that did not yet exist — and the resulting performance is not a forecast of anything, because no live deployment can repeat the trick.

The crude forms are easy to name: trading a bar’s close before the bar has closed, or entering at a day’s low as if the low were knowable before the day ended. The subtle forms are where research actually dies. An indicator normalised over the full sample — a z-score using the whole period’s mean and variance — leaks the future into every historical value. Economic data is revised: headline employment and GDP figures are routinely restated in subsequent releases, so a backtest keyed to the final revised series is trading on numbers that nobody possessed on the release date; only vintage, first-print data reproduces what was actually knowable. Corporate financials are restated. Split and dividend adjustments applied retroactively can shift historical signals. Even a dataset vendor’s silent cleaning of bad ticks, applied years after the fact, hands the simulation a smoother past than any live system experienced.

What makes look-ahead bias dangerous is its silence. It produces no error, no warning, and no implausible single trade — only a persistent, unexplained excellence that evaporates in production. It is frequently the hidden engine underneath an apparently robust result, and no amount of walk-forward validation detects it if the leak is embedded in the data pipeline itself.

The defence is point-in-time discipline: every value consumed by the simulation must carry the timestamp at which it became knowable, not the timestamp of the period it describes. That, in turn, requires knowing your dataset’s history — what was captured when, and what has been altered since — which is the concern of tick data provenance and the sibling discipline to defeating survivorship bias.