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 Engineering Manager
Daily, weekly and custom hand-offs, primary and secondary layers, stacking overrides, coverage requests from Slack and the web, shift reminders and personal calendar subscriptions are all documented, and unstaffed gaps are flagged in advance at nine in the morning in the schedule's own time zone — most of what our works council asked for. I found no public information on on-call hours exported per person for payroll or standby pay, on fairness or fatigue reporting that would warn when someone carries several nights in a row, or on an explicitly described follow-the-sun pattern across responder time zones. 17 18 20 2 7