Bad news is hardest to hear when people cannot tell what happened, how it affects them, or who is responsible for next steps. Prepare the verified facts and the human impact before drafting a clever opening line. The aim is to be clear and useful, not to make an unpleasant fact sound like good news.
Build the message in the right order
Start with the central fact in ordinary language. Explain what is known about the effect on customers, staff, or the public. Say what has already been done, what remains uncertain, and where people can get help. An audience should not have to read several paragraphs of company background before learning whether they need to take action.
Choose the channel according to the stakes. A private, directly affected group may need individual contact before a public announcement; a broad safety issue may require an accessible public notice as well. Ready.gov recommends planning the communication needs of a business before an emergency. Make sure the same approved information reaches the call center, website, staff, partners, and spokesperson.
Prepare for questions you would rather avoid
What happened?
Separate established facts from working hypotheses. State the source of a number or timeline if it matters.
Who was harmed?
Describe the known scope and the steps affected people should take; do not reveal private information to prove that you are being transparent.
Why did you not act sooner?
Give the documented sequence and explain a delay honestly. Do not blame an unnamed team or invent a reassuring motive.
When will this end?
Offer a milestone and next update time if the completion date is unknown. Follow up when promised, even if the answer has not changed.
Listen and correct the record
A difficult question may contain anger, fear, or a detail the response team has missed. Let the question finish. Answer the point asked, acknowledge impact without arguing about feelings, and give a specific follow-up route if the answer requires checking. Repeating a prepared slogan can sound evasive, especially when someone asks about a concrete loss.
The PRSA ethics code calls for accuracy and truth. If a public answer proves wrong, correct the same channel and make the change easy to find. Keep a question log so recurring concerns improve the next update and the underlying response. Credibility is built through verifiable action after the announcement, not by the spokesperson's composure alone.