The Calm-Draft Folder: Crisis Copy to Write Before the Proverbial Hits the Fan

It is 7:42 on a Tuesday. Your payment provider has gone down, the support queue is filling up, and someone in the leadership chat asks the question every brand dreads: who is writing the message? Everyone looks at the person who once wrote a decent newsletter. That is not a crisis plan. That is a hostage situation with a keyboard.

At Content Crib, we spend a lot of time helping brands sharpen their everyday copy. But brand voice is really tested at the edges—when something breaks, when a delivery slips, when a refund is late. That is when pre-written crisis copy earns its keep. Not a full press release. Not a legal statement. A calm-draft folder: a short crib sheet you build while nobody is panicking, so you are not inventing tone from scratch while the proverbial is hitting the fan.

Why write the apology before you need it

Crisis copy written under pressure tends to default to one of two modes: over-apologising or going full robot. You either get four paragraphs of sincere regret that say nothing, or a message so cautious it sounds like it was drafted by a committee of lawyers wearing cardigans. Neither helps a customer who just wants to know whether their payment went through.

Pre-drafting holding statements is not about hiding. It is about buying yourself time to be clear. The first message does not need every fact. It needs to say: we know, we are on it, here is when you will hear from us again. UK customers are generally forgiving of mistakes. They are much less forgiving of being fobbed off.

What goes in the calm-draft folder

You do not need a 40-page crisis manual. You need four things, kept where more than one person can find them:

• Three holding statements: acknowledgement, delay and remedy.
• A status-page template.
• A short customer email skeleton.
• A one-page approval and ownership note.

Keep each item to a page. Add an owner and a review date. If the folder lives only in one person's drive, it is not a plan—it is a rumour. In regulated sectors, include the approval path for legal or compliance from the start. Nobody wants to discover the sign-off process at 8pm.

Holding statement one: the quick acknowledgement

This is the first thing you post when you know something is wrong but not yet why. Keep it short and timestamped.

Template: We are aware that [service] is [issue] for [scope]. We are investigating now and will update this page by [time]. If you need help in the meantime, contact [channel].

Fill in the scope honestly. If it is everyone, do not say 'some customers' to soften it. If it is a small subset, say so. A vague scope makes people assume the worst. A clear scope, even a bad one, reduces the number of people who assume it applies to them.

Holding statement two: the delay

This is the one brands forget. The first update says you will know more by 10am. It is now 10:15 and you do not. Do not go silent. Silence reads as chaos.

Template: Work is taking longer than we said. We are still on it. Our next update will be by [time].

Then add one useful line: what customers should or should not do. If people should not retry a payment, say that plainly. If they should check their inbox, say that too. One instruction is better than none.

Holding statement three: the remedy

This is where tone gets tested hardest. People want to know what happens next and whether they need to do anything.

Template: Here is what we are doing: [action]. Here is what you need to do: [action, or 'nothing']. Here is when it will happen: [timeframe].

Do not promise compensation before it has been approved. Do not speculate about who is to blame. Do say what you know, what you are fixing and when the next update will land. If you were charged incorrectly, say how that will be corrected. If you were not charged, say that too—people worry about money first.

The status page: short, timestamped, honest

A status page is not a blog post. It has one job: tell people what is happening now. Use a simple template: current status, affected services, when it started, last updated, next update, what to do. Timestamp every update. Nothing undermines trust faster than an 'investigating' notice that has not changed for six hours.

Write in plain English. 'You may not be able to log in' beats 'degraded authentication performance' for most audiences. Save the technical language for the technical detail section, if you need one at all. Keep the main message scannable on a phone, because that is where most people will read it—probably while standing on a train platform or queuing for a coffee.

The email skeleton: one job, one link

Crisis emails should not try to do everything. The status page is the live source of truth. The email is a nudge.

Skeleton: Subject line naming the service and the issue. Opening line confirming what is happening. One short paragraph on who is affected. One short paragraph on what you are doing. One clear action—usually 'check the status page for updates'. Sign-off from a team or role, not a faceless 'The Team' if you can avoid it.

Avoid ALL CAPS subject lines and exclamation marks. Avoid 'we sincerely apologise for any inconvenience caused'—it is the copywriting equivalent of a shrug. If an apology is warranted, say sorry once, plainly, and then move to what happens next. 'Sorry it is taking longer than it should' sounds human. 'We apologise for any inconvenience this may cause' sounds like a template with a pulse.

Draft now, leave later

Draft the structure, tone, roles and channels now. Draft the approval steps, the contact details and the legal boundaries now. Leave the facts blank until you have them: exact cause, number affected, timeline, remedy, compensation, named spokesperson if needed.

Use square-bracket placeholders and a 'do not publish until' checklist. Then, when the facts arrive, fill the brackets and read it aloud. Does it sound like your brand? Would a worried customer understand it on the first read? If not, sharpen it before it goes out.

Sounding responsible without sounding robotic

Short sentences help. So does saying sorry once, if it is warranted. Explain what happens next. Give a time for the next update. Own the customer experience rather than immediately pointing at a supplier—even if a supplier caused it, your customer bought from you.

Do not say 'we take data protection very seriously' unless you are about to say what actually happened. Do not use 'unprecedented' unless it genuinely is. British understatement can be an asset: 'This is not good enough, and we are fixing it' lands better than a paragraph of corporate regret. Match your normal brand voice. If you are warm, be warm. If you are plain, be plain. Do not suddenly become a different company because the server fell over.

Folders do not prevent outages. But a calm-draft folder stops your brand sounding like a stranger on its worst day. Write the apology while you are calm. You will write a better one when you are not.