Scheduling a meeting between people in different time zones seems simple until you try to do it. The sender calculates what works for them, the recipient converts to their local time and finds the proposed time is either in the middle of the night or during a meal. A reply goes back suggesting an alternative, which the original sender then converts. The back-and-forth takes longer than the meeting itself.

A meeting time planner eliminates this by showing multiple time zones simultaneously and letting you find slots that work for everyone before sending the invitation. The result is fewer scheduling emails and zero confusion about what time the meeting is actually at.

How time zones work and why they are confusing

Time zones are offset from Coordinated Universal Time, abbreviated UTC, by a whole or half number of hours. Most offsets are whole hours but some countries use 30-minute or 45-minute offsets. India is UTC plus 5 hours and 30 minutes. Nepal is UTC plus 5 hours and 45 minutes. These fractional offsets catch people who assume all time zones are whole-hour differences.

Daylight saving time adds another layer of complexity. Countries that observe daylight saving shift their clocks forward in spring and back in autumn, but they do so on different dates. The US and Europe shift their clocks on different weekends, which means for a few weeks each year the time difference between New York and London is different from what it usually is. Not all countries observe daylight saving at all, which changes the difference between countries that do and countries that do not twice a year.

Time zone abbreviations are often ambiguous. EST could mean Eastern Standard Time in the US or Eastern Summer Time in Australia, which are in completely different parts of the world at very different UTC offsets. Using UTC offsets when specifying meeting times removes this ambiguity. UTC minus 5 is unambiguous in a way that EST is not.

Finding overlap when teams span many time zones

Some combinations of locations have no practical overlap during normal working hours. A team split between California and India has a 13-hour difference in winter. If both sides want to be on the call during their standard working hours of 9am to 6pm, there is no overlap at all. Someone has to take a call outside working hours or the team needs to agree on rotating who takes the uncomfortable slot.

Other combinations have better overlap. London and New York have a 5-hour difference, which means late morning in New York overlaps with the afternoon in London. Singapore and Sydney have a small difference that keeps most business hours aligned. Knowing the overlap window in advance lets you set expectations and schedule accordingly rather than discovering at invitation time that a proposed slot does not work.

Best practices for international meeting invitations

Always include the UTC offset in the meeting invitation alongside local times. Writing the meeting time as 3pm EST is less clear than 3pm New York time (UTC minus 5). Including the UTC offset removes any doubt about which specific time the meeting is at.

Calendar software handles time zone conversion for recipients who accept the invitation if the invitation is set up correctly. The meeting shows at the correct local time for each recipient. But this only works if the invitation is created in the correct time zone in the first place. Verify that your calendar software is set to the correct time zone before creating cross-timezone invitations.

For recurring international meetings, establish the meeting time in UTC rather than in one participant's local time. When a participant's country observes daylight saving and changes its offset, a meeting specified in their local time will shift for everyone else unless the UTC time is held constant. Specifying the UTC time and letting each participant calculate their local equivalent keeps the meeting at the intended global time year-round.

Rotating the inconvenient slot fairly

When there is no good overlap and someone has to take a call at an inconvenient time, rotating who takes the early morning or late night slot distributes the inconvenience fairly over time. A team with members in two locations far apart can alternate which side holds the inconvenient slot week by week, or quarter by quarter for less frequent meetings.

Documenting the rotation explicitly so everyone knows when they are expected to take the difficult slot avoids the situation where one team always ends up with the bad time because they never pushed back. Fair rotation requires clarity about who is scheduled to accommodate the other side on which occasions.

Asynchronous alternatives to meetings

Some meetings scheduled across difficult time zones would be better handled asynchronously. A meeting that consists mainly of one person presenting information to others can often be replaced by a recorded video, a detailed written summary, or a document that others can read and comment on at their own time.

Async communication removes the time zone problem entirely because each person engages with the content at a time that works for them. The trade-off is a longer response loop and the loss of the real-time interaction that meetings enable. For decisions that require back-and-forth discussion, real-time meetings are usually better. For information distribution, approval of straightforward items, and status updates, asynchronous formats work well and respect everyone's time zone.

Asynchronous alternatives to meetings across time zones

When the time zone spread makes a convenient meeting time impossible, asynchronous communication becomes not just an alternative but the better option. A recorded video update that can be watched at any time, a shared document where team members add their input when it suits their working hours, or a well-structured async discussion thread often serves the meeting's purpose without requiring anyone to be available at an inconvenient time.

Organizations with large time zone spreads, particularly those with team members in Asia, Europe and the Americas simultaneously, often develop explicit norms about which decisions require synchronous discussion and which can be handled asynchronously. Defaulting to async for routine updates, status reports and non-urgent decisions reserves synchronous meeting time for situations where real-time discussion genuinely adds value.

Time zone awareness tools that show the current time for each team member's location make the logistics of scheduling more transparent. When everyone can see at a glance what time it is for each person, proposing a meeting time that is reasonable for everyone becomes faster and avoids the back-and-forth of checking whether a proposed time works for people in different locations.

Daylight saving time complications

Daylight saving time changes create scheduling problems that regular time zone converters do not handle correctly. Clocks change on different dates in different countries, and some regions within countries do not observe it at all. A meeting scheduled based on a time zone difference calculated before a daylight saving change may be off by an hour after the change if the two regions switch on different dates.

Using tools that account for daylight saving time transitions, or specifying meeting times in UTC which does not change seasonally, eliminates this source of confusion. Recurring meetings scheduled across time zones should be reviewed when clocks change in any of the participating regions to ensure the scheduled time is still correct. Calendar applications from major providers generally handle this correctly, but manually coordinated meetings without calendar invites are vulnerable to daylight saving time errors.

Rotating meeting times in recurring international team meetings ensures the same people are not consistently burdened with the least convenient slot. If one team member is always asked to join early in the morning or late at night, rotating so that the inconvenient time is shared across the team is fairer and maintains better long-term working relationships. A schedule that distributes the time zone burden equally is worth the administrative overhead of adjusting meeting times periodically.