On-Call Burnout Risk Scheduler
Calculate on-call rotation sustainability and burnout risk factors. Enter values for instant results with step-by-step formulas.
Worked Examples
Example 1: Healthy SRE Team
Problem:8 engineers, 7-day rotation, 3 incidents/week average, 1.5 hours resolution, 30% after-hours.
Solution:45 days on-call/year per person. ~2 incidents per shift. Low after-hours interruption. Burnout risk: 3.2/10 (Low).
Result:3.2/10 risk | Sustainable schedule | Good team size
Example 2: Understaffed Startup
Problem:3 engineers, 7-day rotation, 8 incidents/week, 2 hours resolution, 50% after-hours.
Solution:121 days on-call/year per person (33%!). ~8 incidents per shift with 4 after-hours. Burnout risk: 8.1/10 (High).
Result:8.1/10 risk | Unsustainable | Must grow team or reduce incidents
Example 3: High-Volume Platform
Problem:6 engineers, 7-day rotation, 15 incidents/week, 1 hour resolution, 40% after-hours.
Solution:60 days on-call/year. 15 incidents per shift is very high. Even with fast resolution, volume creates stress. Burnout risk: 6.5/10 (Medium).
Result:6.5/10 risk | Incident volume too high | Reliability investment needed
Frequently Asked Questions
What is on-call burnout?
On-call burnout is exhaustion from sustained incident response duties. Symptoms include fatigue, decreased performance, cynicism about work, and eventually turnover. It's caused by sleep interruption, unpredictability, and chronic stress.
How many engineers for sustainable on-call?
Minimum 4-5 for basic coverage. 6-8 is healthier. Fewer means each person is on-call too often. The SRE rule of thumb: no one should be on-call more than 25% of the time (one week per month).
How do after-hours incidents affect burnout?
After-hours pages are 2-3x more impactful on burnout than daytime. They interrupt sleep, disrupt family time, and prevent true rest. Reducing after-hours incidents should be a priority—often through better architecture and automation.
How do I reduce on-call burden?
Options: grow the team, improve reliability (fewer incidents), automate responses, shift incidents to business hours through architecture, implement follow-the-sun (global team), and ensure adequate compensation.