On-call schedules, rotations & escalation
How this is scored
Who is on call and what happens when nobody answers: schedules with daily, weekly and custom rotations, layers and follow-the-sun hand-offs across time zones, overrides, swaps and holiday cover, escalation policies with timeouts, repeat and fallback levels, round-robin and team escalation, calendar export and sync, reminders before a shift, on-call reports and hours exported for on-call pay and working-time rules, and a mobile app that shows the shift and lets a responder hand it over.
0 — No schedules or escalation of any kind; alerts go to a fixed list of people.
3 — A simple weekly rotation and one escalation step; overrides, layers, time zones and on-call reports are basic or not described.
5 — Schedules with several rotation types and layers, overrides and swaps from the app, escalation policies with timeouts and several levels, time-zone handling, calendar export, shift reminders, and a report of who was on call when.
8 — Follow-the-sun and multi-team schedules, round-robin and conditional escalation, coverage gaps flagged before they happen, schedules and policies managed as code or by API, and on-call hours exported per person for pay and working-time rules, all documented.
10 — Scheduling a large organisation runs on: every feature above with fairness and fatigue reports, rest-period rules enforced or warned, schedules imported from HR or workforce tools, and every scheduling limit documented per plan.
The SRE Lead
Schedules with user overrides, escalation policies that page level by level until somebody acknowledges and record each run, repeat cycles with auto-resolve, and severity- or time-based rules are documented, along with unlimited policies per team and service, readiness lists showing who can actually be paged, calendar feeds, and on-call managed as code through the API, CLI and Terraform. We found no public information on rotation types and layers, follow-the-sun hand-offs across time zones, shift reminders, or on-call hours exported for pay and working-time rules. Good bones for eight teams, but the time-zone and reporting depth I need before trusting it with sixty engineers is not described. 6 7 8 9