The Paging Volume Budget Per Engineer
Page volume per on-call shift is a leading indicator of burnout. The budget, the trend lines, and the conversation that prevents quitting.
The budget
The paging volume budget is 3 pages per shift on average. Above that, the rotation is unsustainable; sustained breach triggers an explicit burnout protocol rather than waiting for someone to resign.
- 3 pages per shift. Cap per shift. Anything higher means the on-call is being woken excessively and the rotation is degrading.
- Daytime exception. Business-hours flexibility lets higher page volume be sustainable when the engineer is awake anyway.
- Burnout protocol on sustained breach. 4+ shifts over budget triggers explicit intervention: alert tuning, staff-up, or feature freeze.
- Published budget per team. Visible cap and rationale. Honest conversations require the data to be public, not buried.
Trend lines
Per-engineer page count over 90 days surfaces the leading indicator of team health. Trends matter more than single shifts; the trajectory tells the real story.
- Per-engineer per-shift count. 90-day rolling average. Standard tracking on the engineering operating dashboard.
- Trends up. Alert-noise or system-degrading signal. Investigate before the rotation breaks down.
- Trends down. Team-winning signal. Celebrate; protect the gain from new alerts that creep in.
- Quarterly published trend. Visible per-team trajectory. Accountability requires the chart to live somewhere everyone can see.
The conversation
The monthly leadership conversation is the forcing function. SRE leadership reviews trends with each rotation; tracks causes; assigns action items with owners.
- Monthly review with rotation. Leadership and rotation in the same room each month. Drives mutual awareness of the trajectory.
- Surface causes. Trend-up triggers specific-alert and specific-service investigation. Concrete drivers, not generic “we are noisy.”
- Action items. Tune-noisy-alerts, staff-up, fix-flapping-system targets land in the action backlog with owners.
- Named owner per item. Each action item has a responsible engineer. Catches the “we discussed but did not act” pattern.