When an issue becomes visible, the pressure to say something can be intense. The harder question is not whether to communicate, but how much detail to share.

The answer is rarely ‘everything’. The right level of detail is the detail that helps people understand what happened, what it means for them, what action is being taken and when they will hear more.

In a developing issue, clarity matters more than completeness. If the full picture is not yet known, say what is confirmed, what is still being checked and what the organisation is doing next.

Start with what the audience needs to know

Detail should serve a practical purpose. Before issuing a statement, ask what the audience needs to decide or do.

Customers may need to know whether they can use a product or service. Staff may need instructions on what to say and where to escalate questions. Regulators may need evidence that risks are contained. Media may need a clear statement and a reliable update point.

A public holding statement does not need the same depth as a regulator briefing. A staff message may need more operational guidance than a media response. The mistake is assuming one message can carry every detail for every audience.

Share verified facts, not speculation

A useful rule is simple: verified facts first, qualified facts second, speculation never.

Speed matters, but fast misinformation creates a second problem. If facts are still being checked, use plain qualifiers such as ‘based on information currently available’ or ‘we are confirming the scope’. Avoid confident language if the evidence is incomplete.

Accuracy does not mean silence. A weak update says only, ‘We are investigating.’ A stronger update explains the process: what has been paused, who has been notified, what is being reviewed and when the next update will come.

Match the detail to the risk

The more direct the impact on people, the more clearly the organisation must explain the risk and response.

Use the harm test. If someone could suffer physical, financial, emotional or operational harm from missing a detail, include it. If the detail only satisfies curiosity, hold it back or place it in a later background document.

High-severity issues usually need a factual chronology: when the organisation became aware, what action followed and what remains under review. Lower-severity matters may need only a short explanation, a clear remedy and a next update.

When too much detail becomes a problem

Too much detail can confuse people, bury the action they need to take and create avoidable risk.

Long statements often answer internal anxieties rather than stakeholder needs. People do not need every step in the organisation’s escalation process. They need to know whether they are affected, what they should do and how the issue is being controlled.

Excessive detail can also create new questions. Partial technical information may be misunderstood without context. Internal process notes may expose gaps before they have been assessed. Names, private data and sensitive operational specifics should be handled carefully.

What good crisis communication looks like

  • Lead with confirmed impact and required action.
  • Separate verified facts from matters still under investigation.
  • Tailor detail for staff, customers, regulators, media and other stakeholders.
  • Use short updates rather than one overloaded statement.
  • Remove private, sensitive or unnecessary operational detail.
  • Set a clear time or trigger for the next update.

Article curated with AI based on a question we wished we had once asked, all reviewed by Bastion Reputation’s specialist team.