During a digital incident, silence creates rumours and premature certainty creates inaccuracies. Communication needs to move at the same pace as the technical investigation, without revealing sensitive details or promising a recovery time nobody knows.
Assign one message owner
One person gathers confirmed information and maintains a single version of events. They do not decide everything alone, but prevent departments from giving contradictory answers. Record a deputy and an out-of-hours approval process.
Separate facts, impact and hypotheses
Every update should state what has been confirmed, who is affected, what the team is doing and when the next update will arrive. Possible causes remain internal until supported by evidence. Saying “we are investigating” is useful when accompanied by a specific time for the next update.
Adapt the message to its audience
Technical teams need logs, scope and actions. Support needs answers and known limitations. Customers need the impact, an alternative route and a time to check back. Management needs risks, decisions and required resources.
Do not hide uncertainty
Avoid absolute claims such as “no data was affected” before the investigation is complete. Explain what has been checked and what remains open. Careful accuracy protects trust better than a reassuring statement that is later overturned.
Maintain a communication timeline
Record the time, channel, recipients, exact message and approval. The timeline supports review and shows what the team knew at each moment. Protect the record from uncontrolled editing.
Close the incident with substance
The final update explains what has been restored, whether users need to act and which measures follow. Do not present speculation as the root cause. Once the analysis is complete, publish an appropriate level of detail and track commitments.
This incident communication framework is an original operational guide developed by DigitalNow.