All resources
Analytics11 December 2025·6 min read

Forecasts are wrong on purpose: how to read a confidence interval before you bet on it

A demand forecast that says '1,200 units' is quietly lying to you. The honest version says a range — and the range is the actual deliverable.

Ask a forecasting model for next month's demand and it will happily hand you a single number. That number is, with near certainty, wrong — not because the model failed, but because point forecasts are always wrong by some margin. The useful output was never the number; it was the range around it, and how that range should change your decision.

What a confidence interval is actually telling you

A forecast of '1,200 units, 80% confidence interval 950–1,500' is saying: if you ran this exact situation many times, the true outcome would fall in that range roughly eight times out of ten. The width of that range carries as much information as the center point — a tight range means the model has seen this pattern before and is confident; a wide range means you're in unfamiliar territory and should hedge accordingly.

Where teams get burned

  • Ordering to the point forecast — stocking exactly 1,200 units when the honest range is 950–1,500 guarantees you'll be wrong in one direction or the other, every time.
  • Ignoring interval width changes — a suddenly widening range is often the earliest signal that something has shifted (a new competitor, a channel change) before the point estimate itself moves.
  • Comparing forecasts without comparing uncertainty — a model that's '10% more accurate' but never tells you how confident it is on a given day is harder to act on than a humbler model with honest ranges.

The right question isn't 'is the forecast right' — it's 'what decision changes if reality lands at the low end of the range versus the high end.' If the answer is 'nothing,' you don't need a forecast; you need a plan robust to both.

What we build so ranges are usable, not just visible

Dashboards that show the interval alongside the point estimate, not buried in a tooltip. Backtests that report calibration — does the true value actually fall inside the stated interval as often as claimed — because a model that's overconfident is more dangerous than one that admits uncertainty. And decision rules tied to the range itself: reorder thresholds set against the low end for safety stock, capacity planning set against the high end for risk.

Related capability

This is what our Predictive Business Intelligence practice is built around.

See how it's scoped