First-Hour Incident Checklist + Communications Template

A practical first-hour playbook for small organisations: contain, preserve, decide, and communicate with less chaos.

Security Incident Response Continuity Ops
Goal
Reduce decision delay in the first hour of an incident by defining the first actions, key roles, and basic communications flow in advance.

1) First-hour checklist

  1. Contain: isolate affected accounts, devices, or systems if that is safe to do.
  2. Preserve: keep evidence before wiping, rebuilding, or making major changes.
  3. Decide: confirm who leads, who approves, and what the immediate recovery priority is.
  4. Communicate: use one owner for facts and messages.
  5. Record: note what happened, what was done, and what still needs deciding.

2) Roles to pre-assign

RoleName / ownerWhat they decide / do
Incident leadOwns the operational response and next actions.
Business approverApproves material actions and business-impact decisions.
Technical responderRuns containment, investigation, and recovery tasks.
Comms ownerControls internal and external messaging.

3) Internal communications template

Subject: [Incident update] [System / issue] - initial note What we know: • [Short factual summary] What we are doing now: • [Containment / investigation / recovery steps] What staff should do: • [Pause action / avoid clicking / use backup process / contact point] Next update: • [Time / trigger for next communication]

4) Questions to ask during the first hour

5) Common gotchas

Note: This document is general operational guidance and does not replace legal advice. It helps you establish a practical baseline and reduce common privacy risks.
👉 Free 30-minute consultation

No hard sell - just clarity and practical next steps.

hello@virtusgroup.biz
virtusgroup.co.nz
0800 847 887 (VIRTUS)

Book now