JournalCrisis communications

How to Write a Holding Statement, With Structure and Examples

A holding statement buys time without conceding anything you cannot yet confirm. Here is the five-part structure, four worked examples, and the phrases that reliably make things worse.

The Brillaince team13 September 20268 min read

A holding statement is a short, pre-approved public message issued at the start of a crisis. It shows that the organisation is aware, present and taking the matter seriously, while committing to nothing that is not yet verified.

A holding statement is the most-used document in crisis communications and the one most teams write worst, usually because they are writing it for the first time while the thing is already happening.

Its job is narrow. It exists to establish that you are aware, present and taking the matter seriously, while committing to nothing you cannot yet verify. It is not a response, not a defence and not a resolution. Teams get into trouble when they try to make it do all three.

The five components

Every workable holding statement contains these, usually in this order, and usually in one short paragraph each or less.

Awareness. You know. Say so plainly and early, because the gap between something becoming public and a company acknowledging it is the space in which people conclude you are hiding.

What you can confirm. Only facts that are actually established. If that is very little, say very little. “A vehicle was involved in an incident at our Coimbatore site this morning” is a confirmable fact. “We believe this was caused by a third party” at hour one is not, even if it turns out to be true.

What you are doing. The concrete action already underway. Investigating is acceptable if it is genuinely happening and you can name who is doing it. Better is anything more specific: the site is closed, the product has been withdrawn from sale, the account has been suspended pending review.

Who is affected and what they should do. Skipped constantly, and the component that most separates a statement written for the public from one written for the company. If customers need to stop using something, check something or contact someone, that instruction belongs near the top, not in a follow-up.

When you will say more. A specific commitment you can keep. “We will provide an update by 6pm today” is strong if you will actually do it. If you cannot commit to a time, “we will update as soon as we have verified information” is weak but honest, and preferable to a deadline you miss.

Four worked examples

These are illustrative structures rather than templates to paste. The wording should always be yours, because a statement that reads like it came from a template is immediately recognisable as one.

A product safety concern.

We are aware of reports concerning [product], and we are treating them with the seriousness they deserve. We have paused sale and distribution of the affected batch while we investigate. Anyone who has purchased [product] with batch code [X] should stop using it and contact us at [channel]. We expect to provide a further update by [time], and we will share what we find whether or not it is comfortable for us.

The last clause is optional and does real work. It pre-commits to disclosure, which is both a useful discipline internally and the sort of thing that gets quoted favourably later.

A data incident.

We identified unusual activity on one of our systems on [date] and took it offline immediately. We are working with external security specialists to establish what happened and what information may have been involved. We have not yet confirmed whether customer data was accessed. We are contacting the relevant authorities. We will write directly to anyone affected as soon as we have established the facts, and we will publish an update by [time].

Note what is absent. No reassurance that data is safe, because that is not yet known, and it is the single most common thing companies say early and retract later.

An allegation about an individual at the company.

We are aware of the allegations reported today concerning a member of our team. We take them seriously. The individual has been suspended while an independent review is conducted. Out of fairness to everyone involved, including the person who raised the concern, we will not comment further on specifics while that review is underway. We will act on its findings.

The restraint here is deliberate and defensible. This is one of the few situations where declining to comment on detail reads as appropriate rather than evasive, provided the reason is stated.

A service outage.

[Service] has been unavailable since approximately [time]. The cause has been identified and our engineering team is working on a fix now. We do not yet have a confirmed restoration time. We will post an update here every thirty minutes until this is resolved, including if there is nothing new to report.

The commitment to update even when there is no news is the part that matters. Outage anger is driven far more by silence than by downtime.

The phrases that reliably make it worse

“We take this extremely seriously.” Present in almost every corporate statement ever issued, which is exactly why it now signals nothing. Demonstrate seriousness with the action you describe instead.

“An isolated incident.” Asserted early, quoted permanently, and frequently contradicted within days by the second and third reports that arrive once the first is public.

“There is no evidence that…” Technically true at hour one because nobody has looked yet. Reads as a denial. When evidence subsequently appears, this sentence becomes the headline.

“We apologise for any inconvenience caused.” Appropriate for a delayed delivery. Actively inflammatory when something serious has happened to someone, because it categorises their experience as an inconvenience.

“Our customers’ safety is our top priority.” If it needs saying it is not being demonstrated. Describe what you did instead.

Passive constructions that remove the actor. “Mistakes were made” and its relatives. Audiences notice, and it is read as exactly what it is.

Timing, channel and approval

Publish where the story is happening. A statement on a corporate newsroom that receives four hundred visitors a month is not a response to something moving on social. Post in the channel where the conversation is taking place, then link to a fuller page if one exists.

Send to journalists who have asked, before they file rather than after. A reporter working on a piece who has your statement will usually include it. The same reporter who received nothing will publish “the company did not respond to a request for comment”, which is a materially worse sentence to appear in the record.

Keep approval to one named person. Statements that require sign-off from three executives are statements that publish two hours late, and the delay is almost always more damaging than the wording improvements the extra review produced.

What to prepare before you need it

The reason most holding statements are bad is that they are written under time pressure by people who have never written one. This is entirely fixable on an ordinary afternoon.

Draft three or four skeletons for the scenario types your business realistically faces, which for most companies means some combination of product failure, data incident, staff conduct, service interruption and supply chain. Leave the facts blank. Agree the approval chain and write down who deputises when the approver is on a plane. Store them somewhere reachable from a phone, not on a shared drive behind a VPN that nobody can log into at the weekend.

Then the work during the actual first hour becomes filling in specifics rather than inventing structure, which is the difference between publishing at minute fifty and publishing at hour three. What else belongs in that hour is covered in the first sixty minutes, and knowing you need one at all is the job of crisis detection.

Common questions

What goes in a holding statement?

Five things: confirmation that you are aware, only what you can currently confirm as fact, what you are doing about it, who is affected and what they should do now, and when you will say more. Anything beyond those five is usually a sentence you will regret once the facts are established.

What is the difference between a holding statement and an apology?

A holding statement establishes that you are present and looking into something. An apology accepts responsibility. Issuing an apology before the facts are known creates liability for something that may not be yours, and issuing a holding statement where an apology is clearly warranted reads as evasion. The choice depends entirely on whether the facts are settled.

How long should a holding statement be?

Under a hundred words in most cases. Length reads as defensiveness, and every additional sentence is another thing that can be quoted back at you when more facts emerge. The first response is not the place to make your full argument.

When should a holding statement be issued?

Once you have confirmed something real is happening and before the first substantial press cycle forms, which usually means within the first hour or two. Speed matters, but publishing before you know whether the claim is even about your company is worse than publishing thirty minutes later.

Should a holding statement be posted publicly or sent to journalists only?

Put it where the conversation is. If a story is developing publicly on social, a statement issued only to reporters leaves the public conversation unanswered for hours. If a single journalist is working on a piece and nothing is public yet, responding to them directly is usually sufficient.

The short answer

What goes in a holding statement?

A holding statement buys time without conceding anything you cannot yet confirm. Here is the five-part structure, four worked examples, and the phrases that reliably make things worse.

Get started

Easier to judge on real data.

Everything argued here is quicker to see than to read about.

Book a Demo