The budget and what actually happened

The problem it solves

A budget usually gets built by taking last year and adjusting it for what the next one is expected to bring. It is approved in December with a certain amount of ceremony, consulted once in January, and by March nobody opens it. It never got compared against the bank statement while there was still time to correct something, which is the only window in which a budget helps you steer instead of helping you explain.

The symptoms are easy to recognize. Managers accountable for a budget they had no hand in building and therefore do not defend. Spending approvals that all climb to the owner, who signs nearly everything because refusing takes a conversation there is no time for that week. Recurring charges nobody has reassessed since the day they were contracted, services that renew themselves, and a miscellaneous line that grows quietly because no one claims it.

Then revenue falls short and the cut is applied evenly, which is the tidiest possible way to damage what was working and protect what was not. Something slower and more serious happens alongside it: the budget loses authority. After a year of variances nobody examined, next December's exercise is done for form's sake, with numbers everyone in the room knows will not guide a single decision.

What it covers

The workshop starts with where the figures come from, because a budget built on last year repeated inherits every error in it and cannot be argued with. Participants identify the real drivers of their operation, the units, the billable hours, the routes, the shifts or the seats filled, and build the lines from those. Structured that way, every assumption is visible and can be discussed with the person who proposed it, which is the difference between a budget and a wish arranged in columns.

The second block separates fixed, variable and discretionary costs, a classification that looks elementary until it meets actual line items. In a group exercise participants sort their own lines and argue over the ones that resist, because what the company will be able to move when it needs to move something depends entirely on that sorting. The budget is then assembled area by area with a named owner, under the rule that nobody answers for a figure they did not help build.

The core of the session is the monthly variance review, which is what turns the document into an instrument. The group defines who sits in it, how often, what gets looked at first and what each kind of variance calls for: some only require an explanation, some require action this week, and some are telling you the assumption was wrong and the budget needs correcting rather than the operation. A full review is rehearsed on worked figures, including the uncomfortable part, which is asking about someone else's line.

The closing block sets rules built to survive a busy week: spending limits by level, who approves what, and the amount above which someone else has to be consulted. Through scenario analysis, each company also builds its own cutting order, the written list of what gets touched first, second and third when the revenue does not arrive, decided calmly now instead of under pressure later.

What participants learn

• Build the budget from the operation's real drivers rather than from last year repeated.
• Classify costs as fixed, variable or discretionary, and determine which ones can genuinely move.
• Implement a monthly variance review with an owner per area and a defined action for each type of variance.
• Define spending limits and approval levels that do not depend on the owner's signature.
• Prioritize what gets cut first when revenue falls short, instead of cutting evenly across the board.

Agenda

1. 01Where the assumptions come from, and who answers for them
2. 02Fixed, variable and discretionary costs
3. 03The budget by area, and its owner
4. 04The monthly variance review, and what each variance calls for
5. 05Rules, limits and approval levels
6. 06Recurring charges nobody has re-examined
7. 07What to cut first when the revenue does not arrive

What the organisation leaves with

• A budget structure by area, with a named owner and the drivers each line is built from.
• The monthly variance review defined in writing: who takes part, on what date, and what each type of variance requires.
• A table of spending limits and approval levels naming who approves at each one.
• A written cutting order, decided before it is needed, setting out what gets touched first and what is left alone.