01
First 15 minutes
Confirm the approved action language, affected area, source of updates, and next update time before the first public notice goes out.
Crisis Communications for Utilities
A practical communications framework for utilities issuing, updating, and lifting a boil water notice with clear public-health guidance and coordinated customer information.
The short answer
When a boil water notice is necessary, people do not need a long technical explanation first. They need to know whether the notice applies to them, what they should do now, where they can find verified updates, and when they will hear from the utility again.
The communications program must run alongside operations from the first hour: public-health guidance first, a single source of truth, prepared customer-facing staff, and a disciplined update rhythm while testing and restoration continue.
Step 1
The first notice should make the immediate guidance unmistakable. State the affected area, the notice type, the action customers should take, and any population-specific instructions that the responsible public-health authority has approved. Put those facts before the operational narrative.
Avoid language that requires a resident to interpret risk on their own. If information is still being verified, say what is known, what is being tested, and when the next update will be issued.
Step 2
A notice page, social channels, customer alerts, call-center scripts, field crews, partner agencies, and local officials should all draw from the same approved facts. Inconsistent updates create more confusion than a lack of detail.
Set a specific next-update time even when there is no material change. That gives residents a reason to return to the utility’s source rather than rely on a screenshot, rumor, or third-party account.
Step 3
Customer-service staff, field crews, elected officials, schools, health-care facilities, businesses, and community partners will receive questions immediately. Give them a concise fact sheet, the current guidance, a referral path for technical questions, and a clear instruction not to speculate.
This is especially important when the affected area is changing or testing is underway. The communications team needs a reliable handoff from operations so the public answer stays aligned with the most current verified information.
Step 4
When the notice is lifted, communicate the decision, the effective time, any customer actions that remain appropriate, and where residents can review the official update. Do not assume a social post is enough; use the same channels that carried the initial notice.
After the immediate event, document the questions that caused the most confusion. They are the best starting point for improving the next incident communications plan and customer-service protocol.
Incident clock
A boil water notice needs a time-based communications rhythm, not a generic checklist. The sequence below keeps public-health action and verified operational updates aligned.
01
Confirm the approved action language, affected area, source of updates, and next update time before the first public notice goes out.
02
Give customer-facing staff, field teams, partner agencies, elected officials, schools, and care facilities the same approved facts and escalation path.
03
Maintain a published update rhythm while operations continue. State what is known, what is being verified, and when the next official update will be available.
04
Use the same channels to state the effective lift time, any approved customer actions, and where residents can verify the final official update.
Relevant proof
Water-quality response
A customer-information and trust challenge in a high-stakes water-quality environment.
First 24 hours
See Sigler’s utility-focused framework for response coordination, public information, and operational handoff.
Continue the conversation
How to Explain a Lead Service Line Replacement Program to Your Community
A plain-language communications approach for utilities explaining lead service line replacement, property access, customer responsibility, and program timelines.
How to Run a Public Meeting That Turns Hostile
A practical communications guide for utility, infrastructure, and public-agency leaders preparing for—or responding to—a hostile public meeting.
Common questions
The affected area, what customers should do, when the notice began, where to find verified updates, and when the next update will be given. Operational context should support—not obscure—the immediate guidance.
Set an update rhythm that matches the event and keep it. Even a short update that testing or restoration continues can prevent an information vacuum.
Customer-service staff, field staff, leadership, elected officials, partner agencies, and any organization likely to be asked for guidance by affected customers.
Use the same channels as the initial notice, state when the lift is effective, provide any approved next steps, and keep the source update available for customers who need to verify it.
A boil water notice is not the time to invent an approval path or a customer-information process. Build the communications annex before the next incident tests it.
Start a ConversationReady to start a conversation?
Contact Us