Free tool, runs on your device
Runbook builder
Example: the training orders-api runbook (8 percent checkout errors against a 0.5 percent reference) fills every group below and exports clean Markdown. Your draft stays local; nothing is uploaded and no account is needed.
0 / 8 fields filled (coverage only, never a quality score)
Title and purpose
System and owners
Symptom and impact
Diagnosis checks
Intervention steps
Rollback
Verification and comms
Links, testing, version
Live Markdown preview
# - **Purpose (one sentence)*** - ## System and owners - Service / system*: - - Environment*: - - Scope (in / out): - - Owner role*: - - Escalation role: - ## Symptom and impact - Symptom / alert*: - - User impact: - ## Preconditions and authority* - ## Diagnosis checks 1. Check: - | Expected result: - | If failed, next: - ## Intervention steps 1. Action: - | Risk: - | Stop condition: - ## Rollback - Rollback precondition: - - Rollback steps: - - When rollback is wrong: - ## Verification and comms - Verification / success criteria*: - - Escalation and comms note: - ## Links, testing, version - Links and references (optional): - - Last tested date: - - Version: - - Review note: -
Inputs never leave this device: no backend, no analytics payload, nothing in the URL.
What this tool gives you
- Guided groups instead of one giant form: purpose, system, symptom, checks, actions, rollback, verification.
- Steps you can add, remove and reorder with the keyboard; no drag and drop required.
- Live Markdown preview, clipboard copy with manual fallback, UTF-8 .md download with a safe filename.
- Versioned JSON export and import with size limits; a broken file never destroys your draft.
- Opt-in storage on this device only; clearing removes just this tool's key.
Prefer files? Blank template · Filled orders-api example · Runbook concept
Next: runbook discipline is part of shipping, see Production delivery for FDEs.
Straight answers
Frequently asked questions
What does the runbook builder produce?
Readable Markdown from your fields: title, system, symptom, checks with expected results, actions with risks, rollback, verification and owner. The same structure as the blank template and the filled orders-api example.
Is my runbook text sent anywhere?
No. Everything stays in your browser; saving is opt-in on this device only. Analytics events carry the tool ID and locale, never your text.
What should I do before trusting the output on-call?
Fill every section, name a real owner, set a test date and walk it as a tabletop exercise. Coverage here counts filled fields; it never scores quality or readiness.
How is this different from the runbook glossary page?
The glossary page teaches the concept with a worked example; this tool produces your document. Start with the concept if the terms are new.