How to Run a Fair Meeting Rotation Across Time Zones
Your team lead in Berlin has taken the 9 PM call with Seattle every week for four months. Nobody decided that on purpose. It happened once, it worked, and it quietly became permanent, because nobody wrote down whose turn it was next.
That's the usual failure behind an "unfair meeting time" complaint on a distributed team. It's rarely a bad decision. It's the absence of a system, which lets the same person keep absorbing the bad slot by default.
The Problem Is the Silent Default
If a team spans more than about 8 hours, at least one recurring meeting is inconvenient for somebody. That's arithmetic, not a scheduling failure.
The failure comes after that. Whoever complains least keeps the bad slot, and whoever pushes back gets moved to a better one. Over a few months that becomes a two-tier team, without anyone choosing it. The person who took the early slot "just this once" has no natural moment to renegotiate, because renegotiating now sounds like complaining about something that has always been this way.
What a Real Rotation Looks Like
Take a team in Seattle, London and Singapore, and a weekly meeting. In January there is no hour that suits all three. This is what each possible start looks like, with the best three options for a Tuesday (times in each city's local clock, calculated from the time zone database):
| Option | Seattle | London | Singapore |
|---|---|---|---|
| A: 13:00 UTC | 5:00 AM | 1:00 PM | 9:00 PM |
| B: 21:00 UTC | 1:00 PM | 9:00 PM | 5:00 AM Wed |
| C: 05:00 UTC | 9:00 PM Mon | 5:00 AM | 1:00 PM |
"Mon" and "Wed" mean the day before and after Tuesday. Each option puts one city in a good afternoon slot, one three hours early, and one three hours late. Counting a good slot as 8 AM to 6 PM, that's the best the clock allows. It also happens to be a ready-made rotation, because every city gets the easy slot once in three weeks. Run A, B, C, then A again, and nobody is stuck.
In July the numbers move by an hour for Seattle and London and not for Singapore, so recompute the table when the clocks change. Write the options down as UTC times and let each person convert, or use the time zone converter with the date set.
The Rule and the Record
Two things make a rotation work, and neither needs software.
The rule: no recurring meeting sits permanently outside 8 AM to 6 PM local time for the same person. If it has to fall outside that window, the person or region that takes the bad slot changes on a fixed schedule, weekly or every second week, not "whenever someone complains."
The record: one place, in the meeting invite or a shared sheet, that says this week's owner and next week's. A log with three columns is enough:
| Week | Slot | Who takes the awkward hour |
|---|---|---|
| 1 | Option A | Seattle (early) and Singapore (late) |
| 2 | Option B | London (late) and Singapore (early) |
| 3 | Option C | Seattle (late) and London (early) |
The value isn't the spreadsheet. It's that "next in rotation" becomes a visible fact instead of a decision someone has to argue again every week. Fairness disputes mostly come from rules that are implicit, and they mostly stop once the rule is written where everyone can see it.
Where Rotation Is the Wrong Tool
Rotation fixes who pays for a meeting that has to happen live. It doesn't fix a meeting that doesn't need to be live. If a team holds three or four real-time calls a week across a 10-hour gap, rotating the pain is treating a symptom.
A useful test before you schedule any recurring cross-time-zone call: could this be a shared document with comments? If yes, that's a better fix than a perfectly fair rotation of an unnecessary meeting. Keep live time for decisions that gain from back and forth.
Two cases need a different answer:
- A person who must always run the meeting. Rotate the slot for the other participants, or split it into two shorter regional sessions so one group isn't always the awkward one.
- Only two regions. It's simpler: alternate which side takes the early or late slot each week. For a San Francisco and Mumbai team (12.5 hours apart in summer, 13.5 in winter) there is no comfortable hour at all, so alternating is the only fair arrangement.
What to Do Next
Pick the one recurring meeting that currently has a fixed bad slot, the one where the same person or region always takes the inconvenient hour. Write the rule into the invite description, and set week 1's owner today. Use the meeting scheduler to see what a proposed time means in up to three locations and who ends up outside a 9 to 5 day, then put the same times in the log.
Related Articles
- How to Schedule a Meeting Across Time Zones: the broader step-by-step process this rotation fits into.
- How to Test an AI Scheduling Assistant for Time Zone Mistakes: five tests to run if a tool is doing this rotation for you.
- Common Time Zone Scheduling Mistakes: related scheduling failures beyond unfair rotation.
Related glossary terms: What Is a Time Zone? · Timezone Abbreviation Ambiguity