Use Case

Building fair support rotations across time zones.

Follow-the-sun coverage sounds simple until you realize someone always gets the 2 AM handoff. Here's how to make rotations genuinely fair.

Updated November 9, 2026 · Reviewed by The Vibing Dev.

The follow-the-sun model

A standard 3-region support rotation splits the day into three shifts:

• APAC (SGT/JST/AEST): 9 AM – 6 PM local
• Europe (GMT/CET): 9 AM – 6 PM local
• US (ET/CT/PT): 9 AM – 6 PM local

The handoff happens at the boundary between regions. When APAC's day ends at 6 PM SGT, it's 12 PM GMT (Europe's midday) and 7 AM ET (US morning). That handoff window is where problems hide.

The handoff gap problem

If APAC logs off at 6 PM SGT and Europe doesn't start until 9 AM GMT, there's a 3-hour coverage gap (6 PM – 9 PM SGT = 10 AM – 1 PM GMT). Incidents during this window fall through the cracks. The planner reveals these gaps instantly:

1. Add your three hub cities (e.g., Singapore, London, New York)
2. Set each to 9–5 working hours
3. The golden window shows overlap — but the absence of overlap between regions shows the gap
4. Adjust handoff times to close the gap: shift APAC to 10 AM – 7 PM, or Europe to 8 AM – 5 PM

Strategy 1: Overlap the handoffs

Instead of clean breaks, build 30–60 minute overlaps between shifts. The outgoing team briefs the incoming team while both are online. Use the planner to find the overlap:

• Set APAC to 8 AM – 5 PM SGT
• Set Europe to 8 AM – 5 PM GMT (which is 4 PM – 1 AM SGT)
• The overlap at 4–5 PM SGT / 8–9 AM GMT is the handoff window
• Repeat for Europe → US handoff

Strategy 2: Rotate the inconvenient slot

Some handoffs will always land at an awkward hour for someone. Fairness means rotating who takes the hit:

• Week 1: US takes the early handoff (7 AM ET catch-up with Europe)
• Week 2: Europe takes the late handoff (7 PM GMT catch-up with APAC)
• Week 3: APAC takes the overnight handoff (10 PM SGT catch-up with US)

Track who's on the hook each week in a shared doc. The planner's In hours / Early / Late / Outside ratings make it obvious when someone is being asked to meet outside reasonable hours.

Strategy 3: Use the meeting cost calculator to quantify burden

If your support team also has sync meetings (daily standup, weekly retrospective), the Meeting Cost Calculator can flag timezone burden. Add each team member, set their rates, and the calculator will show who's consistently meeting Outside hours — the "timezone tax" that's invisible in a calendar view.

Visualizing coverage gaps

The planner's timeline view makes coverage gaps obvious. When you see blank space between two regions' work hours, that's an uncovered window. Strategies to fill it:

• Stagger shifts: Not everyone works 9–5. Some team members cover 7 AM – 4 PM, others 11 AM – 8 PM.
• On-call bridge: One person from the outgoing region stays on-call for 2 hours after their shift ends.
• Async escalation: Non-critical issues wait for the next region. Critical issues page the on-call.

How to set this up in the planner

1. Open World Clock Meeting Planner in International mode
2. Add your hub cities (e.g., Singapore, London, New York)
3. Set each team's working hours — don't assume 9–5 for everyone
4. Check the golden window: if it exists, you have overlap for handoffs
5. Check the gaps: empty space between regions = uncovered hours
6. Use Export → Slack summary to share the rotation schedule
7. Bookmark the shareable link so team leads can reference it

Common mistakes

• Ignoring DST: A handoff at "6 PM SGT / 10 AM GMT" in October shifts when Europe falls back. Use the planner with a future date to verify.
• Assuming symmetry: US → Europe handoff is not the mirror of Europe → US. The planner shows the real offset for each direction.
• Not naming rows: Click "Add participant name" to label each row with the team name (e.g., "APAC Support", "EU Support"). Makes exports unambiguous.