How to Schedule a Meeting Across Multiple Time Zones Without Confusion

You have been there. Someone sends a meeting invite that says '3pm' and does not specify a time zone. You assume it is your 3pm. It is not. You miss the meeting. Or worse — you show up an hour early and sit there alone, slowly realising what happened. Scheduling across time zones is one of those things that seems simple and absolutely is not. Here is how to get it right every time.

Step 1: Always Include the Time Zone — Always

This sounds obvious. It is not obvious enough, because people constantly forget to do it. '3pm' means nothing without a time zone. '3pm UTC' or '3pm Eastern Time (New York)' is unambiguous. One more thing: avoid abbreviations like EST or PST. They are not standardised. EST is used for Eastern Standard Time in North America AND Eastern Summer Time in Australia. Those are very different times. Write out the full name or use the UTC offset.

Step 2: Check Whether DST Is Currently Active

Daylight Saving Time is the sneaky villain of international scheduling. It changes the UTC offset of a location by one hour — and different countries switch on different dates. So a recurring weekly meeting that has always been at the same time can suddenly shift by an hour for some participants when DST kicks in. For example, when the US switches to DST in March but Europe has not switched yet, the gap between New York and London temporarily shrinks from 5 hours to 4 hours. Always use a world clock tool to verify the current offset before scheduling anything important.

Step 3: Find the Overlap Window

When your team spans a lot of time zones, finding a time that works for everyone during normal business hours can feel impossible. And sometimes it genuinely is. The trick is to identify the 'overlap window' — the hours that fall between 8am and 6pm for everyone at the same time. For a team with people in New York and Singapore, that window is basically nonexistent. 8am in Singapore is 7pm the previous evening in New York. One team is always going to be inconvenienced. The fair thing to do is rotate the meeting time so the pain is shared.

Step 4: Use Calendar Invites — They Do the Math For You

Google Calendar, Outlook, and Apple Calendar all automatically convert meeting times to each participant's local time zone when you send an invite. This is the easiest way to make sure everyone sees the right local time. Just set the meeting in your own time zone and let the calendar handle the rest. It will also automatically adjust for DST transitions. Use this feature. It exists for a reason.

Step 5: Confirm in Writing Before the Meeting

Even with calendar invites, it is worth sending a quick message that spells out the time in UTC and in each person's local time. Something like: 'Our call is Tuesday, March 15 at 15:00 UTC — that is 10am New York, 3pm London, 11pm Singapore.' It takes 30 seconds and prevents a lot of confusion. Especially around DST transition weeks.

Common Mistakes That Will Ruin Your Day

• Using timezone abbreviations (EST, PST, IST) without specifying the country — these are not standardised and can mean different things in different places.
• Forgetting that DST transitions happen on different dates in different countries, temporarily changing the offset between locations.
• Setting up a recurring weekly meeting without accounting for the week or two each year when DST transitions cause the time to shift for some participants.
• Assuming a country observes DST — Japan, China, India, and most of Africa do not.
• Confusing UTC+0 with GMT — they are effectively the same, but some systems treat them differently.

Share this article