Free for 30 days on Scale.Start free
Run6 stepsOngoing, ~30 min/week + 2 hr at month end

On-call rotation, monthly cycle

A monthly-cycling on-call rotation where the schedule rolls forward without manual cron, every page has a runbook (or a queued ticket to write one), Friday handoffs are a doc not a vibe, and month-end produces an honest list of what to improve.

Open in DockSee every step →

A monthly-cycling on-call rotation where the schedule rolls forward without manual cron

A monthly-cycling on-call rotation where the schedule rolls forward without manual cron, every page has a runbook (or a queued ticket to write one), Friday handoffs are a doc not a vibe, and month-end produces an honest list of what to improve.

Spin up an agent for the heavy lifting

Your scheduler agent (yours) rolls the schedule forward each Friday, sends the next-week reminder, and nudges anyone who hasn't confirmed.

6 steps, 0 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.

6Surfaces
6Steps
3Agent prompts
3Tools mapped
Surfaces
  • tableSchedule
  • tablePages
  • docHandoff log
  • tableRunbook index
  • docMonth retro
  • 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>/on-call-rotation and follow the agent prompt.”

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

Common questions on this template.

Do I need to replace PagerDuty?
No. PagerDuty (or Opsgenie / Incident.io) pages people; this workspace operates the cycle around the schedule. Schedule mirrors PagerDuty so your agent can analyze it, but PagerDuty stays the source of truth for who's actually on-call right now. Two systems, one job each.
What if our team rotates daily instead of weekly?
Add a `shift_type` column to Schedule and switch the Friday handoff cadence to daily. The agentPrompt's 'Every Friday at 3 PM' becomes 'Every shift end'. The retro horizon (monthly) stays the same because monthly is the right unit for pattern-finding regardless of shift length.
Our team is too small for a rotation, is this useful?
Below 3 engineers, probably not. With 3-4 engineers, the rotation is light but the runbook tracking + handoff log is the value (because the institutional memory across rotations is fragile). Above 8 engineers, the schedule itself becomes the value because manual schedule management starts breaking.
Can the agent auto-resolve pages?
No, by design. The on-call always closes the loop themselves; the agent only fills in derived data (MTTA, MTTR) and flags missing runbooks. Auto-resolution is how on-call ops teams accidentally hide their fire — when you forget what broke, the next break feels surprising. The agent's job is to surface, not to suppress.
What does the agent do if no one confirms next week's schedule?
Monday morning, the agent posts a 1-line escalation to the on-call lead: '$person is primary next week but hasn't confirmed since Friday's nudge'. Lead decides: chase, swap, or accept the silence. The agent never auto-reassigns; reassignment without consent is how people stop trusting the rotation.
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 →

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.