The public statement, before legal writes it
The first public statement after a difficult event is a brand document as much as a legal one, and it is usually drafted by the wrong department first. This piece sets out why legal’s instinct to say as little as possible collides with what patients and the market need, and how communications should co-author that statement from minute one.
The document nobody assigned an owner to
Every hospital group has a crisis manual somewhere, usually in a shared drive nobody has opened since the consultant who wrote it left. It has an escalation tree, a list of spokespeople, a media contact sheet with three numbers that no longer work. What it almost never has is a clear answer to a simple question: who drafts the first sentence the public sees.
In the absence of an answer, the default is legal. Not because anyone decided it should be, but because legal is the function that gets called first when something goes wrong, and the person who gets called first ends up holding the pen. By the time communications is looped in, there is already a draft, and the draft already has a shape — cautious, passive, hedged, three paragraphs of process language before anything resembling a human sentence.
This is not a complaint about legal. Legal is doing exactly what it is designed to do. The complaint is about sequencing. A statement drafted to survive a deposition and a statement drafted to be read by a frightened family, a nervous board and a scanning journalist at the same time are not the same document, and writing the first one first makes writing the second one much harder to undo.
What legal is trained to optimize for
Legal’s job in a difficult moment is to minimise exposure. That means minimising admission, minimising specificity, minimising anything that could be read later as a concession of fault. It is a discipline built around a courtroom that may or may not ever exist, years from now, in front of an audience that reads documents literally and slowly.
The instinct is defensible on its own terms. The problem is that the audience reading the first statement is not a judge. It is a family that wants to know the organisation understands what has happened to them. It is staff who will be asked about it by neighbours before the internal briefing reaches them. It is referring doctors deciding whether to keep sending patients. It is, increasingly, a market — investors, analysts, rating agencies — reading tone as a proxy for management quality. None of these audiences is parsing the statement for admissible language. They are parsing it for whether the organisation sounds like it is in control of itself.
A statement written only to survive litigation tends to fail all of these audiences at once, because the qualities that protect it legally — vagueness, distance, the passive voice — are the exact qualities that read as evasive to everyone else. The organisation ends up legally cautious and reputationally exposed, which is a worse trade than either function intended.
What the market and the patient actually need
In my experience, what a first statement needs to do is narrow: acknowledge that something serious has happened, say what immediate step has been taken, name a clear channel for people who need direct answers, and commit to a timeline for saying more. That is the entire job. It does not need to explain, apportion or predict. It needs to sound like a person wrote it under pressure and kept their composure.
This is a narrower brief than legal usually drafts to and a narrower brief than communications usually wants to write, because communications’ instinct under pressure is often to over-explain — to reach for warmth, context, reassurance, all of which can read as spin if the facts are still moving. The discipline on both sides is restraint, aimed at different failure modes. Legal restrains to avoid liability. Communications should restrain to avoid sounding like it is managing a story rather than responding to an event.
Patients and families, in particular, are listening for one thing above all else: does this statement sound like it was written before or after someone checked how it would look. A statement that reads as though it was cleared through six people before a single fact was confirmed fails that test even when every word in it is accurate.
The two failure modes
Saying too little
The legal-only draft tends to fail by silence. It waits for full certainty before saying anything, which in a fast-moving news cycle means the organisation is the last party to comment on itself. Journalists, competitors and social media fill that vacuum long before the statement clears review, and by the time it does, the organisation is responding to a narrative rather than setting one. Silence is read as either indifference or guilt, rarely as prudence, no matter how sound the legal logic behind it.
The fix is not to abandon caution. It is to separate what is uncertain — cause, fault, clinical detail — from what is not: that an event occurred, that it is being looked into, that a named channel exists for people who need direct contact. That much can almost always be said early, without waiting for the fuller picture, and saying it early is what buys the organisation the room to be slower and more careful with everything that follows.
Saying it in the wrong voice
The opposite failure is a statement that says enough but sounds wrong — either too clinical and distant, all process and no acknowledgment, or too soft and promotional, leaning on brand language at a moment when brand language reads as tone-deaf. Both versions are usually the product of a document drafted by one function and lightly edited by another, rather than authored jointly from the first line.
Voice is not a cosmetic layer applied after the legal content is settled. It is load-bearing. A statement that is legally accurate but sounds like a form letter does as much reputational damage as one that says too much, because it confirms the exact suspicion the audience already has — that the organisation is protecting itself first and the people affected second, whatever the words technically say.
Co-authorship, not sign-off
The structural fix is unglamorous: communications and legal draft the first statement together, in the same room or the same call, from the first sentence, rather than one function writing and the other reviewing. Review is where co-authorship goes to die, because a reviewer’s job is to flag risk, not to shape voice, and a document that has been reviewed by legal after the fact almost always reads as though it has been reviewed by legal after the fact.
Co-authorship works differently. Legal states the constraints up front — what cannot be said, what cannot be implied, what needs a qualifier — and communications writes inside those constraints rather than around them. This is a faster process than it sounds, because most of the friction in crisis drafting comes from redrafting after the fact, not from the constraints themselves. A ten-minute conversation before the first draft saves three redraft cycles after it.
The output of co-authorship is usually shorter than either function would have produced alone — legal because communications resists padding the statement with process language that reads as filler, communications because legal resists language that reaches further than the facts support. Short, in a first statement, is almost always the right length.
The room, built before you need it
None of this works if the first time legal and communications negotiate a statement together is during an actual event. The relationship, the shorthand, the mutual trust that lets each function move fast without re-litigating the other’s judgment — all of that has to exist before the pressure does.
In practice this means a standing arrangement, not a one-off meeting: a named counterpart on each side, a shared template for a first statement that both functions have already agreed to, and at least one dry run a year where the two teams draft a statement together against a hypothetical, timed, with the same speed constraints a real event would impose. The dry run is worth more than the template, because it is where each side learns how the other actually thinks under time pressure, which is not the same as how they think in a planning meeting.
The organisations that handle a difficult moment well are rarely the ones with the most polished manual. They are the ones where the legal lead and the communications lead have already argued about a statement once before, in a low-stakes setting, and worked out where each of them will bend.
Tone is a brand decision, not a legal one
One distinction is worth holding onto through all of this: legal should own the boundaries of what can be said. Communications should own how it is said inside those boundaries. When that division blurs — when legal starts editing for tone, or communications starts negotiating legal exposure — both functions end up doing the other’s job badly.
Tone is not a soft consideration layered on top of the real, legally serious work. It is the thing the audience actually reacts to. A statement’s word choice, its length, whether it opens with an acknowledgment or a disclaimer, whether it names a person or hides behind “the organisation” — these are brand decisions with real consequences for how the next weeks unfold, and they deserve the same seniority in the drafting room as the legal review does.
This is also why the communications lead in that room needs enough seniority to hold a position under pressure. A junior communications resource in a room with senior legal counsel will defer on tone as readily as on liability, and the statement will read exactly like what it is: legal language with a coat of paint.
The approval chain that kills a statement
Even a well co-authored statement can die in the approval chain. Every additional sign-off — a regional head, a board member, an external counsel, a promoter’s office — adds a layer of caution and a delay, and the two compound. By the fourth reviewer, the statement has been sanded down to something so safe it says almost nothing, and it has taken so long to clear that it is now answering questions the news cycle has already moved past.
The fix, agreed in advance rather than negotiated in the moment, is a capped approval chain for the first statement specifically: a named short list of people who can sign off, a time limit on how long any one of them can sit on it, and a default that if the clock runs out without a response, the co-authored draft goes out as written. Later statements, with more time and more certainty, can go through a fuller process. The first one cannot.
I have watched a good statement get worse with every additional approval, not because any single reviewer was wrong, but because nobody was accountable for the cumulative effect of ten reasonable edits. A capped chain exists to protect against that specific failure.
What good looks like
A first statement that works tends to share a small number of traits, regardless of what the event was:
- It goes out within a defined window, not when it happens to be ready.
- It was drafted jointly by legal and communications, not sequentially.
- It says what happened in the broadest accurate terms, what immediate action was taken, and where people can get direct answers.
- It commits to a timeline for the next update, and that timeline is kept.
- It reads as though a specific person is accountable for it, not an anonymous institution.
- It went through a capped approval chain agreed before the event, not negotiated during it.
A service line rarely dies from a single bad quarter, and a reputation rarely dies from a single difficult event either. What does the damage, almost every time, is the gap between what happened and what the organisation was seen to say about it — and that gap is set in the first hours, by whoever happened to be holding the pen.
Questions people ask
Why does legal usually draft the first statement after a difficult event?
Legal is typically the first function notified when something serious happens, and the person who is called first ends up holding the pen by default rather than by design. There is rarely a pre-agreed answer to who owns the first public sentence, so the role falls to whichever function responds fastest, which in most hospital groups is legal. This is a sequencing problem, not a competence problem — legal is doing its job well, just in a drafting role it was never meant to hold alone. The fix is not to remove legal from the process but to bring communications into the room at the same moment, so the first draft is shaped by both disciplines from the start rather than handed from one to the other.
What is the difference between a legally safe statement and a brand-safe statement?
A legally safe statement minimises admission, specificity and anything that could be read later as a concession of fault, written for an audience that may parse it literally in a courtroom years from now. A brand-safe statement is written for the audience actually reading it in the moment — patients, families, staff, referring doctors, investors — who are judging whether the organisation sounds composed and in control, not whether individual clauses are legally airtight. The two documents share most of their content but differ in tone, pacing and how directly they acknowledge what happened. A statement optimised only for legal safety often reads as evasive to every other audience, which creates reputational exposure that the legal caution was meant to prevent.
Should communications or legal have final sign-off on a crisis statement?
Neither should have unilateral final sign-off; the two functions should own different parts of the same document. Legal should set the boundaries of what can be said and what needs qualification, since that reflects real risk. Communications should own how it is said within those boundaries — word choice, structure, tone, whether the statement acknowledges the audience’s concern before it explains process. When one function is allowed to override the other’s domain, the statement degrades: legal editing for tone produces cold, evasive language, and communications negotiating legal exposure creates real risk. A capped, jointly agreed approval chain, decided before any event occurs, works better than an informal hierarchy where whoever is more senior in the room wins the argument.
How fast should the first public statement go out after a difficult event?
There is no universal number, but the organisation should agree on a specific window in advance rather than deciding in the moment, because “as soon as it’s ready” almost always means too slow. A defined window — for example, before the end of the same news cycle — forces the drafting process to separate what is certain from what is not, rather than waiting for full certainty before saying anything. What matters more than the exact time limit is that everyone involved in drafting and approving the statement knows the deadline going in, because a shared deadline is what stops the approval chain from quietly extending itself one reasonable request at a time.
What should and should not be included in a first statement?
A first statement should include an acknowledgment that something serious has happened, in the broadest accurate terms; a description of the immediate step taken in response; a named, direct channel for people who need answers right away; and a commitment to a specific timeline for further updates. It should not include speculation about cause, any language that apportions fault, or clinical or operational detail that has not been confirmed. The discipline is narrowness, not silence — saying a fixed, factual amount early is almost always better than waiting for a fuller picture, because the organisation that says nothing early is read as either indifferent or evasive, regardless of how sound its legal reasoning is.
How do we build a working relationship between legal and communications before a crisis happens?
The relationship needs to exist before the pressure does, which means a standing arrangement rather than an ad hoc one: a named counterpart on each side who knows the other by name and working style, a shared statement template both functions have already agreed to, and at least one dry run a year where the two teams draft a statement together against a hypothetical scenario under a real time constraint. The dry run matters more than the template, because it is where each function learns how the other actually behaves under time pressure — which is different from how they behave in a planning meeting — and where the inevitable disagreements about tone versus caution get worked out once, calmly, instead of for the first time during an actual event.
Why does an approval chain sometimes make a crisis statement worse?
Every additional reviewer in an approval chain adds a layer of caution and a delay, and both compound. Each individual edit — a softened word, a hedged clause, an added qualifier — is defensible on its own, but by the time a statement has passed through four or five reviewers, it has often been sanded down to something so vague it says almost nothing, and the delay means it is now answering a news cycle that has already moved on. No single reviewer is responsible for this outcome; it is a cumulative effect nobody is accountable for preventing. The fix is a capped approval chain for the first statement specifically, agreed in advance, with a named short list of approvers and a time limit after which the co-authored draft goes out as written.
Who should be the public spokesperson after a difficult event?
The spokesperson question is separate from the drafting question but follows the same logic: it should be decided in advance, not improvised. In most cases the strongest choice is a named, senior clinical or administrative leader who can speak with authority and composure rather than an anonymous “spokesperson for the organisation,” because audiences respond differently to a statement that is visibly owned by a specific person. That person needs to be media-trained before an event occurs, not during one, and needs to be briefed jointly by legal and communications so their public remarks stay consistent with the written statement rather than drifting from it under questioning.
How is a first statement different from later, fuller updates?
The first statement operates under near-total uncertainty and extreme time pressure, so its job is narrow: acknowledge, act, direct, and commit to a timeline. Later updates operate with more facts and more time, so they can carry more explanation, more context and, where appropriate, more specificity about what has been found and what is being done about it. Treating the first statement like a smaller version of the final report is a common mistake — it tries to do too much too early, which either slows it down past the point of usefulness or forces it to speculate. The first statement’s only job is to buy the organisation room to get the fuller updates right.
Does a difficult event always require a public statement, even a small one?
Not every internal issue requires a public statement, and issuing one for something that was never going to attract outside attention can create more risk than it resolves. The judgment call is whether the event is likely to reach patients, families, media or investors through any channel the organisation does not control — word of mouth, social media, a regulatory filing, a competitor. If that likelihood is real, a proactive statement on the organisation’s own terms is almost always better than a reactive one written after the story is already being told by someone else. This is a joint call between legal and communications, made quickly, using the same pre-agreed criteria rather than a fresh debate each time.
How should a hospital group communicate with investors during a difficult event, separate from the public statement?
For a listed or investor-backed group, the public statement and the investor communication are related but not identical, and both should be prepared by the same core team to keep the tone and facts consistent. Investors and analysts are typically less interested in the emotional register of the statement and more interested in scope, financial exposure, and management’s process for handling it — so the investor-facing note can be more direct about materiality and next steps than the public statement needs to be. What both documents share is the same underlying discipline: say what is known, commit to a timeline, and avoid speculation that later has to be walked back, because a walked-back statement damages credibility with investors even faster than it does with the public.
What is the single biggest mistake hospital groups make with their first public statement?
The biggest mistake is treating the first statement as a legal document with a communications review, rather than a jointly authored document from the outset. That sequencing — draft first in legal, then hand to communications for a tone pass — produces exactly the failure mode both functions are trying to avoid: language that is legally cautious but reads as cold, evasive or distant to everyone else reading it. The second most common mistake is not having a capped approval chain agreed in advance, which lets a defensible statement get slowly diluted by well-intentioned edits until it says almost nothing and arrives too late to matter. Both mistakes are structural, not a failure of any individual, and both are fixable before the next event, not during it.
