Blog

How to plan rotating meeting times across time zones

Plan a fair meeting rotation across time zones, compare local times before you send an invite, and avoid confusion when daylight saving changes.

Lauren HughesTools and utilities 5 min read

A meeting that lands in the middle of the workday for one colleague may start before sunrise or run late at night for someone else. If the same people always take the inconvenient hour, attendance and morale can suffer.

A rotating schedule shares that burden. Use the World Clock to compare local times, then choose a repeatable rotation that colleagues can understand and plan around.

Plan a rotating meeting schedule

  1. Open the World Clock and add the cities or time zones where regular attendees work. Use the city that matches each person’s location, not just a country name, since some countries span multiple time zones.
  2. Choose a set of candidate meeting times in the organizer’s local time. Check each candidate against the clock for every attendee, including the date. A time that is Tuesday afternoon for you might be Wednesday morning elsewhere.
  3. Agree on reasonable hours before picking a rotation. Ask colleagues what counts as too early or too late for them, and note any recurring limits such as school pickup or a shift change. Do not assume that everyone works the same hours.
  4. Pick a rotation pattern, such as an early slot one week and a late slot the next. Check the whole pattern across all locations before publishing it, rather than comparing only the first meeting.
  5. Write each invite with the date, the organizer’s time zone, and the meeting link. Use a calendar invitation that displays in each attendee’s local time, and state the rotation in the invitation description.

For a team that meets regularly across several regions, it can help to keep a shared reference with each attendee’s city and normal working hours. For another approach to keeping local times visible for a team, see How to build a world clock for an online team.

Choose a rotation that fits your team

Alternate between two slots

Two meeting times are easy to remember and work well when the group has two main regions. For example, one week can favor the region that is earlier in the day, while the next favors the region that is later. Check the actual local times before using a slot, since the gap between regions can change during the year.

Rotate among regions

For a team spread across three or more regions, you can take turns choosing the slot that is most convenient for a different group. A rotation such as Region A, then Region B, then Region C makes the intent clear. It does not guarantee every person gets an ideal time, so review the impact on individuals as well as on regions.

Keep one slot and rotate who attends

Sometimes a meeting cannot move because it depends on a customer, a live operation, or another fixed event. In that case, keep the time stable and rotate which team members are expected to attend live. Share notes or a recording with people who are not attending, and check that this arrangement does not leave anyone out of decisions.

Use a range instead of a single time

If attendees have different work schedules, ask each person to mark the hours they can usually attend. Look for a shared window, then rotate within that window when possible. A short poll can help gather availability, but verify the final options against the World Clock before you send invitations.

Keep the rotation fair and predictable

Fair does not have to mean that every person gets exactly the same number of early and late meetings. It means the team can see how decisions are made and that the same colleagues are not repeatedly asked to absorb the inconvenience.

  • Count the awkward hours. Keep a simple record of which regions or people get the earliest and latest starts. Review it over several meetings, not just one week.
  • Publish the pattern ahead of time. Sharing the next few meeting dates lets people arrange work and personal commitments. Avoid changing the time at the last minute unless there is a real need.
  • Rotate the burden, not just the clock time. A meeting at 8 a.m. may be manageable for one person and difficult for another. Ask the people affected and take their actual schedules into account.
  • Keep meetings focused. If someone must join outside their normal hours, use an agenda and start on time. Move optional updates to a written note rather than extending the call.

Check daylight saving time before sending invites

Daylight saving time can shift local clocks by an hour, and regions do not all change clocks on the same date. Some places do not observe daylight saving time at all. As a result, a meeting that currently appears at 9 a.m. for one group may appear at 8 a.m. or 10 a.m. for them for a few weeks, even if the organizer keeps the same local time.

Check the first meeting after each seasonal clock change, especially when attendees are in different countries or states. The World Clock can help you compare current local times, but a current-time view is not a substitute for checking a future meeting date. When possible, create calendar invitations with the intended time zone so calendar software can adjust the displayed time for each guest. Include the date and time zone in any written schedule as well.

If colleagues report different dates for a meeting, confirm the invitation’s date and the time zone it uses before changing the time. A date change across the International Date Line can be normal, not an invitation error. For more on why this happens, see Time zones on the International Date Line.

Before finalizing the schedule, ask one attendee in each region to confirm that the invite appears at the expected local time.