Skip to content
Back to handbooks
handbookEngineering Operations

Engineering Follow-the-Sun Handoffs Handbook

Follow-the-sun engineering only works when handoff timing, async expectations, and escalation windows are made explicit. This handbook turns that into a repeatable operating model.

Published April 7, 2026Updated September 8, 2026Reviewed September 8, 2026Reviewed by MaxReview current
Direct Answer

Treat every handoff as a transfer of context, not just a timestamp. The winning system defines the outgoing owner, the next seeing window, the escalation path, and the live-overlap exception rule.

The Core Rule

The handoff is incomplete until the receiving region can answer four questions without waking the previous owner:

  1. What changed?
  2. What still blocks progress?
  3. When will this be seen locally?
  4. What counts as an emergency escalation?

The Daily Sequence

Americas to Europe

  • Finalize the handoff before the Americas enter late afternoon.
  • Use the async handoff predictor to estimate the European pickup window.
  • Reserve live overlap for incident triage, release approval, or priority escalations.

Europe to Asia

  • Keep the written handoff short enough to scan in one pass.
  • Attach the decision log and the next hard deadline.
  • If the task is inside a DST transition week, include both UTC and local time.

Worked scenario: follow-the-sun handoff

For a San Francisco–London–Tokyo engineering lane, a fixed 16:00 UTC on Monday 12 January 2026 lands at 08:00 San Francisco, 16:00 London, and 01:00 Tokyo the next day. That is a handoff chain, not a reason to wake Tokyo for a routine call. Open the three-city planner state for escalation windows and use the async handoff predictor for the next seeing window. Keep the handoff artifact explicit about owner, blocker, next local pickup, and emergency threshold. The local labels use the site’s IANA-backed time methodology; the async predictor remains an estimate, not a delivery guarantee.

What To Put In Every Handoff

  • Current owner and next owner
  • Expected first-seen window
  • Severity level
  • Pending decisions
  • Exact deadline with timezone
  • Link to the canonical planning board

When To Break The Async Rule

Use a live meeting only when delay compounds risk:

  • release rollback
  • customer-facing outage
  • security incident
  • blocking dependency with no fallback
  • Save the operating cities as a team board.
  • Use the meeting planner for escalation windows.
  • Use the async handoff predictor for every non-urgent transfer.
  • Keep the Slack integration response short and link back to the planner state.