# Runbook

> A short, tested document that says what to do when a specific alert fires: which checks to run, which command to execute, when to escalate. A runbook that a system can execute by itself is automation; one that a person reads at 3 a.m. is still worth writing.

Reliability

## In Quorum

The Runbooks Research (Series A, after On-call) and an SRE team with an engineer unlock Write a runbook, 10 Dev Hours, for one incident kind the team has already ended by hand. Once it is written, that kind resolves on its own on the first Step. The postmortem records it as automatic, as it does a Cluster rescheduling a pod or a standby failing over, and the Runbook achievement reads that record.

## Design

[Runbooks](https://wiki.playquorum.dev/design/11-incidents.md#runbooks)

## Read next

[MTTR](https://wiki.playquorum.dev/glossary/mttr.md), [MTTD and MTTA](https://wiki.playquorum.dev/glossary/mttd-and-mtta.md), [On-call](https://wiki.playquorum.dev/glossary/on-call.md), [Blast radius](https://wiki.playquorum.dev/glossary/blast-radius.md)

## Learn more

- [Google SRE book: Postmortem culture](https://sre.google/sre-book/postmortem-culture/)
- [PagerDuty: What is a runbook?](https://www.pagerduty.com/resources/automation/learn/what-is-a-runbook/)

## See also

- [Glossary](https://wiki.playquorum.dev/glossary.md)

Source: https://wiki.playquorum.dev/glossary/runbook