A meeting time zone rotation spreads the inconvenient hours across everyone on the team, so the same one or two people aren’t always the ones staying up late or waking up early.
On a team that spans several time zones, the meeting time usually gets picked once and then repeats forever. It suits whoever was in the room when it was chosen. Others adapt quietly, week after week, until it becomes “just how it is.” Nobody decided it should be unfair. It simply never got counted.
Counting is the fix, and counting is something AI is useful for as long as it shows its arithmetic. This guide shows how to list everyone’s working hours, convert candidate meeting times into local times, count who lands outside their window, and build a rotation that evens out the burden. The team and numbers in the examples are invented. Time zones and daylight saving rules do change, which is why the public tz database records each zone’s history of offsets and daylight saving use, and is updated periodically to reflect government changes.
Contents
Why “One Fixed Time” Quietly Costs Someone
When a team has members eight or more hours apart, no single time is comfortable for everyone. That’s geometry, not bad planning. What matters is who pays. A fixed time makes the same people pay every week. A rotation shares the cost, and it makes the cost visible, which often leads to a better conversation about which meetings need to be live at all.
Three Ways to Pick a Time
- Fair on paper: One fixed time – No; Rotate without counting – Maybe; Rotate with a count – Yes.
- Easy to run: One fixed time – Yes; Rotate without counting – Yes; Rotate with a count – Yes, once set up.
- Shows who’s burdened: One fixed time – No; Rotate without counting – No; Rotate with a count – Yes.
- Handles changes in the team: One fixed time – Poorly; Rotate without counting – Poorly; Rotate with a count – Well.
- Risk of hidden unfairness: One fixed time – High; Rotate without counting – Medium; Rotate with a count – Low.
Collect Windows, Convert Times, and Count
Step One: Collect Working Windows
Ask each person for their local working hours and what they consider an unreasonable time for a meeting. Don’t assume. A person may be happy with 7:00 a.m. calls and unwilling to take anything after 6:00 p.m., or the reverse. For each person, record:
| Person | Time zone (UTC offset on the meeting date) | Window they’re comfortable with |
|---|---|---|
| Ana | UTC-8 | 8:00 to 18:00 |
| Ben | UTC+0 | 8:00 to 18:00 |
| Cleo | UTC+5:30 | 8:00 to 18:00 |
| Dev | UTC+9 | 8:00 to 18:00 |
This team and its offsets are invented. For real people, use the offset in effect on the date of the meeting, since daylight saving changes can shift it by an hour. Different people can have different windows, and it’s fine to give some people wider windows than others if they’ve said so.
Step Two: Convert Candidate Times
Pick a handful of candidate meeting times in a single reference time, such as UTC. For each, work out each person’s local time: UTC time plus their offset, wrapping around midnight.
For example, 08:00 UTC is 00:00 for Ana (08:00 minus 8 hours), 08:00 for Ben, 13:30 for Cleo (08:00 plus 5:30), and 17:00 for Dev (08:00 plus 9). Then mark each local time as inside or outside that person’s window.
Step Three: Let AI Do the Counting
This is a tedious, error-prone task for humans, and AI handles it well if you make it show the work:
I'm building a fair rotation for team meetings across time zones. Here are the team members, their UTC offsets on the meeting date, and their comfortable windows.
[paste the table]
Candidate meeting times in UTC: [list, such as 00:00, 08:00, 16:00]
Please:
1. For each candidate time and each person, show the calculation (UTC time plus offset, wrapped past midnight) and the local time.
2. Mark each local time as INSIDE or OUTSIDE that person's window.
3. For each candidate time, count how many people are OUTSIDE and name them.
4. Do not recommend a single best time.
Then, given I hold [N] meetings in the rotation, show the cumulative number of outside-window meetings each person would have under these three plans: (a) always using the first candidate time, (b) rotating through all candidates in order, (c) any combination you find that keeps the maximum per-person count as low as possible.
Rules:
- Use only the offsets, windows, and times I gave.
- Do not assume daylight saving changes. If a date might be affected, write "CHECK DST."
- Show all arithmetic.
- Do not decide which plan is fair. Present the counts.Treat this prompt as my suggestion: it is not taken from any official guide.
The prompt asks for every calculation to be shown, which matters most with half-hour offsets and midnight wraparound, where mistakes are easiest to make.
Worked Example for Meeting Time Zone Rotation
For the team above, with comfortable windows of 8:00 to 18:00, consider three candidate times in UTC:
| UTC time | Ana (UTC-8) | Ben (UTC+0) | Cleo (UTC+5:30) | Dev (UTC+9) | Outside |
|---|---|---|---|---|---|
| 08:00 | 00:00 outside | 08:00 | 13:30 | 17:00 | Ana (1) |
| 00:00 | 16:00 | 00:00 outside | 05:30 outside | 09:00 | Ben, Cleo (2) |
| 16:00 | 08:00 | 16:00 | 21:30 outside | 01:00 outside | Cleo, Dev (2) |
No time keeps everyone inside their window. That’s the honest finding, and it’s useful to see in a table.
Now compare plans over six meetings:
- Always 08:00 UTC: Ana is outside her window all six times. Ben, Cleo, and Dev are never outside. Total: 6.
- Rotate evenly through all three (two meetings each): Ana 2, Ben 2, Cleo 4 (two meetings at 00:00 plus two at 16:00), Dev 2. Total: 10. Cleo carries double.
- A balanced mix: 08:00 three times, 00:00 once, 16:00 twice: Ana 3, Ben 1, Cleo 3 (once at 00:00 plus twice at 16:00), Dev 2. Total: 9, and the highest individual count is 3.
Simple rotation looks fair but isn’t, because Cleo appears in two of the three slots. The balanced mix keeps the maximum at 3, and the total is lower than the even rotation (9 versus 10), though Ana, who’s outside only in one slot, ends up carrying 3.
Whether that’s acceptable is a conversation, not a calculation. Maybe Ana prefers occasional very late calls to others’ more frequent early ones, or maybe the team decides some of these meetings should be written updates instead. All the numbers here are invented, and your team’s windows will produce different results.
Weigh the Pain, If You Need To
Not every outside-window time is equally bad. A 6:30 a.m. call may be easier than a midnight one. If your team agrees, add weights, such as 1 for slightly outside, 2 for quite outside, and 3 for the middle of the night, and count weighted totals instead. Keep it simple. A scheme nobody understands won’t be trusted.
Keep a Running Tally
Make a small sheet with one column per person and one row per meeting, and record whether each person was outside their window. Update it after each meeting. Every few weeks, look at the cumulative totals and pick the next time that evens things out. The tally is the real fairness tool, since it replaces “I feel like I always get the bad slot” with something everyone can see.
Make the Rotation Work in Practice
Ask Whether the Meeting Needs to Be Live
The fairest late-night meeting is the one that doesn’t happen. For each recurring meeting, ask:
- Could it be a written update?
- Does it need everyone, or only some people?
- Could it be recorded or summarized for people who can’t attend?
- Does it need to be weekly?
If you do record or summarize, check your team’s privacy and consent rules first. If a meeting remains live, the rotation shares the cost.
Know the U.S. Daylight Saving Dates
According to NIST: Daylight Saving Time Rules, U.S. daylight saving time starts at 2:00 a.m. on the second Sunday of March and ends at 2:00 a.m. on the first Sunday of November; in 2026 those dates are March 8 and November 1. It also says Hawaii, American Samoa, Guam, Puerto Rico, the U.S. Virgin Islands and Arizona (except the Navajo Nation) do not observe it, and that the U.S. Department of Transportation regulates daylight saving time and time zones. For a team with members in those places, enter the offset per person per date in your table, and flag every meeting in the weeks around March and November, since the gap between two people can change by an hour even when neither moves.
Announce the Schedule Well in Advance
A rotation only feels fair if people can plan around it. Publish the next six to eight meeting times at once, with each person’s local time shown next to the slot, so nobody has to do the conversion in their head. Put the dates in a shared calendar, and note which slots fall near a daylight saving change. When a meeting time moves, say why. “We’re shifting this one to 16:00 UTC because Ana took the last three early calls” is a sentence that builds trust, and it only exists if you’ve kept the tally.
Be Clear About Flexibility
Let people say “I’d rather take the early slot more often” or “I can’t do Tuesdays.” A fair rotation respects stated preferences, not just math. Also say what happens when someone swaps: do they take the next bad slot, or does the tally adjust?
Meeting Time Zone Rotation: Mistakes to Avoid
- Assuming offsets never change. Daylight saving rules differ by place.
- Rotating evenly through slots instead of counting people. The example shows how that can overload someone.
- Not asking people about their windows. Don’t guess what’s inconvenient.
- Accepting conversions without the shown calculations. Half-hour zones and midnight wraparound cause errors.
- Treating the schedule as permanent. Teams change. Rerun it when someone joins or moves.
Questions About Meeting Time Zone Rotation
What is a meeting time zone rotation? It’s a schedule that varies meeting times so the inconvenient hours are shared across team members instead of falling on the same people.
How do I make a meeting time zone rotation fair? Count how many times each person lands outside their comfortable window, and choose times that keep those counts balanced over weeks.
Can AI plan a meeting time zone rotation? It can convert times and count outside-window meetings if you give it the offsets and windows and require it to show its work.
What if no time works for everyone? That’s common on spread-out teams. Rotate, reduce the number of live meetings, and use written updates or recordings where you can.
How should I handle daylight saving time? Use each person’s offset on the actual meeting date, and recheck when clocks change in any region.
Should everyone have the same working window? Not necessarily. Ask people for their own, and record them.
How often should I revisit the rotation? When the team changes, when clocks change, or when the running tally shows someone carrying too much.
Count Last Month’s Calls
Take your last month of recurring meetings, convert each into everyone’s local time, and mark who was outside their window. You’ll likely see a pattern you hadn’t noticed. A meeting time zone rotation built on that count shares the late calls openly, and it gives your team a fairer schedule that anyone can check.
This article offers general team-management tips. Time zone offsets and daylight saving rules vary by place and date. The example team, times, and counts are fictional.
Sources:
Leave a Reply