International On-Call

Cross-border rotation.

Follow-the-sun benefits

International on-call uses global team distribution to eliminate overnight pages. Done right, every shift is a daytime shift somewhere; the cost is coordination, the gain is humane operations.

• 24/7 coverage without nights. Per-region daytime on-call; the engineer paged at 2pm in London is awake and warm, not bleary at 3am.
• Faster response for distributed customers. Per-region local on-call; users in any region hit a responder within their daytime.
• Reduced burnout. Per-engineer no 3am pages; the rotation preserves teams across years instead of burning them across quarters.
• Better retention. Sustainable rotation; engineers do not leave because of on-call; institutional knowledge accrues.

Requirements

Follow-the-sun requires real geographic spread. Three to four time zones is the minimum for full coverage; the cross-team coordination cost is the hard part, not the time-zone math.

• Engineers in 3-4 time zones. Asia, Europe, Americas at minimum; each region needs enough headcount for a real rotation.
• Cross-team coordination. Per-zone-transition handoff; tools must support cross-region shared state and incident handoff.
• Cultural and language considerations. Per-region response style differences; align practices explicitly; the unwritten rules vary.
• Runbook localisation. Per-region local-language runbooks where useful; the discipline supports response under pressure.

Handoff discipline

Handoffs are where international rotation breaks. Synchronous overlap at zone transitions, explicit incident transfer, shared documentation; without these, context evaporates at every shift change.

• Synchronous handoff. 15-30 min overlap at zone transitions; outgoing briefs incoming live; written notes alone are insufficient.
• Active incident transfer. Per-active-incident explicit IC transfer; the new IC takes the conn explicitly, not by silent assumption.
• Documentation in shared tools. Shared scrollback, shared incident doc; outgoing confirms acknowledgment from incoming.
• Handoff template. Per-team standardised template; the structure prevents the "everything was quiet" non-handoff.

Operating international on-call

Operating international on-call is its own discipline. Standardise tools across regions, respect regional holidays, review zone balance annually; the operational details determine whether the pattern survives growth.

• Standardise tools. Same Slack, PagerDuty, dashboards across regions; cross-region collaboration breaks if tooling diverges.
• Per-region holiday calendars. Public-holiday awareness; coverage adjusts so a regional holiday does not become a global gap.
• Annual review of zone coverage. Hiring patterns and regional growth shift the balance; the audit catches drift before pages start dropping.
• Per-region engineer support. Manager engagement in each region; remote on-call needs more support, not less.