---
name: budgeting-and-forecasting
description: Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.
---

# Budgeting and forecasting

## The budget is a commitment, the forecast is a belief

Keep them separate. A budget re-cut every month is not a commitment; a forecast held to the original
budget is not a belief. Both failures make the numbers useless for different reasons.

## Running the cycle

1. **Set the frame first** — targets, headcount envelope, and the assumptions everyone builds on
   (pricing, attrition, timing). Distributed teams building on different assumptions produces a
   consolidation that cannot be reconciled.
2. **Collect in a fixed template.** Free-form submissions cost more to normalize than to build.
3. **Challenge the inputs**, specifically: what is the volume driver, what is this per unit, what
   happens if it comes in at half. Budget submissions are negotiating positions and should be
   treated as such without hostility.
4. **Consolidate and find the gap** between bottom-up and top-down. There always is one. Close it
   explicitly by cutting something named, not by proportional trimming — proportional cuts damage
   the highest-return line as much as the lowest.
5. **Publish what was not funded** and why. This prevents the same request arriving three times.

## Rolling forecast

Re-forecast on a fixed cadence over a constant horizon. Update only what has changed and say what
changed and why. A re-forecast with no narrative is a new set of numbers with no information in it.

## Variance analysis

Variance is only useful decomposed. For each material variance, separate:

- **Volume** — did we do more or less of it?
- **Rate** — did each unit cost or earn a different amount?
- **Timing** — did it move between periods, or is it gone?
- **Mix** — did the composition shift?

Timing variances need no action and are constantly mistaken for performance. Rate variances on
recurring costs compound and are constantly under-reacted to.

Explain the top few by value, not every line. A variance report covering everything gets read as
nothing.

## Sources

`references/sources.md` in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.

## Tooling

Planning: Anaplan, Pigment, Workday Adaptive Planning, Vena, Cube, and similar. A
well-built spreadsheet on a clean chart of accounts beats a planning tool nobody has been
staffed to maintain; move when budget owners outnumber the people who can hold the model
in their head.

Driver data comes from the ledger, the CRM, and the HRIS. The planning tool is only ever
as current as those connections.

## Never

- Present a forecast without saying what changed since the last one.
- Let a department own an assumption that drives another department's numbers.
- Report accuracy without measuring it. Track forecast error over time — it improves quickly once
  visible and never improves while unmeasured.