The day it goes wrong in public

You have a boil order out and the phone will not stop. A reporter wants to know if the water made anyone sick. Nobody trained you for this part.

The operator on your crew is doing the technical work right now, isolating the problem and running the notice. Your job starts the moment someone outside the utility asks a question, and whatever you say next is not your opinion anymore. It is the utility's answer, and the town remembers it long after the water clears.

None of this requires a natural talker or a trained press officer. It requires a structure you can lean on when your own head is not thinking straight, and a plan for who says what, decided before the day arrives.

Rung 4 of the manager track.

The operator fixes it, you explain it

One person closes valves, runs samples, and gets the system back to normal during an active event. That is not your seat here. The tiers, templates, and rescind steps for the notice itself belong to the person issuing it, covered in boil-water-notice-and-crisis-comms.

Your seat faces the town. The rule that keeps the two seats from colliding: do not put the person fixing the problem in front of the press. Their hands are full with the fix, and they should not also carry the reporter's questions or the comments piling up on social media.

Someone else carries the public side, and that person is decided in advance, not picked in the parking lot when the news truck shows up.

Where trust breaks down

Most of the damage in a crisis does not come from the outage itself. It comes from how it gets handled. Four patterns do almost all of the damage:

• No message goes out, so people fill the silence with the worst version of the story.

• The message comes late, and a routine problem starts to look like something being hidden.

• The message is too technical or too vague, jargon or a shrug of "cause unknown" that confuses

• The tone is defensive or dismissive, lines like "it wasn't our fault" or "please be patient"

more than it explains. that make people angrier, not calmer.

None of these four are really about the technical event. They are about pace and tone. A message that goes out fast, in plain language, calm and matter of fact, heads off most of the damage before it starts.

The four-part message that holds the line

You do not need every fact before you can say something. You need four things, in this order, and nothing else has to make it into your first message.

• Acknowledge: say what happened, in plain words, right away.

• What you're doing: the facts you actually know right now, no jargon.

• What customers should do: the one specific action, boil water, limit use, expect low

• When you'll update: a real date and time for the next word from you, not "soon."

pressure.

Aim for something a sixth grader could read in under a minute and understand the first time through. That is not a knock on your customers. It is what calm sounds like under pressure, and it is faster to write than a careful, hedged paragraph.

The fourth part carries more weight than it looks like it should. If you promise an update by four o'clock, send one by four o'clock even if nothing has changed. Silence at that point costs you more trust than the outage itself did, because it turns "we don't know yet" into "they went quiet."

Get the first message out fast. A rough target from utility board training is within about an hour of learning something is wrong. An hour-old message with real information beats a polished one that arrives after somebody else has already written the story for you.

Choosing what to include and what to leave out

Not every true detail belongs in a public message. The test is simple: does this help a customer act or stay safe? If it is unconfirmed, an unguaranteed promise, or somebody else's rumor, it stays out.

Share the location of the problem, how long it is expected to run, and whether a boil order applies. Add plumbing guidance if the weather calls for it, and say where updates will post. State plainly that the water is safe, when that is actually true.

Hold back anything still in draft or under review, and any restoration time you cannot stand behind. Hold back a promise a board member floated before a vote. Hold back rumors and personal allegations making the rounds.

Hold back the operational side noise, too. A slow locate on someone else's line, or a crew that looks idle while it waits on a part, is not the customer's problem. None of it belongs in the message you send.

Who talks to the press, and who doesn't

Decide the spokesperson before the crisis, not during it. The manager or the board chair carries that role alone, for as long as the event runs. Write it into the emergency plan so nobody has to improvise the answer in the parking lot.

Route everything else to that one person. When a customer, a staffer, or a board member pushes for operational detail or an internal email, the answer is a polite redirect, not an argument and not a promise. Point people back to the one official channel every time, so the posted notice becomes the place everyone learns to check.

Different people need the same facts, framed differently. A customer wants to know if the water is safe and the bill is fair. The fire district wants to know if hydrants are still available; a regulator wants documentation and a plan.

A board member wants risk, cost, and confidence, and hates learning about a crisis for the first time in a public meeting. Brief the board before you brief the public. The public meeting should confirm a story your board already heard, not be where they learn it for the first time.

Holding the line between what you know and what you suspect

The hardest question on the worst day is usually some version of "did this make anyone sick." You may not know yet. Say exactly that.

"We don't know yet, and here is what we're doing to find out" is a complete, honest answer. It is not a dodge. Do not speculate to fill a silence.

Do not let a reporter's question, a board member's guess, or a social media rumor write your message for you. Every answer you give under pressure should trace back to something confirmed, not something merely plausible. State what you know, state what you are still checking, and hold the rest for the next update.

You also do not owe every message an apology. Stating what happened, and what you are doing about it, is usually enough. A calm, factual message is not a defensive one, and you are not required to treat every event as the utility's fault when it was not.

The mechanics of the notice itself, the tiers, the templates, and the rescind steps, belong to the operator running the event, covered in boil-water-notice-and-crisis-comms. Once the water is running again, the harder conversations with staff, the board, and the town are only getting started, covered in what comes next with staff, the board, and the town. For the rest of the manager track, start at /field-guide#managers.