How to run an on-call handoff for a remote team
An on-call handoff is the moment one person stops carrying the pager and the next person starts. On a remote team it often happens in a DM, a quick call, or not at all, and the incoming person learns about the flaky alert when it fires at 2am.
Run it in writing, in the channel, with a short voice check beside it. The outgoing person posts what happened, what is still open, and what to watch. The incoming person reads it, asks in the room, and takes ownership out loud.
The usual way
A remote on-call handoff often looks like this.
- The DM handoff. "Anything I should know?" "Nah, quiet week." The two people who said it are the only ones who saw it.
- The missing context. An alert was silenced on Tuesday with a good reason. Nobody wrote the reason down.
- The orphaned item. A fix was half done when the shift ended. It belongs to whoever notices it next.
- The calendar sync. A recurring handoff call lands at a bad hour for one side of the rotation, so it gets skipped.
A format for a distributed team
1. Post the handoff in the on-call channel
At the end of the shift, the outgoing person posts one message in the team's on-call channel. Same shape every week.
- Incidents: One, Wednesday, checkout errors after a config change. Rolled back. Postmortem thread linked.
- Still open: Disk alert on the reporting database. Silenced until Friday while the cleanup job runs.
- Watch for: The certificate renewal job runs Sunday night. It failed last month.
- Changed this week: New runbook step for restarting the queue workers.
Four headings keep it short. A post in the channel is a post the next shift, the one after that, and the team lead can all read.
2. Give every open item one owner
Each line under "Still open" gets a name. Usually it is the incoming person, sometimes it stays with the person who started the fix. Write it in the post.
- Owner named. "Disk alert: Sam owns the cleanup, Priya is on call if it pages."
- End date named. A silence with no end date is an alert nobody will turn back on.
- Link to the thread. The history of the item sits where the work happened.
3. Do the live check in an open voice room
Some handoffs need a few minutes of talking: a tricky item, a judgement call, a question the post raised. Skip the recurring invite. Use a walk-in voice room beside the on-call channel.
The outgoing person sits in the room for a short window at the end of the shift. The incoming person walks in, asks what the post does not answer, and leaves. Whoever else has context can walk in too. If the post answered everything, nobody needs to come.
4. Accept the pager in writing
The incoming person replies in the handoff thread: "I have it." That one line is the record of when the shift changed hands, and it tells the rest of the team who to page.
5. Feed the next handoff
During the shift, the on-call person replies in the handoff thread as things happen. By the end of the week, most of the next handoff post is already written.
Make it repeatable
- Pin the format. The next handoff starts from the last one's headings.
- Link the incidents. For anything that paged, link the war room thread. How to run an incident war room for a remote team covers that part.
- Turn repeats into postmortems. An alert that shows up in two handoffs in a row deserves its own review. See How to run a remote postmortem.
- Keep it out of DMs. When DMs hide the decision covers why.
How Bullpen fits
Bullpen is team chat with walk-in voice rooms and AI helpers on the roster. An on-call handoff can live in one thread in one channel, from the outgoing post to "I have it".
The handoff lives in the channel. Every week's post sits in the same place, so the history of the rotation is one scroll.
The live check happens in the channel's walk-in voice room. It stays open beside the channel. People walk in for the handoff and leave when it is done.
Wren writes the notes. Wren is an AI helper. In that walk-in voice room, Wren posts notes and action items back to the channel the room belongs to, so what was agreed out loud lands in the handoff thread.
Scout finds why the alert was silenced. Scout is an AI helper on the same roster. Mention Scout and ask why the disk alert was silenced last week. Scout answers from what was said and links the message it came from.
Nix keeps the end dates honest. When a silence or a fix has a date, mention Nix in the thread and the reminder arrives in the channel on the day. How to keep track of follow-ups in team chat covers the details.
Try it on your next shift change
At the end of your next on-call shift, post the four headings in the on-call channel and ask the next person to reply "I have it."