Building a budget that tells the truth

You inherited a budget nobody built on purpose. Last year's total, plus a percent for inflation, has been the whole method for years. Nobody has checked it against what the system actually costs to run.

That works fine until someone asks you to defend it. A board member wants to know why the capital line is what it is.

A council member wants to know why rates have to move this year and not last year. "It's what we did last year" is not an answer either of them can vote on.

A budget built from the actual work, instead of from last year's total, is one you can walk through line by line. That is the whole difference between a budget and a guess.

Rung 4 of the manager track.

Why last year plus a percent stops telling the truth

Financial management at a small utility means running accounting, policy, planning, budgeting, and oversight as one connected job, not five separate chores. The goal underneath all of it is simple: charge a fair rate that consistently generates enough revenue to cover every expense, short-term and long-term, including reserves.

Breaking even is the floor, not the target. A system that only covers today's bills has nothing left for an emergency, a failed pump, or a facility wearing out.

The Safe Drinking Water Act pushed two ideas onto every small system. Full-cost pricing means charging rates that reflect the true cost of producing and delivering service, including debt and future replacement. Asset management means planning for what your infrastructure will need before it fails.

A budget rolled forward from last year's total tests neither idea. It just assumes last year got the number right. If last year was also copied from the year before that, nobody has actually checked in a long time.

A budget built bottom-up from the real work is the only kind you can walk through and defend. Every number in it traces back to something you can point at.

The four numbers a bottom-up budget runs on

A budget built from the work runs through four numbers, in order. Each one has to be real before you move to the next.

1. Operating expenses. Split fixed costs (salaries, insurance, debt payments) from variable costs (electricity, chemicals, leak repairs). Start from what you actually spent the past two or three years, not what you budgeted. Add in any unplanned emergency spending from that window, then adjust forward for what is already changing: a raise, a new hire, a materials-cost increase, a loan coming online.
2. Asset inventory and depreciation. Inventory what the system owns and work out what it costs to replace, spread across its useful life. This is where depreciation becomes a planning number instead of just an accounting entry. What you are really spending every year on a pump or a tank is its replacement cost divided by how long it lasts, whether or not a check gets written for it this year.
3. Capital improvement plan. Build the board's ranked list of what needs major repair, rehabilitation, or replacement, covering at least the next ten years. Is the system nearing design capacity? Does skipping an upgrade risk a regulatory violation? What can the system pay for from its own resources, and what needs a loan, bond, or grant? Bring in a consulting engineer for real cost estimates on anything major; a guess here undermines every number downstream.
4. Revenue requirement. Add the first three together and you get the total the budget has to generate to cover operations, debt, and capital. That number is the honest answer to what the system actually costs. How it turns into an actual rate on an actual bill is a separate decision for the board.

Line up these four numbers against your chart of accounts, category by category. Now you have a budget you can explain to anyone who asks. That is what bottom-up means in practice: every line traces to a real input, not to last year's line with a percent stapled on.

The reserves step most systems skip

Most history-based budgets skip a line entirely: money set aside for what is coming, not just what is due today. Adding that line is what turns a budget from a bill-paying exercise into an actual financial plan.

Start with a floor. The capital side of your budget should cover the full depreciation of everything the system owns. Add roughly 10% on top of that.

If your capital line is smaller than that, you are not funding replacement. You are deferring it onto a future budget and a future rate increase. A quick check is worth running every year: does the capital number in front of you resemble what your asset inventory says is wearing out, or is it just whatever was left over after everything else got paid?

You do not need a finished reserves policy to take this step in the budget. You need two numbers. What does the capital improvement plan say is coming in the next several years, and what has unplanned emergency work actually cost the system recently?

Put both into the budget as a real line, not an afterthought. Sizing the reserve, choosing the accounts, and writing the policy for using and refilling it is worth its own guide.

Making sure the number actually balances

A budget only counts as built when it balances. Expenses, including debt service and reserve transfers, cannot exceed revenue. If they do, you have a revenue problem, not a budget problem, and that is a question for the board about rates, not something a budget alone can fix.

Before you call it finished, run a projected cash-flow check against it. A budget can balance on paper for the year and still leave you short of cash in one month.

That happens when a big capital outlay or loan payment lands before the revenue meant to cover it arrives. Confirming the cash will be there when a bill is due is separate from confirming that the year adds up on paper.

Getting it adopted, then watching it work

Start the budget well before the fiscal year begins. The governing body should adopt it at least 30 days ahead of the new year. That means the four-step build needs to start months earlier, not the week before the vote.

Adoption is not the finish line. The board should get a monthly report comparing actual revenue and expenses to the budget, line by line.

Nine months into a twelve-month year, each line should be tracking near 75% of its annual figure. A line running well above or below that deserves a question, not a shrug.

This is the payoff of building it bottom-up. Every number in that monthly report traces back to something real: a wage rate, a replacement schedule, a capital plan item. You can explain a variance instead of just noting one, and that is what "defend it line by line" actually looks like in a board meeting.

If the real numbers change mid-year, a wage increase, a new grant, a broken pump, amend the budget and have the board vote on the change. A budget you never touch after adoption stops being a plan. It goes back to being a guess, just a more recent one.

Reading your utility's money walks through the statements a budget like this one feeds, so you can watch the plan turn into real numbers month over month. For more guides built for people running the business, start at the manager track.