Cross-Region Handoff

Follow the sun model.

Overview

Cross-region handoff runs on-call follow-the-sun across geographies so no single region carries 3am pages indefinitely. Sleep deprivation is the slowest-failing operational risk, and the only durable fix is a rotation where the active pager always sits in someone’s daylight hours. The handoff itself is what makes that work, the document, the overlap window, the localized runbook.

• Follow-the-sun model. Three regions covering eight-hour windows; daylight on-call replaces night pages with handoffs.
• Handoff document. Per-handoff written context: open incidents, watchlist items, scheduled changes, customer commitments. The next region reads it before taking the pager.
• Time-zone overlap. 30 to 60 minutes overlap between regions; live conversation during handoff catches anything the document missed.
• Per-region runbook plus documented policy. Region-localized runbooks for region-specific systems; per-team handoff policy committed for onboarding.

The approach

The practical approach is region-aligned rotations sized to local team headcount, mandatory overlap windows treated as paid work rather than optional, the handoff document templated and required before pager transfer, and per-region runbooks for anything that depends on region-local infrastructure. The whole pattern collapses if any one piece is treated as optional.

• Region alignment. Per-region rotation sized for local team; never assign a region a slot it cannot staff sustainably.
• Overlap window. 30 to 60 minutes paid overlap; the outgoing on-call walks through state with the incoming on-call live.
• Handoff document. Templated: open incidents, watchlist, scheduled changes, customer commitments. Required before pager transfer.
• Per-region runbook plus committed policy. Region-local infrastructure has region-local runbooks; the team handbook documents the handoff rule for onboarding.

Why this compounds

Cross-region handoff discipline compounds across years. Each rotation that respects sleep retains the operator who would otherwise leave; the team’s global on-call muscle grows; the handoff document evolves with each incident class the team handles.

• Operator retention. Sleep stays intact; the burnout-driven attrition that kills global on-call programs does not start.
• Continuity. Templated handoff document plus overlap window means context survives the pager transfer; nothing falls between regions.
• Operational hygiene. Per-region runbooks force the team to document regional differences explicitly rather than rely on tribal knowledge.
• Institutional knowledge. Each handoff teaches global-systems patterns; the team’s ability to run distributed on-call grows quarter over quarter.

Cross-region handoff is an operational discipline that pays off across years. Nova AI Ops integrates with on-call telemetry, surfaces patterns, and supports the team’s global on-call discipline.