Page 1 of 1

How your team runs its on-call rota

About 10 minutes. Please describe real events, not opinions. Short answers are fine, and "never happened" is a useful answer too.

I'm researching this problem to decide whether to build a product. Nothing is for sale here. I'm Hieu Tran; I use AI tools to help with this research, including drafting messages and organising responses. Answers are kept private and only shared in anonymised form.

Think of the last time your on-call rota caused trouble: someone on call too often, a holiday clash, a missed page, a swap that went wrong. What happened?

What did it cost: a missed incident, burnout, an argument, hours rebuilding the schedule?

How is the rota built today? Who does it, with what tool or spreadsheet, and how long does it take each cycle?

What do you pay for paging and scheduling (PagerDuty, Opsgenie, incident.io, Rootly, Grafana OnCall…)? With Opsgenie being retired, what have you decided?

Your role

Company website

Engineers on the rota

A
B
C
D

Email for one or two short follow-up questions (optional)