Skip to content
compiler.dev

On-call rotation generator

List your engineers, pick a time zone, hand-off time and shift length, and get a fair round-robin rotation as a table, plus an .ics file you can import into Google Calendar, Outlook or Apple Calendar.

YYYY-MM-DD

#On callStartsEnds
1AdaMon, 2 Nov 2026, 10:00Mon, 9 Nov 2026, 10:00
2GraceMon, 9 Nov 2026, 10:00Mon, 16 Nov 2026, 10:00
3LinusMon, 16 Nov 2026, 10:00Mon, 23 Nov 2026, 10:00
4MargaretMon, 23 Nov 2026, 10:00Mon, 30 Nov 2026, 10:00
5DennisMon, 30 Nov 2026, 10:00Mon, 7 Dec 2026, 10:00
6AdaMon, 7 Dec 2026, 10:00Mon, 14 Dec 2026, 10:00
7GraceMon, 14 Dec 2026, 10:00Mon, 21 Dec 2026, 10:00
8LinusMon, 21 Dec 2026, 10:00Mon, 28 Dec 2026, 10:00
9MargaretMon, 28 Dec 2026, 10:00Mon, 4 Jan 2027, 10:00
10DennisMon, 4 Jan 2027, 10:00Mon, 11 Jan 2027, 10:00

Download .ics calendar

Times shown in Europe/London. Each person is on call every 5 shifts.

Everything runs in your browser; nothing you type is sent anywhere.

How to use it

  1. Enter one person per line, in the order they should rotate.
  2. Choose the start date, the hand-off hour in your time zone, the shift length and the number of shifts.
  3. Review the table, then download the ICS file and import it into your team calendar.

Frequently asked questions

How long should an on-call shift be?

One week is the most common. Shorter shifts mean more hand-offs but less fatigue; longer shifts mean fewer hand-offs but heavier load. Teams with frequent pages often use 3 to 4 days.

How do I choose the hand-off time?

Hand off during working hours when both people are online, such as 10:00 local, rather than at midnight.

Does it handle daylight saving?

Yes. Hand-offs stay at the same local time in the zone you choose, and the ICS file stores the exact UTC instant of each shift.

How big should the rotation be?

At least four to six engineers, so each person is on call no more than about one week in four to six.

Made by compiler.dev, faster GitHub Actions runners. More free tools.