Skip to content

How do I communicate an incident to my team without panic?

Saying nothing breeds rumors. Saying too much breeds panic. Three rules for a first statement.

Try this first

  1. 1Honest but no details. 'There is a possible security incident, we are investigating. I will share what we know by end of day.' That is enough.
  2. 2Give concrete actions: 'For now, change passwords, re-run MFA when asked. Do not click on new links until we say so.'
  3. 3Designate one fixed contact for questions. Stops 'I heard from a colleague' loops.
  4. 4Update at least once a day until resolved. Silence = people invent stories.
  5. 5On wrap-up: short explanation of what happened, what we did, what lesson we draw. Prevents repeats.

When to bring us in

On larger incidents with customer communication or possible notification duty: do not write the customer mail solo. We help with phrasing that is legally and empathically sound.

See also

None of the above fits?

Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.

Who are you?

For the AI question we need your email and company, so we can follow up if the AI gets stuck, and to prevent abuse.

Limited to 2 questions per hour and 5 per day, kept lean so the AI stays useful. For more, contacting us directly works better for you and us.

Or skip the DIY entirely

Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.