What makes an on-call rotation fair?

Fairness comes from equal distribution of shifts, predictable timing so people can plan their lives, and no single person carrying every weekend or holiday. A round-robin over a fixed shift length, like this tool produces, gives everyone the same number of turns in the same order.

How long should an on-call shift be?

Weekly shifts are the most common because they amortise the cost of context-switching and let the responder settle in. Some teams use shorter shifts to reduce burnout or longer ones for very quiet services. Pick the length that balances fatigue against handover overhead.

What is an escalation path?

An escalation path is the ordered list of who gets paged if the primary on-call does not acknowledge an alert within a set time. It usually goes primary, then secondary, then team lead or manager, ensuring an incident never goes unanswered because one person is asleep or unreachable.

Why define incident severities?

Severity levels tell responders how urgently to act and who to involve. A SEV1 total outage warrants waking people up; a SEV3 minor bug can wait for business hours. Clear definitions prevent both under-reaction to real outages and alert fatigue from paging on trivial issues.

Is my team list sent anywhere?

No. The rotation is generated entirely in your browser from the names and settings you enter. Nothing is uploaded, so you can plan internal schedules privately.

On-Call Rotation Schedule Builder

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

The On-Call Rotation Schedule Builder turns a list of engineers into a fair, predictable on-call schedule plus the supporting policy a real rotation needs. Ad-hoc on-call assignment breeds resentment and gaps; a clean round-robin with a documented escalation path and severity definitions keeps incidents covered and the team sane.

How it works

The builder assigns shifts by round-robin: starting from your chosen date, each shift of N days goes to the next person in the list, wrapping back to the first when the list is exhausted. Because every member appears in the same order at the same interval, the load is distributed equally and the schedule is predictable weeks ahead. Alongside the table, the tool emits an escalation path (primary → secondary → lead), a handover checklist for the start of each shift, incident severity definitions (SEV1–SEV3), and a contact list — the four things a responder needs the moment an alert fires.

Tips and example

Publish the schedule far ahead. People need to plan around on-call; a rotation only known a day out is not fair even if the maths is.
Always have a secondary. A single primary is one missed page away from an unhandled incident; the escalation path exists for exactly that case.
Tune severities to reduce fatigue. If everything pages as SEV1, nothing is urgent. Reserve waking people up for real customer impact.

Example: a 4-person team on weekly (7-day) shifts starting Monday means each engineer is primary one week in four, in a fixed, repeating order, with the next person in the list as secondary.