On-Call and Distributed Teams: Follow-the-Sun Done Right

Follow-the-sun is the gold standard for distributed teams. The conditions that make it work are concrete; the failure modes are predictable.

Why follow-the-sun

Follow-the-sun is the gold standard for distributed teams. Each region covers daytime; nobody is paged at 3am because nobody's daytime is the wrong daytime.

• Daytime coverage. Each region covers their own working hours; the on-call shift is the work day.
• Handoff discipline. Nights belong to the next region; the handoff is the contract.
• Sustainable. No human is paged outside daytime; the programme runs indefinitely without burnout.
• Hiring lever. Distributed teams compete on this; engineers in non-headquarters time zones get a fair on-call life.

Four conditions

• 1. Three regions geographically distributed.
• 2. 4-6 engineers per region.
• 3. Strong handoff doc + rotation system.
• 4. Aligned tooling across regions.

Common pitfalls

Most follow-the-sun rollouts fail in three predictable ways. Recognising the pitfalls upfront prevents the slow erosion that follows.

• Two-region setup. Coverage gaps; does not work for true 24-hour coverage; needs three regions.
• One global team without regional handoff. Everyone always on call; the team gets the cost of distribution without the benefit.
• Tool fragmentation. Each region uses their own tools; no cross-region visibility; handoffs become guesswork.
• Cultural drift. Each region develops its own response style; incidents that span regions get handled inconsistently.

Bridging artifact

The handoff doc is the institutional memory across regions. Without it, each shift restarts from zero; with it, momentum survives the timezone change.

• End-of-shift update. Handoff doc updated at the end of each region's shift; the next region inherits the state.
• Start-of-shift review. Reviewed at the start; the incoming shift knows what's open before any pages fire.
• Persistent format. Same template across regions; standardisation lets engineers parse it fast.
• Audit trail. Doc archives become the institutional memory; postmortems reference them as primary source.

Antipatterns

• Two regions only. Coverage gap.
• One global team without regional ownership. Always-on misery.
• Different tools per region. Fragmentation.

What to do this week

Three moves. (1) Apply this practice to your next on-call rotation. (2) Survey the team after one cycle. (3) Iterate based on feedback; the discipline is the cadence.