Budgeting

A budget is a promise with a feedback loop. Build from drivers, give every line an owner, and review variance on a calendar — not a crisis.

When to use

• Annual/quarterly operating budgets; new business lines; personal budgets.
• Variance reviews and re-forecasts.
• Designing how money decisions get approved.

Method

1. Scope first: operating vs capital vs personal; entity and currency; what the budget governs (and what it doesn't).
2. Structure with owners: cost centers/lines each with a named owner — lines without owners become orphaned spending.
3. Approach per line: zero-based for new/volatile areas (justify from scratch); incremental for stable ones (last + delta with reasons) — state which you're using.
4. Build from drivers: headcount × rate, units × cost, usage × price — not flat percentages; drivers make variance diagnosable.
5. Revenue side: link to revenue-management and forecasting — budgets balance against expected income, not hope.
6. Contingency explicit: a visible line sized to identified risks; hidden padding is forbidden (project-budgets for jobs).
7. Approve & lock the baseline: revisions re-approved, not drifted; approval thresholds documented.
8. Monitor: monthly budget vs actual vs latest forecast; variance thresholds trigger written explanations + actions; rolling 12-month forecast where things move fast.
9. Close: annual true-up; carry-over rules decided; lessons to next cycle.

Quality gates

• Every line has an owner; drivers documented.
• Contingency explicit; approval thresholds set.
• Monthly variance process running with actions.
• Rolling forecast cadence set where volatility demands.

Red lines

• No hidden padding; no silent reallocations; actuals never edited (corrections annotated with date + reason).

Related

project-budgets (job-level) · forecasting · revenue-management.