Working for a board without losing the plant

A board member calls your operator directly to ask why a work order hasn't closed. Another shows up at the shop with a strong opinion about which pump to buy. Neither habit is yours, but you're the one who has to fix it.

You sit between the people who vote on the budget and the people who keep water moving. That's the part of the job nobody certifies you for.

You spent years learning chlorine residuals and pressure zones. Nobody handed you a manual for the moment a board member starts running your crew from a lawn chair.

The fix isn't a bigger argument. It's a clearer map of who decides what, plus a few habits that keep both sides out of each other's way.

Rung 4 of the manager track.

What the board actually decides

A board's job comes down to five things: follow the law, set policy, pass a budget, hire the top operator, and keep records. Everything else gets delegated to the people who run the place day to day.

That's a short list. It doesn't include picking a pump model or approving a routine work order. Deciding which valve gets replaced first is an operating call, not a board call.

Those calls belong with the operator, because that's where the training, the license, and the daily judgment actually sit. The board's five duties brush against operations without controlling them. It sets the budget that buys the pump, not which pump gets bought.

Where you stand in the chain

Picture three boxes stacked in order. The board sets direction. You turn that direction into staffing and a working budget, and the operator executes it.

Each box does its own job and stays out of the next one's. When a board member calls your operator about a work order directly, that call skips a box. It's rarely malice.

More often it's just habit. Maybe the system used to be smaller, or the board member used to do the work themselves. Sometimes nobody ever explained that there's a chain to follow.

The plainest fix is a standing rule, stated once, calmly, to the whole board: operational requests come to you first. You relay what needs relaying and protect the operator's time for the actual work. This isn't about guarding turf.

A board member who reaches straight past you on a bad day puts you in a weaker spot with your own crew. Next time, the operator won't know whose direction to follow.

A one-page grid beats a hundred arguments

Fuzzy roles show up as the same three headaches everywhere: decisions that never seem to close, approvals that drag for weeks, and complaints the board hears about before you do. A simple chart fixes most of it.

The chart is called a RACI grid. It's one page, with four columns.

Responsible names who does the work. Accountable names who makes the final call, one name only, or the buck never stops. Consulted names who gets asked before work starts, and Informed names who simply gets told once it's done.

Build one in an afternoon. List the recurring tasks down the side: a leak repair, budget prep, a boil-water notice, hiring a contractor. Across the top, drop just one or two letters per cell.

Take a boil-water notice as an example. The operator is Consulted and Informed, billing staff is Responsible for getting word out, the board is Accountable and Informed, and customers are Informed once it's live.

Two warning signs to check for once the grid is built. A cell with two Accountable names means nobody actually owns that decision, and it will stall. A cell with no Responsible name means the task quietly won't get done.

Both gaps are exactly what pulls a board member into your operator's lane. Someone has to fill the hole, and the board is often the one standing closest to it.

The other half of this exercise is a single number. It's the highest dollar amount the operator can spend without coming back to the board first.

Here's a rough check on that figure: about $1,500, roughly the cost of a routine chlorine pump. If your number sits under that, it's probably too low for an actual emergency. Write it down, and raise it if it's forcing a call that should be automatic.

Speaking with one voice

A board acts as a single body. No individual member, including the chair, can bind the utility alone. Authority comes from a vote of the full board, recorded in the minutes.

Once the board votes, it's the board's decision. Every member backs it in public, even the ones who voted no. Members can argue hard at the table, but outside the room, the vote stands.

This matters to you directly. If a board member gives your operator an instruction the full board never voted on, it carries no more weight than a customer's opinion. You're allowed to say so, kindly.

"I hear you, and I'll bring that to the board" is a complete answer. It respects the member, keeps the operator out of conflicting orders, and puts the decision back where it belongs.

When the board leans into your lane

Most overreach isn't hostile. It's usually a board member trying to help, trying to save money, or genuinely worried about something they noticed. Treat it that way, and most of it defuses on its own.

A board member who wants to pick the pump or reset a chlorine feed usually isn't trying to overrule you. They just haven't thought through what that decision actually requires. Say it plainly if you need to.

"That call has to stay with the certified operator," you can say. "It's what the training and the license are for." Most people step back once they hear it laid out plainly.

When it doesn't stop, take the conversation out of the room where it started. A quiet word with the chair works better than a public correction.

So does a short agenda item that walks the board through the RACI grid and the operator's spending limit. You're not trying to win the exchange. You're trying to get the lane markers back where they belong, so the next call doesn't happen at all.

The report that keeps everyone calm

The best defense against a board reaching into operations is giving it somewhere else to look. A standing monthly report gives the board what it's actually after.

That means water produced against water sold, repairs and outages, test results, complaint counts, and budget status. It's the information a board member is usually chasing when they start asking operational questions.

Delegate, then monitor, rather than delegate and disappear. When something in the report looks off, an engaged board asks why: water loss ran high this month, what happened. That question lets you and the operator bring back the answer, not the board reaching for the fix itself.

That's oversight without a hand on the wrench. A board that trusts the report stops needing to call the shop floor to find out what's going on. Build the grid, hold the line on the chain, and send the report every month without being asked.

Most of the friction in this job comes from boards that never got either one. For more of the manager track, head back to the Field Guide.