01
Crisis team
Name the incident lead, communications lead, operations liaison, legal reviewer, executive decision maker, customer-service lead, and backups. Record how they are reached after hours.
Utility Crisis Preparedness
A working crisis communication plan framework for water and wastewater utilities: decision roles, notifications, regulator coordination, updates, recovery, and testing.
The short answer
A utility crisis communication plan should not be a binder that lists contacts and generic talking points. It should be a decision system: who gets the facts, who can approve what, which audiences need action, and how the organization keeps one verified public record while operations respond.
The test is simple. If a water-quality concern, main break, wastewater spill, outage, or employee emergency begins at night, the plan should help the team issue useful first information, coordinate with the right authorities, and set a reliable update rhythm before uncertainty becomes the public story.
Step 1
An emergency operations plan and a public-information plan are related, but they do not solve the same problem. Operations needs to stabilize conditions, protect people, gather samples, restore service, and meet regulatory obligations. Communications needs to turn verified facts into action people can understand without getting ahead of the response.
Bring the communications lead into the planning process with operations, legal counsel, customer service, and leadership. The result should make the handoffs clear: who reports a changed condition, who verifies it, who approves public language, and who makes sure staff and external partners receive the same information customers see.
Step 2
Not every field issue needs a public crisis response, but every event should have a defined path for deciding whether it does. Establish categories such as service disruption, water-quality concern, wastewater spill, major infrastructure failure, workforce incident, and external emergency. For each, identify the conditions that trigger customer communication, executive activation, regulatory coordination, or a broader public-information posture.
Classification is not about finding the perfect label. It is about eliminating avoidable delay. If the team knows what facts it needs, what authority applies, and what the first communication decision is, it can preserve time for the operational decisions that only technical staff can make.
Step 3
Customers may need immediate action. Board members and elected officials may need a factual briefing before they hear from constituents. Schools, health-care facilities, large business users, community partners, field crews, and neighboring systems may each need different timing and detail. A stakeholder matrix should record the purpose, channel, owner, approval requirement, and backup method for each group.
Do not treat the matrix as a mass-distribution list. It is a way to recognize that a customer-service script, a regulator notification, an elected-official update, and a public social post have different jobs. The message can be consistent without being identical.
Step 4
A holding statement is not a substitute for facts. It is a disciplined starting point that lets the utility say what it knows, what it is doing, what customers should do now, and when they will hear next—without waiting to write every sentence from scratch. Prepare adaptable language for the scenarios most relevant to the system’s risk profile.
The plan should also settle approval authority. Decide what a communications lead can publish using verified incident facts, what requires a technical confirmation, when legal review is essential, and who can resolve an impasse. A plan that requires every senior person to approve every update will fail at the moment it needs to be fastest.
Step 5
The initial public notice should answer the questions a household will ask immediately: Does this affect me? What should I do now? Where is the affected area? What is the utility doing? When will there be another official update? Technical context should help answer those questions, never displace them.
For a boil-water scenario, that action-first structure is especially important. The utility should already know which tools it can use—alert systems, the incident page, social channels, field notification, customer-service scripts, partner outreach, and translation support—and who owns the next update when testing or restoration is still underway.
Step 6
Recovery communication begins before the incident is over. Customers and stakeholders need to understand when service is restored, whether precautions remain, what assistance is available, and where they can find the official record. The team should also be prepared to explain what it will review once the immediate response closes.
Within days of the event, hold an after-action review that looks beyond whether a news release was issued. Examine operational-to-communications handoffs, approval bottlenecks, unanswered customer questions, channel performance, stakeholder coordination, and the decisions that delayed or improved the response. Turn the findings into a timetable for updating the plan and running the next tabletop exercise.
Planning framework
This is not a document outline to finish after an incident begins. It is the operating architecture that lets water and wastewater leaders make defensible, timely public-information decisions while operations, counsel, and regulators are handling the event.
01
Name the incident lead, communications lead, operations liaison, legal reviewer, executive decision maker, customer-service lead, and backups. Record how they are reached after hours.
02
Define the conditions that trigger a communications response, distinguish monitoring from public notification, and identify who can declare a higher-response posture.
03
Set what can be released immediately, what requires technical or legal review, who resolves disagreement, and how an approval is recorded when time is short.
04
Map who needs information first: customers, employees, board members, elected officials, schools, health-care facilities, business customers, community partners, and neighboring systems.
05
Identify responsible public-health and regulatory contacts, notification obligations, the role of approved guidance, and who confirms facts before the utility speaks.
06
Prepare action-first notices, affected-area maps, language-access needs, customer-service scripts, and the channel sequence for a water-quality, service, or wastewater event.
Use the boil water notice guide →07
Establish a request log, a media-response owner, on-the-record rules, interview escalation, and a disciplined way to correct material errors without extending speculation.
08
Assign primary and backup spokespeople, define their role in public briefings, and prepare them to explain verified facts, empathy, uncertainty, and the next update.
09
Draft scenario-specific starting language that states what is known, what the utility is doing, what customers should do now, and when the next official update will come.
10
Set the first update interval, decision checkpoints, and the authority to communicate ‘no material change’ so customers are not left to fill an information vacuum.
Use the First 24 Hours framework →11
Designate the official incident page, alert tools, social accounts, accessibility and translation checks, monitoring responsibility, and the process for retiring or updating stale information.
12
Plan how the utility explains restoration, continued precautions, customer assistance, and what will happen after the immediate operational response ends.
See Security Water in practice →13
Capture the decision log, recurring public questions, approval bottlenecks, channel performance, and operational handoffs while the details are still clear.
14
Set a recurring scenario-based exercise schedule and include the people who must make and carry communications decisions, not only the staff who wrote the plan.
Relevant proof
Scenario guidance
Use Sigler’s action-first framework for public-health guidance, customer notices, and a reliable update rhythm.
Water-quality response
See how transparent, sustained customer and stakeholder communication supported a high-stakes water-quality response.
First 24 hours
Explore Sigler’s utility-focused response framework for operational handoff, public information, and leadership decisions.
Continue the conversation
Boil Water Notice Communications: What Customers Need to Know First
A practical communications framework for utilities issuing, updating, and lifting a boil water notice with clear public-health guidance and coordinated customer information.
How to Choose a Crisis Communications Firm for a Utility
A practical evaluation guide for utilities choosing a crisis communications firm with utility experience, first-hours readiness, and regulatory credibility.
Common questions
The plan should be owned jointly by the functions that must use it: operations, communications, leadership, legal counsel, customer service, and the staff responsible for regulatory coordination. One communications owner should maintain the plan, but the organization needs shared operating ownership.
Set a recurring schedule and test the scenarios most relevant to the system’s risks. Update the plan after exercises, major organizational changes, new communications tools, and any incident that exposes a real gap.
A holding statement gives the utility a verified starting message while details are still developing. A public notice gives affected people the specific action, geography, timing, and official source of information they need. A strong plan prepares both.
Include counsel in the planning process so the team knows when review is necessary. In an active event, counsel can help protect against speculation and support required notifications, but the plan should avoid creating an approval chain that prevents timely public-health or customer guidance.
Use a realistic scenario, time-based injects, actual approval and notification paths, customer questions, media requests, regulator coordination, and a post-exercise review. Include the people who would make decisions during the event, not only communications staff.
A plan becomes valuable when it helps the right people make the next decision under real pressure. Build, test, and refine the communications system before an incident forces you to invent it.
Discuss Crisis PreparednessReady to start a conversation?
Contact Us