Prepare a holding statement for a service disruption

When a service stops working, people often need an immediate answer to a practical question: can they proceed, should they wait, or is another route available? A holding statement should address that need without pretending the investigation is complete. It is a temporary account of known facts, not a smaller version of a final explanation.

Start with the observed effect

Describe the problem in terms the affected audience recognises. In a hypothetical booking interruption: ‘Some customers are seeing an error when opening the booking calendar. We are investigating and will update this page at 14:00 London time.’ This identifies the symptom and the next information point. It does not invent a cause, affected percentage or repair estimate.

Only include a workaround after checking that it works and that the team can support it. Redirecting every customer to an unstaffed telephone line creates another failure. Explain any limits, such as which requests can be handled through the alternative route. If there is no verified workaround, say that clearly instead of suggesting repeated attempts without a basis.

Keep three kinds of time separate

The time the problem began, the time the statement was issued and the expected time of the next update have different meanings. Label them where relevant. A timestamp helps people distinguish a current notice from a screenshot circulating later. An update time is not automatically a restoration promise; write the distinction so that readers do not have to infer it.

Choose one maintained public location for the statement and have other channels point to it. Short social notices and support replies can summarise the impact, but they should not introduce competing explanations. Make sure customer-facing colleagues know what has been confirmed and where to direct new evidence.

Prepare the change from holding to resolved

When access returns, check what can genuinely be called resolved. A working page does not prove that every delayed booking or transaction has been dealt with. Explain remaining actions and tell affected people how to raise an unresolved case. Preserve a short chronology when it helps readers understand the sequence rather than replacing the entire notice with a cheerful announcement.

Work through a changing incident

Suppose a fictional appointment service first receives reports that its calendar will not load. The opening notice identifies that observed effect. Later, the team confirms that the problem affects only one booking route and verifies a telephone alternative. The second notice can narrow the impact and add the working alternative without claiming to know the technical cause.

If the calendar then becomes available, the next notice can state that access has been restored while acknowledging that the team is still checking pending requests. That is more precise than saying everything is back to normal. The final explanation may arrive later, after the cause and outstanding work have been established. Different stages justify different information; they do not justify changing certainty without evidence.

Before posting each update, compare it with the previous one. Does the new wording contradict an earlier assurance? Has a promised update time passed without an explanation? Do customers need to take an action that was not previously required? These questions help maintain a usable chronology rather than a collection of disconnected statements.

After the disruption, remove emergency prominence when it no longer serves visitors, but keep the relevant account available where people with delayed requests may need it. Update supporting help pages if the incident revealed a recurring problem. The communications review should examine whether people received accurate actions at each stage, not only whether the final statement sounded reassuring.

Before an incident, prepare a blank structure containing fields for impact, verified workaround, issue time and next update. Do not prewrite an assurance that no information was lost or no customers were affected. Those claims depend on evidence from the actual event. Preparation should reduce drafting confusion while leaving factual conclusions open.