When systems go down, silence often does more damage than the outage itself. Good outage status updates tell people what is broken, what to do in the meantime, and when they will hear more. Here is what you should expect from your IT provider, and what to ask for if you are not getting it.
Why outage status updates matter as much as the fix
During an outage, staff make decisions with incomplete information. They have to decide whether to reschedule client calls or switch to paper intake.
Without updates, each person guesses, and several call the help desk at once to ask the same question.
That flood of calls slows down the people trying to fix the problem. So a clear update is not a courtesy. It is part of the response.
What a good update contains
A useful update is short and plain. It should answer the questions people are about to call and ask. Use this list to judge the updates you receive:
- What is affected: the system, and who is affected (everyone, one office, or remote staff).
- What still works, so people know which tools they can keep using.
- A workaround, if one exists.
- What the team is doing right now, in plain language.
- When the next update will come, even if there is no news.
- Who to contact with new information, such as a related error message.
Notice what is missing: a guaranteed fix time. Early in an outage, nobody honestly knows. A provider that promises a quick fix to calm you down, then misses it, loses credibility for the rest of the incident.
How often updates should arrive
Cadence matters more than detail. The first message should go out soon after the provider confirms a problem affecting more than one person. Even “we know, and we are working on it” stops the duplicate calls.
After that, updates should come on a predictable schedule. For a full outage, a rhythm of every 30 to 60 minutes is reasonable. For a partial issue, fewer updates are fine.
Long outages need a slightly different rhythm. Once a problem stretches past a few hours, a scheduled summary for leadership at set times often works better than constant small updates.
The key is that each update states when the next one will come. Then the provider has to keep that promise, even when the only news is “still working on it.”
When the outage starts somewhere else
Many outages start upstream. Microsoft 365, an internet carrier, or a line-of-business software vendor may be the real source. Your provider cannot fix those systems.
However, they can still translate what the vendor says into what it means for your staff. Microsoft, for example, posts incident details in the Microsoft 365 service health dashboard. Your provider should watch it and relay relevant incidents rather than leaving you to discover them.
The same goes for your internet carrier’s status notices. A good provider also tells you when a problem is theirs, rather than blaming a vendor to save face.
Plan the channels before you need them
The most common failure I see is a provider sending outage updates by email while email is down. Agree in advance on at least two channels. For example, use a text alert list for leadership, a Teams channel, and a phone tree for offices that lose internet.
Also decide who inside your organization receives outage status updates and passes them on. Usually that is the office manager or operations lead. Then the provider has one contact point, and staff hear one consistent message.
Who needs what
Executives need impact and decisions. Staff need workarounds and timing, delivered in plain language without technical jargon. Clients may need a short notice if their service is affected, and your leadership should approve that wording before it goes out.
What your own team should do
Updates work best when your side is ready to use them. First, name one internal point person for outages, plus a backup for days that person is out. Next, keep a short printed list of critical phone numbers, because a contact list stored in the cloud does not help when the cloud is down.
Also write down the manual workarounds for your most important processes. For example, a clinic might keep paper intake forms, and a finance team might know how to approve a payment by phone. Then practice once a year, so nobody learns the workaround during a real outage.
After the outage: the review
A good provider closes a significant outage with a short written summary within a few days. It should cover what happened, the timeline, the root cause if known, and what will change to prevent a repeat.
NIST’s SP 800-61 Revision 3, published in April 2025, treats lessons learned as part of ongoing improvement rather than a one-time report. It focuses on security incidents, but the same habit applies to operational outages.
If your provider never sends reviews, ask for one after the next significant outage. Their response will tell you a lot about how they run their team.
Also compare reviews over time. If the same cause shows up twice, the prevention step from the first review did not work, and that deserves a direct conversation.
How WEBIT approaches this
Live calls to WEBIT are answered in under 60 seconds, and tickets are acknowledged within 15 minutes, so people reach a person quickly during an outage. Your named Client Success Manager keeps your contacts informed while engineers work the problem.
We would rather agree on channels and contacts during our 30-day onboarding than improvise during the first outage. That planning is part of how we deliver managed IT services, and our FAQ covers how support works day to day.
Key takeaways
- Good outage status updates cover impact, workarounds, current actions, and the next update time.
- Predictable cadence matters more than detail, and honesty beats a fast promised fix.
- Agree on at least two update channels that do not depend on the failing system.
- Expect a short written review after any significant outage.
Want to pressure-test how your provider handles downtime? Talk to an owner.
