The Moment Everything Becomes a Communication Problem
The phones start ringing before IT has an answer.
Residents cannot pay their utility bills online. The permitting portal won’t load. Someone at the front counter says it’s a vendor problem. Someone else thinks it’s the internet. A trustee has heard it might be a cyber incident.
Within minutes, several explanations are circulating. None of them have been confirmed.
Most municipalities assume the biggest challenge during an outage is restoring the technology. Often, it’s not. The harder challenge is communicating before anyone has complete information.
And here’s the thing I’ve noticed: the municipalities that handle this well aren’t the ones with the fastest IT providers. They’re the ones that decided before the crisis hit who would own the first hour of communication.
Residents Don’t Know Your Vendor—They Know Your Municipality
Residents don’t know who hosts the payment portal. They don’t know whether the problem is 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’s why “The vendor is working on it” doesn’t work as a first response. It’s technically accurate, but it doesn’t answer what residents are actually 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 have, not the questions the technical team is still trying to solve.
What Happens When Leadership Hasn’t Decided
Consider what usually unfolds when a critical service becomes unavailable and nobody has pre-decided who owns the communication.
A utility billing portal goes down on a Tuesday morning. IT starts investigating. The IT director sends an email to the finance director saying “vendor is aware, working on it.” The finance director tells the front counter staff “tell people we’re looking into it.” The town manager hears from a resident’s phone call before seeing any official update. Someone posts on Facebook: “We expect service to be restored shortly.” Social media gets flooded with versions of this message, each slightly different. An elected official texts residents directly with their own update.
By the time IT actually has confirmed information, the municipality has already created four different narratives, missed a restoration deadline it never should have announced, and lost the single, consistent answer that residents need.
The damage isn’t technical. It’s organizational. And it all stems from the same root: nobody decided who owned the first hour.
What Changes When Leadership Does Decide
Now imagine the same outage, but with one difference: six months earlier, in a quiet leadership meeting, the municipality answered this question:
If a major municipal service became unavailable today, who decides what residents are told in the first hour?
Not which department. Which person or role?
The answer was: “The town manager, in consultation with the IT director and finance director.”
Now the outage happens. Within 15 minutes, the town manager has confirmed three facts: the portal is down, the vendor is aware, and nobody knows the restoration time yet. She approves one message. It goes to the website, gets posted on social media, and gets sent to all department heads with instructions: “This is what we’re telling residents. If you get questions, use this message.”
The message says: “Our online utility payment system is currently unavailable. We are working with our software provider to determine the cause and restore access. Payments may still be made in person at Village Hall. We will provide another update by 2:00 p.m.”
It identifies what’s affected. It offers an immediate workaround. It avoids guessing about restoration time. It gives residents a clear expectation for the next update.
The front counter gets one answer to repeat. Social media gets one message to post. Elected officials get the same information as residents. Finance knows which workaround to prepare for. When 2:00 p.m. rolls around, the same person provides the next update, whether the system is back or not.
The resident experience is still inconvenient. But it’s not confusing. And that difference—between inconvenienced and confused—changes everything about how the municipality is perceived after the crisis passes.
Why the Difference Matters More Than You’d Think
When residents don’t have clear information, they create their own. Screenshots circulate on Nextdoor. Someone calls a local news station. Rumors about data breaches spread faster than facts do. Staff get pulled into answering the same question fifty times because there’s no single answer.
Clear communication reduces all of that. It helps department heads give consistent direction. It keeps elected officials from freelancing their own explanations. It protects public trust during the disruption rather than spending months rebuilding it afterward.
The municipalities that handle this well understand that communication isn’t a byproduct of restoring the system. It’s part of business continuity itself.
But communication is only one part. The deeper issue is whether the municipality has recognized vendor risk as an operational dependency and planned for what happens when a third-party system it relies on becomes unavailable. IT resilience planning for municipalities establishes how critical services will continue, what recovery priorities should be, and how the organization operates when an important system goes down.
Technology restores the system. Leadership keeps the situation from becoming more confusing than it already is. Those are different responsibilities.
Before the Next Crisis: Answer One Question
The best time to make this decision is not when the phones start ringing. It’s right now, during a normal leadership meeting.
Ask: If a major municipal service became unavailable this afternoon, who would decide what residents are told during the first hour?
Not which department. Which person or role?
If the answer is clear, the next step is even simpler: that person needs to know they own it. And the rest of the organization needs to know to wait for their message instead of creating their own.
The Real Test
The first public message won’t 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.
But leadership can still provide clarity.
Residents don’t need the municipality to know everything immediately. They need the municipality to say what it knows, avoid guessing about what it doesn’t, and explain what happens next.
Because residents don’t know your vendor. They know their municipality.
And during a disruption, that’s who they’re counting on.
Questions Leaders Are Asking
Who should own communication during a vendor portal outage in a municipality?
The answer was: 'The town manager, in consultation with the IT director and finance director.' Not which department. Which person or role?
Why doesn't 'the vendor is working on it' work as a first response to residents?
It's technically accurate, but it doesn't answer what residents are actually 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 have, not the questions the technical team is still trying to solve.
What should a municipality's first public message say when an online service goes down?
The message says: 'Our online utility payment system is currently unavailable. We are working with our software provider to determine the cause and restore access. Payments may still be made in person at Village Hall. We will provide another update by 2:00 p.m.' It identifies what's affected. It offers an immediate workaround. It avoids guessing about restoration time. It gives residents a clear expectation for the next update.
What goes wrong when no one has pre-decided who owns communication during a service outage?
By the time IT actually has confirmed information, the municipality has already created four different narratives, missed a restoration deadline it never should have announced, and lost the single, consistent answer that residents need. The damage isn't technical. It's organizational. And it all stems from the same root: nobody decided who owned the first hour.
When is the right time for municipal leadership to decide who owns crisis communication?
The best time to make this decision is not when the phones start ringing. It's right now, during a normal leadership meeting. Ask: If a major municipal service became unavailable this afternoon, who would decide what residents are told during the first hour? If the answer is unclear, the municipality has found a governance gap before it becomes a public problem.