The 60-second briefing that gets your board to vote

You already know the wastewater plant's whole story: the clarifier's mood on a hot afternoon, the blower amp draw creeping up, the smell that tips you off before any alarm does. Stand up in front of the board and that story is what comes out, twenty minutes of it. Somewhere around minute four, the board's eyes go somewhere else.

That's not a communication quirk you can fix by talking faster. Small boards already fight decision paralysis, too many people trying to weigh in on every decision before anyone actually decides. A long technical briefing hands the board more to weigh in on, not less, and the vote never comes.

The fix isn't a shorter version of the same briefing. It's a different one, built for what a governing body needs to vote, not for what an operator needs to understand. Rung 3: facing the board.

Who actually decides, and why that changes what you say

The board governs. Staff, including you, operate. Governance is the "what" and "why" of the utility, policy, strategy, budget, oversight, while operations is the "how."

When you brief the board, you're crossing that line for exactly as many minutes as it takes to hand a decision over, then stepping back across it.

That decision doesn't belong to any one board member. A board acts as a single body: authority comes from motions and votes, and no individual, not even the chair, can approve your ask alone.

In the language boards use for role clarity, the board is Accountable. Accountable means one name, or the buck never stops. A briefing built around that fact gives the whole body one clear thing to vote on, not five people to win over one at a time.

That's also why the number matters more than the narrative. Financial stewardship, approving budgets, setting rates, funding infrastructure, is usually a board's most time-consuming duty, and it's the area where board members carry the most personal liability exposure. When a board member asks "how much" before "how it works," that isn't impatience, it's the job.

The five things a decision-maker needs

A board member sitting through your briefing needs exactly five things, in this order. Everything else is background, or it can wait for a follow-up email.

• What. Name the decision, not the symptom. "Lift station 3's pump needs board authorization to replace" is a decision. "We've had some pump trouble" is not.
• Why now. The one fact that makes tonight different from six months ago: a condition rating, a trend line, a failure that already happened once.
• Cost. An actual number, even a rough one. Preliminary cost estimates run 30 to 50 percent off in either direction, and that's still more decision-ready than no number at all.
• Risk of no. What happens, and by when, if the board takes no action. Not a scare tactic, a fact: repairs cost more than replacement.
• Recommendation. Your one answer, not a menu. Staff do and advise the work; the board is accountable for it, and a recommendation with no name behind it is exactly how decision paralysis starts.

The 60-second structure

Say it out loud, with a stopwatch, before you say it to the board. If it runs long, the fix is always to cut, never to add more background.

• The number: open with the fact that defines the decision. Not a greeting, not context, the number.
• Why now: one sentence connecting that number to a consequence, not a description of how the equipment works.
• Cost and source: the dollar figure, and where it comes from, rates already collected, a loan, a grant application.
• The ask: the specific motion you want on the record tonight. One name, one number, one deadline.

Four sentences. If you can't say your ask in four sentences, you haven't finished deciding what you're asking for.

A worked example: the lift station pump

Say the pump at Lift Station 3 in the City of Everytown rates a 4 on the condition scale (significant deterioration, risk of failure) and a 4 on criticality (severe: major disruption, high repair costs), the same band a pump station or treatment unit sits in. Multiply the two and you get a risk score of 16, inside the 12-to-20 band the scale calls high risk: immediate planning for replacement, not routine maintenance.

The cost comes straight from the asset inventory, not from memory. One small system's pumps-and-motors category runs about $100,000 across five units on a 5-year life, funded through roughly $20,000 a year in reserve. If that reserve line has been funded, the replacement is already paid for in rates on file and the vote is a formality; if it hasn't, the gap between what's saved and what's needed is the number the board needs to hear, not a paragraph about impeller wear.

Why now isn't a guess, either. Portland, Oregon once caught a failing pump-station control early and replaced just that part for $1 million instead of a full $6 million overhaul, because the utility already knew which piece was going.

Pennichuck, New Hampshire serviced one hydrant more than five times, about $6,600 a visit, roughly $33,000 total, before switching to scheduled inspection instead of repeated patchwork. Both stories point the same direction: catch it while it's a repair decision, and it stays cheap. Wait past that point, and it becomes an emergency decision, and emergency decisions are never cheap.

The manager's job in the meeting is not to retell either story. It's to say: this pump is a 16, the reserve does or doesn't cover it, and the recommendation is to authorize replacement now.

What kills a briefing

These are the patterns that turn a routine vote into a tabled item.

• Twenty minutes of narrative and no number at the end. The board can't vote on a story.
• A cost that stays a word instead of a figure, "significant," "substantial." Even the roughest estimate is more useful than an adjective.
• No recommendation, or three options with no lean. Multiple open options invite the same decision paralysis that fuzzy roles cause everywhere else on a small board.
• Bringing the item "for discussion" instead of "for a vote." Deferring tough decisions is a named failure of small boards, and it doesn't make the eventual number smaller. It makes it bigger.
• Skipping the reserve math. A budget can look healthy, projects finished, cash in the bank, and still be losing ground once depreciation is counted. A board that never sees that number can't act on it.

Before you walk in

Run this before the meeting, not during it.

• Have your number, a risk score, a percentage, a dollar figure, before you write a word of narrative.
• Write the recommendation first. Build backward to the three sentences that justify it.
• Know whether the cost is already covered by reserve or needs a new source: a rate adjustment, a loan, a grant.
• Remember the vote belongs to the board as one body. You're handing off a decision, not lobbying five people one at a time beforehand.
• Bring the risk-of-no side: what happens, and by when, if nothing gets decided tonight.
• Time yourself reading it out loud. Sixty seconds, or cut it.

A tight briefing gets you a vote. It doesn't guarantee a yes on the first try.

Next on the ladder: Handling the objections boards raise.