On-Call Coverage Roster & Fatigue Risk Planner
Plan sustainable on-call rotations, calculate fatigue risk, and optimize team coverage to prevent burnout.
Worked Examples
Example 1: SRE Team On-Call Planning
Problem: 6-person SRE team, 1-week rotations, 3 incidents/week averaging 2 hours each. Weekend coverage required. Assess fatigue risk and optimize.
Solution: Current Setup:\n- Team: 6 engineers\n- Rotation: 1 week (7 days)\n- Shifts per person/year: 52 / 6 = 8.7 weeks\n- Incidents per shift: 3/week\n- Hours per shift: 3 × 2 = 6 hours\n- Avg hours/day: 6 / 7 = 0.86 hours\n\nFatigue Analysis:\n- Frequency: 8.7 weeks/year (moderate; target <6)\n- Duration: 7 days (acceptable)\n- Load: 0.86 hours/day (low-moderate)\n- Weekend: Yes (+stress)\n- Fatigue Score: ~45 (Moderate risk)\n\nProblems:\n1. Frequency slightly high (8.7 vs target 6)\n2. Weekend coverage adds stress\n3. No backup mentioned (single point of failure)\n\nOptimization Options:\n\nOption 1: Grow Team\n- Add 2 engineers → 8 total\n- Shifts per person: 52 / 8 = 6.5 weeks/year ✓\n- Cost: $200K/year (2 × $100K)\n- Fatigue: Moderate → Low\n\nOption 2: Follow-the-Sun (if global team)\n- Spl
Result: 8.7 weeks/year per engineer (target <6) | Moderate fatigue risk | Add secondary rotation + reduce incidents
Frequently Asked Questions
What is on-call rotation?
On-call rotation is scheduled availability to respond to production incidents outside business hours. Engineers take turns being 'on-call'—carrying pager/phone, expected to respond within SLA (typically 15-30 min). Rotations are typically 1 week (168 hours). After rotation, next engineer takes over. On-call is necessary for 24/7 services but creates stress and disrupts personal time.
How many people do I need for sustainable on-call?
Minimum 4 for weekly rotations (each on-call 13 weeks/year). Healthy: 6-8 (6-9 weeks/year each). Excellent: 10+ (5 weeks/year each). Formula: Team size = 52 weeks / (target weeks per person × rotation length). Target <6 weeks/year per person to prevent burnout. Smaller teams (<4) experience unsustainable load; burnout and attrition result.
What is on-call fatigue and how do I prevent it?
On-call fatigue is burnout from sustained availability stress, sleep disruption, and unpredictability. Symptoms: anxiety, poor sleep, resentment, degraded incident response quality. Prevention: (1) Limit frequency (<6 weeks/year), (2) Short rotations (1 week, not 4), (3) Backup person (coverage for breaks), (4) Incident reduction (automation, better monitoring), (5) Compensation (time off, pay), (6) Handoff discipline (clear docs). Fatigue compounds—monitor team health.
Should on-call rotations be 1 week or 2+ weeks?
Shorter is generally better. 1-week rotations: Pro—shorter burden, frequent breaks. Con—more handoffs. 2-week rotations: Pro—fewer handoffs, deeper context. Con—sustained stress. Research shows 1-week preferred—ability to 'see the end' reduces stress. Exception: Low-incident services (<1/week) can do 2-week rotations. High-incident (>5/week) should do daily or follow-the-sun rotation.
What is follow-the-sun on-call?
Follow-the-sun distributes on-call across time zones: Asia team covers Asia hours, Europe covers Europe, US covers US. No one is on-call overnight. Requires global team (3+ regions). Benefits: Healthier work-life balance, faster response during business hours. Challenges: Handoff complexity, timezone communication, requires enough staff per region. Best for: Large teams (20+), global customers, high incident volume.
Should I pay for on-call time?
Yes. Options: (1) Stipend ($500-1,500/week), (2) Hourly rate for actual incidents, (3) Time-off comp (1 day off per week on-call), (4) Hybrid (stipend + incident pay). Paying signals respect and compensates for lifestyle disruption. Unpaid on-call = resentment and attrition, especially if frequent incidents. Check local labor laws—some jurisdictions require compensation.