On-Call Rotation Generator
Enter who's in the rotation, when shifts hand off, and how long they last. Get the full schedule and an .ics file your whole team can import. Nothing leaves your browser.
| # | On call | From | Until |
|---|
Rotation patterns that hold up
Weekly shifts with a weekday mid-morning handoff are the default for a reason. The outgoing engineer is around to brief the incoming one on anything still smoldering, and nobody inherits a pager at 23:59 on a Friday. If your alert volume makes a full week brutal, shorten the shift rather than adding a second simultaneous on-call; split responsibility means diluted responsibility.
Keep the rotation order stable and visible. Most on-call resentment comes not from the load itself but from surprises: a swap nobody recorded, a schedule that lives in someone's head. A shared calendar fixes more team friction than any process document.
The schedule is half the problem
A rotation only works if the person on shift actually receives the alert. Email alone fails at 03:00; phones sit on silent, inboxes sit unread. The fix is escalation: try the on-call engineer by email, then SMS, then an actual phone call, and if nothing gets acknowledged, move to the next person in the chain.
Related tools
- Cron Expression Tester: for the jobs that page the rotation.
- Error Budget Calculator: what the rotation is protecting.
Turn this schedule into actual alerting
failover.io's Team plan has built-in on-call scheduling: alerts route to whoever's on shift and escalate from email to SMS to voice call until acknowledged. Try the free plan first: 5 monitors, 2-step alert chains, no card.
Start monitoring free