# How to write an incident response playbook

Guide, read 16 November 2026

**The short answer.** Write a playbook by choosing one scenario, listing prerequisites, drafting a numbered workflow with an owner for each step, marking decisions, and testing it with someone who did not write it. This page, read on 16 November 2026, gives the method, a layout comparison and the sources.

## 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.

| Layout | Best for | Limit |
| --- | --- | --- |
| Numbered checklist | Linear tasks such as phishing clean-up | Branches are awkward |
| Table of decisions | Choices with several inputs | Needs a short key |
| Flowchart | Branching investigations | Hard to read at 3 a.m. alone |

Which layout should a playbook use?

## 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](/playbooks/incident-response-playbook-template/) to start, and compare with the [plan](/plans/incident-response-plan-vs-playbook/).

## Related pages

- [Incident response playbook: what it is and how to build a library](/playbooks/)
- [Free incident response plan template](/)
- [Third-party and supplier incident response playbook](/playbooks/third-party-incident-response-playbook/)
- [What is an incident response playbook, and what is it for?](/playbooks/what-is-an-incident-response-playbook/)
- [Incident response playbook template](/playbooks/incident-response-playbook-template/)
- [Incident response playbook for phishing](/playbooks/incident-response-playbook-phishing/)
- [Incident response plan templates: the full set](/templates/)
- [Incident response steps: the order and who does what](/steps/)

## Sources

- Microsoft Learn, Incident response playbooks overview: https://learn.microsoft.com/en-us/security/operations/incident-response-playbooks (read 16 November 2026)
- Microsoft Learn, Phishing investigation playbook: https://learn.microsoft.com/en-us/security/operations/incident-response-playbook-phishing (read 16 November 2026)
- NIST SP 800-61 Rev. 3, full text (April 2025): https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/playbooks/how-to-write-an-incident-response-playbook/
