Skip to content
Incident Response Plan Templates

TemplateChecked 16 November 2026

Incident response checklist template

Download Word (.docx)Download PDF

Sections

  1. 1First-hours checklist
  2. 2Form A: incident log
  3. 3Form B: timeline
  4. 4Form C: handover note
  5. 5Form D: closing report outline

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.

First-hours checklist
StepDoneTimeBy
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.

Form A: incident log
No.Date and time (zone)Recorded byWhat was observed or doneSystem or accountEvidence idDecision and approver
1[ ][ ][ ][ ][ ][ ]
2[ ][ ][ ][ ][ ][ ]
3[ ][ ][ ][ ][ ][ ]

3 Form B: timeline

Fill in as facts are confirmed. Mark estimates with "est.".

Form B: timeline
EventDate 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.

  1. Summary in five sentences.
  2. Timeline (Form B).
  3. Cause and how it was found.
  4. Impact: systems, people, data, money, hours.
  5. Notices sent, to whom and when.
  6. What worked and what did not.
  7. Actions: owner, due date, status.
  8. 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.

Sources

  1. CISA, Cybersecurity Incident & Vulnerability Response Playbooks (November 2021)
  2. SANS Institute, Incident Handler's Handbook (21 February 2012)

Last reviewed 16 November 2026. Each source above was read that day.