Skills on AI

Active theme: Light

Budget Forecasting

Use when asked to build or maintain a budget forecast — the ongoing, continuously updated projection of future income and expenses against actuals — as distinct from a budget itself, which is a fixed plan or target set for a period rather than a live projection.

Budget forecasting is the ongoing practice of projecting future income and expenses and updating that projection as real numbers come in. A budget is a plan: a target set for a period, usually fixed once approved. A forecast is different — it's a living projection that tracks how actuals are diverging from that plan and updates the expected outcome accordingly. Confusing the two is the single most common failure in this practice.

Key components

  • Baseline and starting assumptions — the initial numbers and the assumptions behind them (growth rate, hiring plan, seasonal pattern), stated explicitly so they can be checked and revised later rather than buried in a spreadsheet formula no one remembers the logic for.
  • A regular update cadence — a fixed rhythm (monthly is typical) for refreshing the forecast with actual results, rather than revisiting it only when someone asks.
  • Variance tracking — the gap between what the budget planned and what the forecast now expects, tracked explicitly so stakeholders can see not just the current number but how far it's drifted and why.
  • Scenario ranges — a best-case, expected-case, and worst-case range rather than a single point estimate, since the further out the forecast looks, the less confidence any single number deserves.

Common pitfalls

  • Forecast built once and never revisited — a forecast that isn't updated as actuals come in is really just a second copy of the original budget, and stops doing the one thing a forecast is for.
  • No distinction between the fixed budget and the live forecast — when stakeholders can't tell which number is the original plan and which is the current projection, they end up either alarmed by normal variance or blindsided when the two have quietly diverged.
  • Overly precise point estimates presented with false confidence — a forecast stated as a single exact figure (rather than a range) implies a level of certainty the underlying assumptions don't support, and makes normal variance look like a forecasting failure later.
  • Variance tracked but never explained — a number that shows the budget and forecast have diverged is only half useful without a note on why (a vendor cost increase, a hiring delay, a revenue shortfall).
  • Forecast owned by no one in particular — like an unowned vendor relationship, a forecast nobody is accountable for updating quietly goes stale.

Learn more

  • ROI Analysis for evaluating whether a specific initiative's projected return justifies its cost, a related but narrower calculation than an overall budget forecast.
  • Vendor Management for tracking a specific category of recurring cost (vendor spend) that regularly feeds into a forecast.
  • Break-Even Analysis for a related projection technique focused on the point where cumulative revenue covers cumulative cost.
  • Unit Economics for the per-unit cost and revenue assumptions that often underpin a forecast's baseline.

View budget-forecasting/SKILL.md on GitHub