How to Make a Recurring Meeting Fair When Your Team Spans Every Time Zone

San Francisco, London, and Singapore can’t all be within business hours at the same time — the math doesn’t allow it. Any recurring meeting across that set requires at least one region to join outside their working day.

The worst outcome is leaving this unaddressed. The same people end up on the 7am or 9pm call every week, indefinitely, because nobody formalised anything different. A deliberate rotation where the inconvenience is shared and tracked is much fairer and more sustainable.

Before building a rotation: confirm the gap is real

Verify the actual windows using meetwhen. DST changes and new hires in different cities can open or close a window you weren’t aware of. If there’s a 30-minute overlap that works for everyone during business hours, a rotation isn’t needed.

If there’s genuinely no clean window: proceed.

The rotation model

A rotation moves the meeting time each week (or each cycle) so each region takes turns being the one outside standard hours.

Example: San Francisco, London, Singapore:

Three-week cycle; each region takes one off-hours call per cycle.

Implementation: Don’t just write “Week A / Week B / Week C” in the invite description and expect people to track it. Create separate recurring events for each slot — every 3 weeks — at their respective UTC times. Each participant accepts all three and sees the correct local time for each week.

Write the pattern down explicitly somewhere visible. “In rotation A, SF takes the off-hours slot. In rotation B, Singapore does. In rotation C, London does.” Verbal agreements about rotation schedules don’t survive team changes.

Allow swaps. Someone in SF with a conflict on their off-hours week should be able to swap with a colleague. Build a lightweight process for this rather than treating the rotation as rigid.

Size matters

If one region has 10 people and another has 2, the per-person burden is very different. Track individual off-hours frequency, not just regional frequency. A larger team should take more off-hours calls in aggregate but fewer per person.

Making off-hours calls optional

For all-hands or informal syncs, it’s reasonable to let off-hours participants skip and catch up via recording. If that’s the policy, say it clearly: “If your rotation week requires joining before 7am or after 9pm your time, attendance is optional — recording posted within 2 hours.”

An optional call that people feel implicitly pressured to join anyway is not actually optional.

Review the rotation every 6 months. Teams change, people move cities, DST shifts overlap windows. A rotation that worked for 3 cities may need restructuring when a fourth city joins.