Answer your board's budget objections before they raise them

You know the meeting before it happens. You put a number on the screen, and before you finish explaining it, a board member says "didn't we just fix that." It's followed by "why does this cost so much," "can this wait until next year," and what the system down the road charges. Same four questions, project after project, year after year.

None of that means the board is being difficult. A board member is trusted to manage a utility meant to serve the community for a hundred years or more, spending money that isn't theirs. Rates and capital spending aren't neutral numbers to them; they reflect what the board decided the community's water is worth. Every one of those four objections has a real question buried in it, and the answer is almost always sitting in your own records already.

Four objections repeat at almost every budget meeting, each one hiding a real question underneath the words, and your own system's numbers answer every one of them better than a general argument. Also rung 3, facing the board.

The four objections you'll hear at every budget meeting

Board pushback tends to repeat itself. The same four objections show up at almost every system, almost every year: we just fixed that, why is this so expensive, can this wait, and the neighbors charge less. Rehearsing the pattern behind each one, once, saves you from reinventing the answer live in a meeting.

The pattern is the same for all four. A board member is voicing a legitimate concern in compressed, informal language. Your job isn't to argue the concern away. It's to translate it back into the specific number that answers it, using the system's own data instead of a feeling.

"We just fixed that": is this really the same ask twice

This objection is really asking whether you're bringing back a request the board already paid for, or a new item that only looks similar. The honest answer usually depends on whether you have a written, dated capital plan the board can check against.

A capital budget should equal the depreciation of all the system's assets, plus at least 10% (sometimes called the 1.1 replacement ratio). That isn't a one-time number tied to a single repair. It's a recurring annual figure that funds the next item on the list, not a repeat of the last one. If you can point to a dated capital plan and show the board this is a different asset, or the next scheduled phase of the same asset's life, "we just fixed that" usually resolves on the spot.

Sometimes the objection is fair, and it points to a real problem: a repair that wasn't done right the first time. One small system held rates flat at $30 a month for more than 25 years and called that a win, until the underinvestment caught up: 70 repairs in three years, including a stretch of main that was never installed correctly, patched with the wrong parts, and kept failing in the same spot. One midnight repair had the operator chasing $1,000 pipe clamps the system had never kept in stock. A comparable system nearby that replaced pipe steadily over 20 years is twice the size but has roughly a tenth of the breaks. The lesson isn't "don't fix it again": a small parts inventory and a real installation standard cost less than repeat emergency calls.

"Why does this cost so much": are we being overcharged

This objection is really asking whether the number in front of the board is reasonable, or whether the system is being taken advantage of. The honest answer is almost always the math of running a small system, not a bad price.

Vendors bill per system, not per connection. A district with 180 connections can pay close to the same monthly fee for a piece of core software as a utility with 4,000 connections, which comes out to about 22 cents per customer versus roughly 1 cent. Small utilities also see pipe-break rates at least double those of large utilities, because there's no redundancy to absorb a bad week.

Rural systems maintain far more pipe per customer than a city grid, too: the national average runs around 308 people per mile of main, while some rural Arizona systems run closer to 25 people per mile, a tenth of the customer base defending the same mile of pipe. None of that is padding. It's the fixed cost of a small footprint, spread across a small number of bills.

"Can it wait a year": what waiting actually costs

This objection is really asking whether deferring the decision is free. It isn't, and you can show the board the price of waiting in dollars.

The arithmetic of waiting is the part that lands. Two systems can arrive at the very same rate years from now and collect very different money getting there. The one that steps up a little each year banks revenue the whole way. The one that holds flat and then catches up collects nothing extra in the meantime, and it has to ask for the entire increase in a single vote.

Ask your circuit rider or state rural water association to run that comparison on your own numbers. The two paths end at the same bill, and the gap between them is money the system never collected. A board that sees the two lines side by side usually stops asking why not wait.

Waiting can also carry a financing cost. If deferring a project means borrowing for it later instead of building reserves now, a $1 million loan over 20 years at 4% interest adds $440,000, and that cost still has to come from rates eventually. A reserve target of roughly 200 days of operating expenses exists so a system isn't forced into that loan the moment a project genuinely can't wait any longer.

"The neighbors charge less": why rates differ from system to system

This objection is really asking whether your system is being run less efficiently than the one down the road. Usually it isn't; it's being shaped by different local conditions.

A comparison across several small Arizona systems found the monthly cost of the same 4,000 gallons ranging from under $30 to over $70, even among comparable rural districts, because local infrastructure age, source type, debt load, and terrain all differ. There's no single number two neighboring systems should share. It's also worth checking what a lower rate down the road actually buys before assuming it's the better deal: in one national comparison, systems billing around $15 a month averaged 93.9% health-based compliance and 68.4% management compliance, while systems around $75 a month hit 98.9% and 85.9%. A cheaper bill sometimes means thinner reserves and skipped maintenance, not better management.

Bring the board your own cost-of-service math, fixed cost per customer plus the variable cost per thousand gallons, instead of letting a neighbor's sticker price set the standard.

Build the answer packet before the meeting

Rehearsing the four patterns above only works if the numbers are ready when the objection lands. Before the next budget or rate meeting, put together:

• a dated, written capital plan, so "we just fixed that" has a one-page answer

• your fixed cost per connection and pipe-miles-per-customer figures, so "why so expensive"

• an eight-to-ten-year rate projection showing gradual increases against a do-nothing

• your own cost-of-service worksheet and current reserve balance against your target, so "the

has a real comparison behind it scenario, so "can it wait" has a dollar figure attached neighbors charge less" has your system's numbers instead of theirs

None of this needs to be fancy. A one-page summary of each, updated once a year, turns a defensive scramble into a five-minute answer the board can actually weigh.

Where this goes next

Handling the objection is only half the job. Asking for the money in the first place, and asking for it well, is the other half. Next on the ladder: Asking for money: grants, rates, and reserves.