Forecasting

Where AI can genuinely help budget forecasting and where finance teams still need disciplined modeling, assumptions, and human judgment.

TL;DR for operators A multi-step forecast may produce one trajectory, but the model does not necessarily use the same historical evidence for every point on that trajectory. In the real-world trained-model experiments studied here, an explanation assigned to its own forecast step outperformed explanations borrowed from other steps: the median own-versus-mismatched margin was +0.1418, and 80.6% of runs were positive. ...

TL;DR for operators A forecasting benchmark can change the problem being measured without changing the nominal dataset. In the rideshare data examined here, zeros make up 46.9% of the full dataset but only 5.3% of the standard rolling-origin evaluation windows. Under a series-wise split, the evaluation-window zero rate rises to 59.1%, and the interpretation of an autoregressive hurdle model reverses. ...

TL;DR for operators A forecasting dashboard can correctly report that an earlier observation influenced a prediction and still give the wrong impression about how that influence enters the model. Amadeo Tunyi’s paper, The Failures of Marginal Influence-Based Attribution Methods for Global Time Series Explanations, argues that familiar scalar attribution methods cannot in general recover the model’s direct temporal dependency structure.1 Marginal methods can assign importance to an earlier variable whose influence is entirely mediated through a later, autocorrelated observation. Gradient methods can report sensitivity that exists only outside the support of the data the model actually sees. ...

TL;DR for operators EV charging optimization has a small, rude problem: the most important variable is often the one the operator does not know. A plugged-in car may leave in twenty minutes or three hours. That difference determines whether the controller can wait for cheap electricity or must charge immediately like an anxious intern with a deadline. ...

Football is usually explained after the fact. A team “pressed high.” A winger “found space.” A midfield line “lost compactness.” These statements may be accurate, but they arrive with the comforting uselessness of a weather report read after the picnic. The real managerial question is not merely what happened. It is what could have happened if the opponent shifted earlier, if the team protected the half-space, if the attacking line stretched the back four, or if the next pass invited three different futures instead of one. ...

Dashboard work has a familiar little ritual. Someone opens a chart, zooms into the last few points, notices a dip, a rebound, or a suspiciously clean trend line, and then says something that sounds analytical: “Looks like it will continue.” Sometimes that is wisdom. Sometimes it is just a human staring confidently at a squiggle. ...

Data is expensive. Worse, in real scientific and industrial systems, the most useful data is often the data you do not have yet: the failure condition, the rare regime shift, the long-horizon trajectory, the sensor reading after something starts behaving strangely. This is why “just train a larger model” is not always an operating strategy. Sometimes it is only a procurement strategy wearing a lab coat. ...

TL;DR for operators FutureX is less interesting as a leaderboard and more interesting as an operating model for evaluating AI agents that claim to forecast the future. The benchmark runs a live loop: collect future-facing questions from curated web sources, ask agents to predict before the answer exists, wait for resolution, crawl the answer, and score the prior prediction. That matters because most “forecasting” evaluations are either historical backtests with leakage risk or static datasets quietly ageing into trivia. ...

TL;DR for operators Most forecasting teams already have decent numerical forecasters. Their problem is not that ARIMA, ETS, Lag-Llama, Chronos, or internal demand models suddenly forgot how Tuesdays work. The problem is that many important forecast shocks arrive as text: heat-wave notices, maintenance schedules, holiday effects, price caps, promotions, policy changes, store closures, one-off events, and all the other messy little business facts that refuse to fit politely into a clean covariate table. ...