TemplateChecked 16 November 2026
Incident response checklist template
Sections
The template in full
1 First-hours checklist
Tick each item and write the time. Hand the page to the next shift with the log.
| Step | Done | Time | By |
|---|---|---|---|
| Incident declared. Severity set. Log opened. | [ ] | ||
| Incident lead, technical lead and communications lead called. | [ ] | ||
| Out-of-band channel opened (phone bridge or secure group). | [ ] | ||
| Affected systems, accounts and data listed. Unknowns listed. | [ ] | ||
| Evidence preserved before any change: logs saved, images taken where needed. | [ ] | ||
| Containment actions approved and recorded. | [ ] | ||
| Legal and privacy lead told. Notice clocks started and times recorded. | [ ] | ||
| Insurer and outside responders told, if the policy or plan requires it. | [ ] | ||
| First message to staff approved by the communications lead. | [ ] | ||
| Next update time set and announced. | [ ] | ||
| Handover note written if the shift changes. | [ ] |
2 Form A: incident log
One row per entry. Never edit a row; add a new row to correct it.
| No. | Date and time (zone) | Recorded by | What was observed or done | System or account | Evidence id | Decision and approver |
|---|---|---|---|---|---|---|
| 1 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 2 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 3 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
3 Form B: timeline
Fill in as facts are confirmed. Mark estimates with "est.".
| Event | Date and time (zone) | Source of the time |
|---|---|---|
| First malicious activity | [ ] | [ ] |
| Detected | [ ] | [ ] |
| Reported | [ ] | [ ] |
| Declared | [ ] | [ ] |
| Contained | [ ] | [ ] |
| Notice clock started (one row per rule) | [ ] | [ ] |
| Notices sent (one row per recipient) | [ ] | [ ] |
| Recovery started | [ ] | [ ] |
| Recovery declared complete | [ ] | [ ] |
| Review held | [ ] | [ ] |
4 Form C: handover note
Write this at every change of shift, in under one page.
- Current status and severity.
- Actions open, with owners.
- Decisions waiting, and who must make them.
- People on shift and how to reach them.
- Next update time and audience.
- Where the log and evidence are.
5 Form D: closing report outline
The incident lead completes this before the review meeting.
- Summary in five sentences.
- Timeline (Form B).
- Cause and how it was found.
- Impact: systems, people, data, money, hours.
- Notices sent, to whom and when.
- What worked and what did not.
- Actions: owner, due date, status.
- Changes made to this plan.
About this template
Is there an incident response checklist template?
Yes. CISA's playbook includes Appendix B, an incident response checklist with step, procedure, action taken and date completed columns, and Appendix C, a preparation checklist. The SANS handbook ends with an Incident Handlers Checklist for preparation, identification, containment, eradication, recovery and lessons learned.
This template takes the same idea in a shorter form: a first-hours checklist and four forms to copy into your records system.
Download the template
Free, no sign-up. Word (.docx, 3 KB): download. PDF (49 KB): download. Both files carry the same text as this page, edition 16 November 2026.
Related pages
- Incident response plan templates: the full set
- Free incident response plan template
- Incident response plan template for federal agencies
- Incident response plan template for the UK
- Incident response plan template: Word and PDF downloads
- Incident response plan template for small business
- Incident response playbook: what it is and how to build a library
- Incident response plan: what it contains and how to build one
Sources
- CISA, Cybersecurity Incident & Vulnerability Response Playbooks (November 2021)
- SANS Institute, Incident Handler's Handbook (21 February 2012)
Last reviewed 16 November 2026. Each source above was read that day.