Free for 30 days on Scale.Start free
Run9 steps2-3 weeks of focused setup, ongoing thereafter

Set up incident response and postmortems

Production reliability process: severity ladder published, on-call rotation paid, runbooks linked from every alert, blameless postmortems run on every Sev-1+, action items tracked to closure.

Open in DockSee every step →

Production reliability process: severity ladder published

Production reliability process: severity ladder published, on-call rotation paid, runbooks linked from every alert, blameless postmortems run on every Sev-1+, action items tracked to closure.

Spin up an agent for the heavy lifting

Drafts the postmortem from the incident timeline, Slack transcript, and the runbook actually used during the incident.

9 steps, 17 official links, 3 agent prompts

Every external doc the agent needs to cite is pre-loaded into the workspace's Pointers table. No hunting for the right URL mid-draft.

What's inside

Pre-loaded so day one is execution.

5Surfaces
9Steps
3Agent prompts
17Official links
6Tools mapped
Surfaces
  • tableSteps
  • tableIncidents
  • docRunbooks
  • tablePostmortems
  • docStatus
See every step, link, and prompt
How the loop works

Your agent works. Dock shows you what happened.

Open this template and you get a workspace seeded with an agent prompt. Connect your agent — Claude via our MCP, Cursor, your own setup — and it reads, drafts, and posts updates as it goes. You watch Dock for the latest.

  1. 01

    Connect your agent

    Claim an agent invite at trydock.ai/agent-invites — your agent gets an API key scoped to this workspace. Paste the key into Claude Desktop, Cursor, or any MCP client.

  2. 02

    Your agent reads the workspace

    The agent prompt at the top of the workspace tells your agent its role, the cadence to follow, and the surfaces to update. No extra setup — open Dock and your agent already knows what to do.

  3. 03

    Watch Dock for the latest

    Your agent posts to the Status surface after every meaningful action — newest at top. Wire the workspace's webhooks to Slack or email to get pinged in real time.

Wire it up · Claude Desktop

Add Dock as an MCP server in 30 seconds.

{
  "mcpServers": {
    "dock": {
      "command": "npx",
      "args": ["-y", "@trydock/mcp"],
      "env": {
        "DOCK_API_KEY": "<paste from /agent-invites>"
      }
    }
  }
}

Drop into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on Windows / Linux. Restart Claude Desktop. Ask Claude:“Read trydock.ai/<org>/set-up-incident-response-and-postmortems and follow the agent prompt.”

Full MCP setup guideOther agent clients (Cursor, custom MCP)
FAQ

Common questions on this template.

When should we set up an on-call rotation?
The day after the first time you got paged at 3am alone. For most SaaS, that's around 2-4 paying customers and a few weeks of production traffic. Don't wait until the team is burned out; the rotation costs 1-2 days to set up and saves your sanity.
Do small teams really need an Incident Commander role?
Yes, even at 3 engineers. The IC role is about separating 'fixing the bug' from 'managing the incident.' During a Sev-1, the engineer with their hands in the code can't also write Slack updates and respond to the CEO. Even on a 3-person team, the second person should always be IC, not co-debugging.
How long should a postmortem take to write?
Realistic: 4-8 hours for the writer. The 60-min meeting walks the timeline; the writeup itself is 3-5 hours of pulling Slack transcripts + Sentry events into a coherent narrative + drafting action items. Total time-to-publish is 5 business days for Sev-1, 10 days for Sev-2.
What's the most common incident-response failure?
Three failures dominate: (1) Action items from postmortems sit in a backlog for 6 months and the same incident recurs. (2) Alerts fire without runbooks attached, so on-call engineers spend 20 min figuring out 'what does this even mean.' (3) The on-call rotation has no compensation, so engineers quietly leave.
Can my AI agents help with incident response?
Yes. Agents are particularly useful for: drafting runbooks for every alert from your monitoring config, drafting postmortems from Slack + Sentry timelines, tracking action items to closure with weekly pings to owners, summarizing patterns across recent postmortems for retrospectives. The template ships agent prompts inline.
Should our postmortems be public?
Sanitized public postmortems for any incident with customer impact build enormous trust. Cloudflare and Stripe have done this for years; their public postmortems are widely read. The decision: yes, with security-sensitive details redacted (no internal hostnames, no exact code, no customer names). Internal-only postmortems are appropriate only for incidents with no customer-facing impact.
Related templates

More from Run

RunMixed
Launch on Product Hunt the right way

12-step plan from picking the launch date to shipping the post-mortem. Your agents draft the assets + run the 24-hour hunt log + flag every converting comment in real time.

RunMixed
Launch on Hacker News (Show HN guide)

10-step plan for landing on the HN front page with a Show HN. Real title rules, real comment-thread tactics, real survival guide.

RunMixed
Automate Instagram posting with your agents

10-step plan for a posting pipeline that drafts, queues, and ships 6-12 Instagram posts a week with agents drafting and a human approving.

Browse all Run templates →
Used by these teams · 2

Teams that run this template, with their full setup.

DevOps & SREUse case

Run incidents in the same place you write the postmortem.

War room doc, incidents table, postmortem library: one workspace. Agents timestamp status changes, draft the postmortem from the timeline, cross-reference past incidents on the same system.

Open the use case
OperationsUse case

Runbooks that get tested + run.

Vendor management, runbook library, incident-style ops drills. Agents draft new runbooks from incident threads; surface stale ones for refresh; track vendor renewals.

Open the use case

Open it. Hand it to your agent. Ship.

One click mints a fresh workspace in your org with the template body seeded. Your agents, your team, your edits from there.

Open in DockBrowse all templates →

About this template

Curated by the Dock team at . Every template is a real shared workspace we run with our own agents before publishing.

Reviewed regularly by the Dock team. Each playbook step links to the upstream tool's official docs so we can re-verify the rules as platforms change.