Skip to content

On-Call Handoff Summary

Example prompt: "At the end of each on-call rotation on Monday morning, pull all PagerDuty incidents from the past week, summarise what happened and what was resolved, and post a handoff note to #on-call on Slack and save it to Notion."

How to automate on-call handoff with GloriaMundo

The Problem

When an on-call rotation ends, the outgoing engineer needs to brief the incoming one on what happened during their shift. In practice, this handoff is often a hurried Slack message or a quick chat that misses important details — unresolved incidents, workarounds that were applied, or follow-up tasks that need attention. Poor handoffs lead to repeated triage of the same issues and knowledge that disappears when people go off rotation.

How GloriaMundo Solves It

We build a scheduled workflow that runs at the start of each new rotation. An integration step pulls all incidents from PagerDuty for the past week, including their status, severity, and resolution notes. An LLM step analyses the incident list and produces a structured handoff summary: what was resolved, what workarounds are in place, and what still needs attention. Integration steps post the summary to a dedicated Slack channel and save it as a page in Notion for the team's on-call archive. Glass Box preview lets the outgoing engineer review the summary and add any context the automation might have missed before it is shared.

Example Workflow Steps

  1. Trigger (scheduled): Runs Monday at 09:00, aligned with on-call rotation changeover.
  2. Step 1 (integration): Fetch all PagerDuty incidents from the past 7 days — status, severity, service affected, resolution notes, and acknowledging user.
  3. Step 2 (LLM): Analyse the incidents and produce a structured handoff summary: resolved incidents with root cause, active workarounds, outstanding items needing follow-up, and any patterns or recurring issues.
  4. Step 3 (integration): Post the handoff summary to #on-call on Slack.
  5. Step 4 (integration): Save the summary as a new page in the team's on-call archive in Notion, tagged with the rotation dates.

Integrations Used

  • PagerDuty — source of incident history, severity, and resolution details
  • Slack — delivers the handoff summary to the on-call channel
  • Notion — archives the summary for future reference and trend analysis

Who This Is For

SRE and infrastructure teams with regular on-call rotations who want consistent, thorough handoffs without relying on individual engineers to remember everything that happened during their shift.

Time & Cost Saved

Writing a proper handoff document manually takes 15-30 minutes at the end of a rotation, and it is often skipped under time pressure. This workflow produces a comprehensive summary automatically for a few credits per run. Over a quarter, the archived summaries also become valuable for identifying recurring issues and improving system reliability.