Four Rules for Scheduling Meetings Across Time Zones

A meeting time that looks convenient in one city can fall outside working hours in another, especially near a daylight-saving change. A global time view helps you compare the actual date and local time before sending an invitation.

1. Check the date and city

Use named cities and the meeting date rather than a fixed offset such as “UTC+2.” Offsets can change seasonally, and a call can land on a different calendar day for a colleague. Put the time zone in the invitation and ask participants to verify the displayed local time.

2. Share inconvenient slots

For a recurring meeting across distant regions, a perfect time may not exist. Rotate the early or late slot when possible, and ask the team which hours are actually workable. Make the rotation visible so one location does not silently carry the burden every week.

3. Make decisions available afterward

Share a concise summary, decisions, owners, and next steps. A recording or transcript may help absent colleagues, but tell participants before recording and follow the consent and workplace rules that apply to them. Do not assume every meeting needs to be recorded.

4. Use asynchronous updates when they fit

Status updates and comments on a draft often work well in a shared document. Reserve live time for discussion that benefits from immediate exchange. If there is little overlap, a written handoff can let each location continue work during its own day.

Before each meeting series, check the date in Global Time, then revisit the schedule when regional clocks change.

Avoid ambiguous abbreviations such as CST in the written handoff: name the city or time zone. If a participant travels, the calendar invitation can convert the anchor time, but ask them to verify the displayed date and hour.

Frequently Asked Questions (FAQ)

What if one country changes clocks and another does not? Recheck the actual meeting date in both cities. A recurring invite can shift by an hour for one participant while staying fixed for another.

Should the invite say UTC or a city? Use a calendar time zone and name the anchor city in the message. UTC is useful for systems, but a city makes the local working-hour effect easier to check.

What if there is no comfortable overlap? Rotate the inconvenient hour, shorten the synchronous meeting, or use a written handoff. Do not treat a time-zone converter as a solution to a work-hours conflict.