The first statement during an incident is not an explanation. It is a promise about when the next one comes. Most companies get this backwards: they wait until they can explain, and by then the story has been written by someone with less information and more certainty.

Say what you know, and the edges of it

A useful holding statement has four parts: what happened, who is affected, what you are doing, and when the next update is. It does not need a cause. “We are investigating” is acceptable if it is true; “we are monitoring the situation” is rarely true and never useful.

Name the uncertainty. “We do not yet know whether data was affected” is better than silence, and much better than a guess you will have to retract in an hour.

The next update is the product

Set a time and keep it, even if nothing has changed. A short update at the promised time is worth more than a perfect statement late. If the schedule slips, say so before the deadline, not after — the apology for a broken promise costs more than the delay itself.

Write for three audiences at once

Customers need the impact and the workaround. Support needs the same facts in sentences they can paste. Your own team needs to know what not to say. One page, three sections, same facts; that is the whole template.

  • Customers: what is affected, what to do now, when you will hear next.
  • Support: approved sentences, links, escalation path, what remains unknown.
  • Team: who speaks, where updates live, what not to speculate about.

No theatre

Avoid “we take this extremely seriously”. Everyone says it, so it has stopped meaning anything. Avoid blaming a provider until you know; avoid “service degradation” when you mean “the site is down”. Plain words read as competence, especially under pressure.

Silence is also a statement, and it is usually the least accurate one.

Prepare before you need it

Write the template when nothing is on fire. Name one owner, publish the update schedule, and rehearse it once with support. The cost is an afternoon; the return is not improvising at two in the morning.

We keep four templates ready for every client: a holding statement, a partial-outage update, a full-outage update, and a resolution note. They take a day to write together and are edited once a year.

The templates and the on-call arrangement are described under crisis communication. If something is happening now, put “crisis” in the subject line: hello@albinecommunicate.xyz.