Skip to content
Incident Response Plan Templates

GuideChecked 16 November 2026

How to write an incident response playbook

Open the free templateRead the method

How do you write an incident response playbook?

Follow six moves. First, name one scenario and its trigger. Second, list prerequisites: logs, access and tools. Third, write the workflow as numbered steps with one action and one role each. Fourth, mark each decision with who decides and on what facts. Fifth, list the notices to check. Sixth, define exit criteria.

Then give the draft to a person who did not write it and watch them follow it. Fix every place they hesitate.

  1. Name the scenario and trigger.
  2. List prerequisites.
  3. Draft the workflow.
  4. Mark decision points.
  5. List notices to check.
  6. Set exit criteria, then test with a fresh reader.

Which layout should a playbook use?

Use a checklist for short procedures, a table where a decision needs several facts, and a flowchart where branches matter. Microsoft pairs a workflow diagram with a checklist for each playbook, noting the checklist can help in highly regulated environments to verify what has been done.

Which layout should a playbook use?
LayoutBest forLimit
Numbered checklistLinear tasks such as phishing clean-upBranches are awkward
Table of decisionsChoices with several inputsNeeds a short key
FlowchartBranching investigationsHard to read at 3 a.m. alone

What is the difference between a playbook and a runbook?

The sources read for this site define playbooks but do not define "runbook" as a separate term. NIST uses the words procedures and playbooks, and says procedures explain how technical processes are performed. A common practice is to keep the decision flow in the playbook and the tool commands in an attached procedure.

Use the blank template to start, and compare with the plan.

Sources

  1. Microsoft Learn, Incident response playbooks overview
  2. Microsoft Learn, Phishing investigation playbook
  3. NIST SP 800-61 Rev. 3, full text (April 2025)

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