An order screen stops loading at ten in the morning. Within minutes the team chat fills with the same question asked six ways: is it just me, is someone on it, can I keep working? Each person who asks costs the person fixing the problem a little attention. A short status note, sent early, removes most of those questions. This article describes a simple format for internal tools used by your own staff. For messages to customers, see handling a service outage message to customers: what to say in the first hour.
Decide who writes it before it happens
The note is written by one named person, usually the owner of the tool or the person on call. Agree this in advance and write it next to the tool's other documentation. If nobody owns the message, everyone assumes someone else has sent it, and staff learn about the outage from each other.
Also choose one place where the notes appear: a pinned chat channel, a shared page or a mailing list. People should not have to guess where to look. Staff who cannot open the tool at all need a place that does not depend on it.
The first note: within fifteen minutes
Send it as soon as the problem is confirmed by a second person, not when it is understood. A good first note has five lines:
- What is affected. "The order entry screen does not load."
- What still works. "Order lookup and reports are fine."
- What to do now. "Write new orders on the paper form and keep them in the tray."
- Who is on it. "Petra is investigating."
- When you will hear next. "Next update by 10:45."
Do not guess the cause and do not promise a repair time. A wrong guess is remembered longer than a late fix. "We do not know yet" is an acceptable sentence in a status note if it is followed by the time of the next update.
Give a workaround people can follow
The most useful part of the note is the line that says what to do instead. It should be short enough to follow without asking anyone. If the workaround needs more than three steps, link to a one-page procedure prepared in advance.
Typical workarounds for small internal tools are a paper or spreadsheet form with the same fields, a shared inbox for requests that the tool would normally receive, or a phone call to a named colleague who can look things up. Whatever you choose, say where the manual records go, so that someone can enter them into the tool later. Lost entries are the most expensive part of many outages, and they are avoidable.
If you have no workaround, say that clearly: "Please do not start new orders until 11:00; use the time for follow-ups." Even that tells people something.
Keep the updates on time
Updates are valuable because they arrive when promised. If you said 10:45, send something at 10:45 even if the message is "still investigating, next update 11:15". Silence makes people assume the worst and start asking again.
Each update should change only what changed: the status, the new information and the next time. Avoid long technical explanations. Staff do not need the name of the failing component. They need to know whether to wait, work around or go home.
Keep the interval sensible. Every thirty minutes is enough for the first two hours. After that, hourly updates are fine, and at the end of the day send one note saying what happens overnight and who will write first thing tomorrow.
The closing note
When the tool works again, send a closing note. It has four parts:
- The tool is back and since what time.
- Anything that needs attention: records entered by hand, data from the gap that may be missing, passwords or sessions that need renewing.
- Who to tell if something still looks wrong.
- When the short review will take place.
Ask people to check the manual records first. Entries made on paper during the outage are the usual source of duplicates and gaps once the system is running again.
Learn one thing
Within a few days, spend fifteen minutes on a short review. Write the timeline in five lines: when it started, when it was noticed, when the first note went out, when it was fixed and what the cause was. Then decide on one change: a better alert, a clearer workaround, a backup contact. For a fuller format, see post-incident review for internal systems: one page, blameless timeline, fix owner and follow-up date.
Keep a copy of the notes you sent. The next time the tool fails, the first note already exists as a template, and the person on call only has to fill in the blanks. If you use a weekly rhythm for routine reporting, a Friday status note follows the same idea: short, regular and easy to scan.
A template to keep
Status: [tool name] – [affected function] not working (sent 10:15) Not working: [what]. Still working: [what]. Please do: [workaround]. Owner: [name]. Next update: [time].
Five lines, one owner, one time. That is enough to keep a team working through most small outages.
Sources
- Common practice for incident communication and post-incident review in small organisations, offered as a practical guide. The time limits, update intervals and the template are starting points to adapt to your team. No client results or market figures are claimed in this article.