On-Call Rotation Generator

Weekly rotations are the most common and generally recommended for teams of 4+ engineers. They provide enough time for the on-call engineer to build context while limiting burnout. Biweekly rotations work for smaller teams (2-3 people) where weekly would mean too frequent rotation. Avoid rotations shorter than 5 days — context switching overhead outweighs any benefit.

A healthy on-call rotation needs at least 4-6 engineers to avoid burnout. With 4 people on weekly rotations, each person is on-call roughly once a month. Fewer than 4 means too-frequent duty; more than 8 means engineers lose familiarity with the rotation cadence. For critical services, consider a primary + secondary (shadow) rotation.

Yes, fairness is critical to preventing burnout and resentment. Ensure rotations cycle through team members evenly, including weekends. If some periods are inherently more stressful (e.g., after major releases), consider compensation or lighter duty periods. Track on-call hours and incidents per person over time to identify imbalances.

A shadow (secondary) rotation pairs a less experienced engineer with the primary on-call to provide learning opportunities without full responsibility. The shadow observes pages, joins incident calls, and can help with resolution. After 2-3 shadow rotations, engineers graduate to primary. This is excellent for onboarding new team members into SRE responsibilities.

Build a swap process into your on-call policy: any engineer can swap their on-call week with another willing team member, with manager approval. Maintain a shared calendar for blackout dates. For holidays, consider offering compensatory time off equal to the holiday hours. Some teams create an explicit holiday rotation separate from the regular one.