Cuesta Comunicacion Total logo Cuesta Comunicacion TotalCommunication that lands right
Media Relations

Writing a Statement Before the Story Breaks

The worst statements I have ever seen written were written under deadline, forty minutes before a reporter's story went live, by someone who had never drafted one before that afternoon. The words were fine.

Deep rose wave pattern suggesting a message sent ahead of events

The worst statements I have ever seen written were written under deadline, forty minutes before a reporter's story went live, by someone who had never drafted one before that afternoon. The words were fine. The problem was structural, because a statement built in forty minutes of panic reads like exactly that, however carefully the sentences are chosen after the fact.

A holding statement is not something you write when the story breaks. It is something you write months before, for a situation you hope never happens, and file away where someone can find it at eleven at night. Most organizations do not have one, and the ones that do usually wrote it after the first crisis taught them the hard way, which is the expensive way to learn this particular lesson.

Why waiting until the moment fails

Under real pressure, the part of the brain that handles careful drafting is competing with the part that is managing fear about consequences, and the second part usually wins. Statements written in the moment tend toward one of two failure modes: they either say too much, volunteering details nobody has confirmed yet, or they say almost nothing, which reads as evasive even when the underlying facts are not actually damaging.

A statement drafted in advance, with no active crisis attached to it, does not have that competition happening. You can think clearly about tone, about which facts genuinely need confirming before release, and about which sentence structures avoid sounding defensive, because nobody is watching a countdown while you write it. That calm is not available to you at eleven at night, so it has to be borrowed from an earlier, quieter afternoon.

What a template can and cannot hold

What you draft in advance is not the finished statement, it is a skeleton with deliberate blanks. Ours has four fixed elements: acknowledgment that something happened, without characterizing it before the facts are confirmed; a single sentence about what is being done right now to address it; a commitment to a specific next update, with a real time attached, not a vague soon; and a named point of contact, because a statement with no named person behind it reads as institutional evasion even when it is not intended that way.

What the template cannot hold is the actual content of the incident, obviously, and organizations sometimes make the mistake of pre-writing too much detail, guessing at scenarios that never happen and then trying to force an unrelated crisis into language written for a different one. The skeleton should be general enough to survive contact with a surprise. If your template only works for a data breach and the actual crisis is a product recall, you have built a document, not a capability.

The goal of a holding statement is never to look like nothing happened. It is to look like someone competent is already handling it, which is a very different and much more achievable claim.

Where common advice oversells transparency

A lot of crisis communication advice tells organizations to be fully transparent immediately, sharing everything known the moment it is known. I think this is well intentioned and often wrong in practice. Releasing unconfirmed details under pressure has burned nearly every organization I have advised at least once, because early information during an incident is frequently incomplete or simply inaccurate, and correcting a public statement later reads far worse than a first statement that was appropriately narrow.

The better standard is not full transparency on hour one, it is accurate transparency delivered on a predictable schedule. Say what you know, clearly mark what you do not yet know, and commit to when you will know more. That is honest without being reckless, and it gives a reporter or a customer something concrete to hold onto besides silence, which is what actually drives the speculation that makes a story worse.

ElementPurposeCommon mistake
AcknowledgmentConfirms awareness without guessing at causeCharacterizing severity before facts are confirmed
Current actionShows competence in motionVague language like "taking this seriously"
Next update timeReplaces silence with a schedulePromising "soon" instead of a specific time
Named contactSignals accountability, not a faceless brandRouting everything to a generic press inbox

One client, a mid sized logistics company, had a warehouse fire two years ago that made regional news for a single news cycle instead of a full week, and the difference, according to the reporter who covered it, was that the first statement arrived within ninety minutes with a named operations director attached to it, followed by an update at the promised time the next morning. Nothing about the fire itself was unusual. What was unusual was that nobody had to guess what was happening next, because the company had already told them.

If your organization does not have a holding statement skeleton sitting ready right now, that is the actual task, not the wording of any specific crisis you are imagining. Draft the four elements this month, get legal and leadership to sign off on the general shape while nobody is under pressure, and file it somewhere findable. The pitch that follows a statement matters too, which is covered in what a journalist actually wants from your pitch, and both connect to the wider discipline in media relations of saying exactly enough, on time, and no more than that.

MD
Marco Delrio

Marco spent nine years pitching journalists before he started writing under his own name. He has drafted statements at two in the morning and watched good ones fall apart in an interview anyway, which is why he writes about what actually earns a reply instead of what a template promises.

More posts by Marco

More from the blog