The phones start ringing before IT has an answer.
Residents cannot pay their utility bills online.
The permitting portal will not load.
Someone at the front counter says the vendor is having problems. Someone else thinks it is the internet. A trustee has heard it may be a cyber incident.
Within minutes, several explanations are circulating.
None of them have been confirmed.
Then someone asks the question that matters most:
What should we tell residents?
Most municipalities assume the biggest challenge during an outage is restoring the technology.
It is not always.
The harder leadership challenge is communicating before anyone has complete information.
Technology teams need time to investigate. Residents want guidance now. They need to know what is unavailable, whether another option exists, and when they will hear from the municipality again.
That is why communication during a service disruption is not simply a public-relations task.
It is an operational control.
Why Residents Hold the Municipality Responsible, Not the Vendor
Residents do not know who hosts the payment portal.
They do not know whether the problem involves a software provider, an internet connection, Microsoft 365, scheduled maintenance, or a security event.
They know that a municipal service they expected to use is not working.
From their perspective, the municipality owns that experience—even when someone else owns the technology.
That is why this message is rarely enough:
“The vendor is working on it.”
It may be technically accurate, but it does not answer the resident’s question.
Residents are asking:
- Can I still pay my bill?
- Will my permit be processed?
- Should I come to Village Hall?
- Will I be charged a late fee?
- When should I check again?
Municipal communication should answer the questions residents actually have, not the questions the technical team is still trying to solve.
Before You Post Anything, Answer Four Questions
Communication problems often begin when people start writing before leadership agrees on the facts.
Before updating the website, posting on social media, responding to reporters, or sending department-wide instructions, answer four questions.
What Has Been Confirmed?
Separate confirmed information from assumptions.
If the online utility portal is unavailable, say that.
If you do not know why, say that too.
There is no need to fill every gap in the first message. A short, accurate statement is more useful than a detailed explanation that later has to be corrected.
The first communication should describe what the municipality can confirm, not what someone thinks may have happened.
What services are affected?
Residents do not need a technical diagnosis.
They need to know what they can and cannot do.
Can payments still be made in person?
Can permit applications be submitted by email?
Are phone systems working?
Is the board meeting still being livestreamed?
Is the outage limited to one service, or are several departments affected?
Be specific about the operational impact. Clear boundaries reduce confusion and help staff answer questions consistently.
What should residents do next?
Every public message should give people direction.
Explain the available workaround.
That might mean paying at Village Hall, submitting an application by email, calling a department directly, or waiting until a deadline extension is announced.
Sometimes there is no alternative yet. Say that plainly.
The goal is not to make the disruption disappear. The goal is to help residents understand their options while the technical work continues.
When will we communicate again?
Do not wait until the service has been restored to provide another update.
Silence creates an information vacuum. That vacuum is quickly filled with assumptions, screenshots, secondhand explanations, and outdated information.
When the restoration timeline is unknown, commit to the next communication time.
For example:
“We do not yet have a confirmed restoration time. We will provide another update by 2:00 p.m., whether or not the service has been restored.”
That commitment gives residents a clear expectation and gives staff one consistent answer.
Weak vs. Strong Messaging During a Vendor Portal Outage
Consider a vendor-hosted utility billing portal that becomes unavailable on a Tuesday morning.
The municipality has confirmed the outage but does not yet know the cause or restoration time.
A weak message might say:
“We are investigating the issue and expect service to be restored shortly.”
It sounds reassuring.
It also promises something the municipality may not be able to deliver.
A stronger message would be:
“Our online utility payment system is currently unavailable. We are working with our software provider to determine the cause and restore access. At this time, we do not have a confirmed restoration time. Payments may still be made in person at Village Hall. We will provide another update by 2:00 p.m.”
The stronger version does four things:
- It identifies the affected service.
- It explains what residents can do instead.
- It avoids guessing about the timeline.
- It tells residents when they will hear more.
It does not pretend to have every answer.
It gives residents the information they need right now.
Five Things Municipalities Should Never Guess During an Outage
The pressure to reassure people can lead to statements that create more trouble later.
Do not estimate a restoration time without confirmation
If the vendor has not provided a reliable timeline, do not create one.
Missing an announced restoration time damages confidence in the next update.
Say what is known, acknowledge what is not, and provide the next communication time.
Do not speculate about the cause
The first explanation is not always the final explanation.
A problem initially blamed on a server may later be traced to a vendor configuration, an expired certificate, a network issue, or a security event.
Residents do not need a running technical theory. They need accurate service information.
Do not make data security claims before a review is complete
A system being unavailable does not automatically mean data was exposed.
It also does not prove that data was not affected.
Until the appropriate review is complete, avoid making definitive statements about resident information, payment records, or application data.
Do not blame the vendor publicly
The vendor may be responsible for restoring the system, but the municipality remains responsible for managing the resident experience.
Public blame does not restore the service. It can also distract from the information residents actually need.
Vendor accountability should be handled through the municipality’s escalation, contract, and governance processes—not improvised in a public update.
Do not let every department create its own message
The front counter, department phones, social media pages, elected officials, and municipal website should not provide different versions of the same event.
One person or role should approve the message. Department leaders should receive the same internal update before residents begin asking questions.
Consistency is not about controlling every word.
It is about making sure the municipality speaks from the same set of confirmed facts.
Why Outage Communication Must Begin Before the Fix Is Ready
Communication is often treated as something that happens after IT determines the cause or the vendor provides a restoration estimate.
That is too late.
Communication begins as soon as the disruption affects municipal operations.
Clear communication can:
- reduce avoidable calls and repeated questions,
- help department heads give staff consistent direction,
- keep elected officials working from the same information,
- explain available workarounds,
- and protect public trust while restoration continues.
That makes communication part of business continuity.
Technology restores the system.
Leadership keeps the situation from becoming more confusing than it already is.
Those are different responsibilities.
Both matter.
Decide Who Owns Public Messaging Before an Outage Happens
The best time to decide who approves public updates is not during the outage.
It is during a normal leadership meeting, when the phones are quiet and the facts are not changing by the minute.
Ask one question:
Which Role Approves Resident Updates When a Service Goes Down?
Not which department.
Which person or role?
That person does not need to diagnose the technology. The technical team or vendor should provide confirmed status information.
Leadership’s responsibility is to turn that information into clear operational guidance:
- what is affected,
- what residents should do,
- what remains unknown,
- and when the next update will be provided.
If the answer to that ownership question is unclear, the municipality has found a governance gap before it becomes a public problem.
Strong Outage Communication Starts Before the First Resident Calls
The first public message will not determine how quickly a vendor restores its portal.
But it will influence how residents judge the municipality’s response.
They may still be inconvenienced.
They may still be frustrated.
The technology may still be down.
Leadership can still provide clarity.
Residents do not need the municipality to know everything immediately.
They need the municipality to say what it knows, avoid guessing about what it does not, and explain what happens next.
Because residents do not know your vendor.
They know their municipality.
And during a disruption, that is who they are counting on.
Strong communication during a service disruption starts with decisions made before the first resident calls.
Review who approves public messages, how departments receive updates, what information must be confirmed, and how often residents will hear from the municipality when restoration takes longer than expected.
This is worth settling while the systems are working.