How to run a fair rotating meeting across three or more timezones

Once a team spans three or more zones, a single fixed time almost always taxes the same person forever. Rotation fixes that — if you do it deliberately.

Two timezones usually leave you a shared window, even a narrow one. Three or more frequently do not: by the time the westernmost person is awake, the easternmost person is asleep. At that point a fixed weekly slot stops being a scheduling decision and becomes a standing tax on whoever lives furthest from the centre of gravity.

First, check whether you actually have no overlap

People assume there is no shared window more often than there really isn't. Widen the definition of 'available' before you give up on it: a 08:00 start or an 18:00 finish is a mild imposition, while a 02:00 call is a different category of ask. Set each person's real hours in the planner rather than assuming 9-to-5 everywhere, and see what survives.

If a genuine overlap exists, use it and stop here. Rotation is a cost — it makes the meeting harder to remember and harder to book rooms for. Only pay it when the alternative is worse.

Rotate on a fixed, published cycle

  1. Pick two or three candidate times, each of which is comfortable for a different subset of the team. Name them — 'Americas-friendly', 'APAC-friendly' — so people can reason about them without doing timezone maths.
  2. Assign them to a repeating cycle: week A, week B, week C, repeat. Put the cycle in the calendar invite description, not just in someone's head.
  3. Send the calendar invites in UTC or as real calendar events, never as text like '9am'. A text time in a chat message is the single most common source of missed cross-timezone meetings.
  4. Review the rotation once a quarter, or whenever someone joins or relocates. A rotation tuned for a team that no longer exists is worse than no rotation.

Make the unlucky slot cost less

Rotation spreads the pain but doesn't reduce it. Reduce it separately: keep the meeting short, publish an agenda far enough ahead that someone joining at 06:00 can skip the parts that don't concern them, and always record it. If a person's only reason to attend at a hostile hour is to hear a status update, that update should have been written down instead.

Give people a real exit

A rotation only reads as fair if opting out of a bad-for-you week is genuinely acceptable — attended by proxy, or covered by the recording plus a written summary. If skipping carries a cost, the rotation is theatre and the tax is still being collected, just less visibly.

Sanity-check the actual clock times

Before committing a rotation, run each candidate time through the planner with every participant's real city and hours. The ranking will tell you who absorbs the cost in each variant, which is exactly the thing you are trying to balance. A rotation that looks even on a whiteboard often isn't, because daylight saving moves two of the three zones and not the third.

Popular city pairs

Or see all cities and pairs.