Weekly digest
Pick the categories you care about: movies, AI launches, sports, eclipses, and major public dates. One email per week, and never anything you did not ask for.
Want full preferences? Customize your digest →
Distributed teams
Visualize 24-hour coverage across distributed teams.
Input distributed team zones → see 24hr coverage ribbon with gaps highlighted. Shareable to Slack.
Regions needed
3
For clean 24h coverage
Overlap window
15–30m
Per handoff, documented
Baton pass
Ticket → Owner
Not memory or chat
Operations
Follow-the-sun works best when each region has a clear ownership window, a repeatable handoff note, and a small amount of overlap reserved for escalation. The visual on this page is useful because it shows whether your chosen cities create a clean relay or a messy patchwork with too many dark gaps.
A common three-region stack is North America, Europe or the Gulf, and Asia-Pacific. That usually creates enough continuity for support and engineering work without forcing every team to live in night shifts. The page is meant to make that handoff shape visible, not just to decorate the idea of global coverage.
If you are planning incident response, customer support, or a global operations desk, use this page alongside compare pages and the meeting planner. The compare pages tell you what two specific cities feel like together, while follow-the-sun tells you whether the whole regional chain is actually sustainable.
Failure modes
The model fails when teams rely on meetings instead of documented handoffs. If the outgoing region leaves work in chat threads, memory, or personal inboxes, the next region loses time just reconstructing context. That means the apparent 24-hour coverage is not actually productive coverage.
It also fails when the chosen regions do not have enough overlap to transfer urgent work safely. A page like this should make that obvious by showing whether the sun-shaped coverage still contains a practical baton-pass window between regions.
Questions
The follow-the-sun model
Worked example
Three hubs each work a standard 09:00–17:00 local day. Converted to UTC, the windows form a near-continuous relay around the clock. Each region picks up live work where the previous one left off, with an overlap at each handoff.
| Region | Hub | Local shift | In UTC | Receives the baton from |
|---|---|---|---|---|
| Asia-Pacific | Singapore (UTC+8) | 09:00 – 17:00 | 01:00 – 09:00 UTC | Americas, at the start of its day |
| Europe / Middle East | London (UTC+0) | 09:00 – 17:00 | 09:00 – 17:00 UTC | Asia-Pacific, overlapping its final hour |
| Americas | New York (UTC-5) | 09:00 – 17:00 | 14:00 – 22:00 UTC | Europe, overlapping its final three hours |
Read the UTC column as a relay: Asia-Pacific runs 01:00–09:00 UTC, Europe 09:00–17:00 UTC, and the Americas 14:00–22:00 UTC. The Europe-to-Americas handoff has a three-hour overlap (14:00–17:00 UTC); the Americas-to-Asia-Pacific handoff is the tight one — Americas ends at 22:00 UTC and Asia-Pacific starts at 01:00 UTC, a three-hour gap that a real rotation closes by shifting one team's hours or adding a short on-call window.
Reference fields include the follow-the-sun operating model, 24-hour coverage, the overlap window and its math, three-region rotations across Asia-Pacific, Europe, and the Americas, written handoffs, and the baton-pass concept.
