After-Hours Pages Policy

Reduce after-hours volume.

Overview

After-hours page policy explicitly defines which alerts can wake the on-call and which hold until business hours. Without the policy, every alert is an interrupt and every shift carries the risk of unnecessary 3am wakes. With the policy, P0 (true emergencies) wake the pager, P1 emails the team, and the rest queue for daylight. The discipline is in the explicit routing rules, not in vague guidelines.

• Reduce after-hours volume. Per-alert the after-hours severity decided in advance; not invented by the on-call at 2am.
• Severity tiers. P0 wakes immediately; P1 emails for morning review; P2 and below wait for daylight unless they escalate.
• Quiet hours. Per-team the explicit night-time window where only P0 alerts page; matches operator sleep windows.
• Per-alert routing plus committed policy. Per-alert routing decision documented in the alert config; per-team after-hours policy committed to the team handbook.

The approach

The practical approach is to define severity tiers explicitly and route per-tier (P0 pages, P1 emails, P2+ queues), set quiet hours per team that match the rotation reality, route per-alert based on documented severity decisions made at design time, run weekly review of after-hours volume to catch drift, and document the policy in the team handbook so the routing rules are predictable for onboarding.

• Severity tiers. P0 wakes; P1 emails for morning; P2 queues for daylight; rules are explicit, not invented at 2am.
• Quiet hours. Per-team explicit night window where only P0 alerts page; matches the rotation’s actual sleep distribution.
• Per-alert routing. Per-alert severity decision made at design time and committed to the alert config.
• Per-week review plus documented policy. Per-week after-hours volume review catches drift; per-team after-hours policy committed to the handbook.

Why this compounds

After-hours policy discipline compounds across quarters. Each tuned alert preserves operator sleep; each preserved night reduces burnout risk; the rotation becomes sustainable rather than punishing. After a year, the on-call rotation can be carried by the same team that started it; without the policy, attrition forces continuous re-staffing.

• Operator sleep. Right policy preserves rest; the rotation does not become an attrition driver.
• Business risk. P0 still wakes the pager; the right severity tier matches the actual business impact.
• Operator experience. Fewer false wakes; engineers trust the pager only fires when it matters.
• Institutional knowledge. Each tuning teaches alert design; the team learns which alerts deserve a 3am wake and which do not.

After-hours policy discipline is an operational discipline that pays off across years. Nova AI Ops integrates with on-call telemetry, surfaces after-hours patterns, and supports the team’s on-call discipline.