Learning how to schedule meetings across time zones comes down to three things: find the hours that fall inside everyone’s working day, anchor the meeting to one named zone, and write the time into the invite so nobody has to convert it themselves. Do those three and the hour-long email chains disappear. Skip them and you get the classic three-hour call that starts at 6 a.m. for half the room.
The hard part isn’t the arithmetic. It’s that a “9 a.m. meeting” means nine different things depending on who reads it, and daylight saving shifts the math twice a year under everyone’s feet.
Table of Contents
- What You Need
- How to Schedule Meetings Across Time Zones Step by Step
- Step 1: Confirm Everyone’s Time Zone
- Step 2: Find a Time That Works for Everyone
- Step 3: Convert the Meeting Time Accurately
- Step 4: Create a Clear Calendar Invitation
- Step 5: Send the Time in More Than One Format
- Step 6: Confirm and Reschedule Responsively
- Common Mistakes When Scheduling Meetings Across Time Zones
- Frequently Asked Questions
- What is the easiest way to schedule meetings across time zones?
- How do I write a meeting time so nobody gets confused?
- Should I use EST, EDT, or UTC in calendar invitations?
- How do I schedule a recurring meeting for people in different countries?
- What should I do if there is no convenient time for everyone?
- How do I handle a daylight-saving change after scheduling a meeting?
- Conclusion
What You Need
Gather these five things before you touch a calendar. Ten minutes of prep saves an hour of rescheduling.
- A shared calendar that everyone actually updates, so you can see real conflicts instead of guessing.
- A meeting platform that generates one link for all participants, whichever zone they join from.
- A time zone planner or converter — timeanddate’s World Clock Meeting Planner and World Time Buddy both do this free in a browser.
- Each participant’s location or time zone, plus their normal working hours and any public holidays.
- The meeting details: purpose, duration, agenda, and whether anyone needs to prepare something.
If you skip the working hours list and rely on a free slot showing in someone’s calendar, you’ll schedule a 7 a.m. call for a colleague whose 8 a.m. starts at 6 p.m. their time. A calendar that looks empty is often empty because that person simply does not book before 9 a.m.
How to Schedule Meetings Across Time Zones Step by Step
Step 1: Confirm Everyone’s Time Zone
Ask each person for a city, not a time zone. “Are you on EST or CST?” is a bad question, because those abbreviations are reused across countries and many people answer with the wrong one.
Ask instead: “Which city are you working from this month?” Then look the city up in a tool that reads the IANA time zone database — the same database your phone and laptop use. It adjusts for daylight saving automatically, which a raw UTC offset never does.
It worked for me when a colleague in Lisbon told me they were on “Western European Time” and the invite kept landing an hour off for two weeks. The city answer settled it in ten seconds.
Step 2: Find a Time That Works for Everyone
Write down everyone’s working hours in their own local time, then convert them all onto one grid. Most planners shade out non-working hours and leave the usable overlap in white.
A worked example. Portland works 8 a.m.–5 p.m. Pacific. New York works 9 a.m.–6 p.m. Eastern. Shanghai works 9 a.m.–6 p.m. China Standard Time. Portland to Shanghai is 15 hours apart, so there is no honest overlap between working hours — Portland’s morning is Shanghai’s midnight.
That is the moment to stop searching for a perfect slot. Either take a short early or late hit for one region, or change the format. A 20-minute voice call instead of a 60-minute video call shrinks the pain considerably.
For groups that do have overlap, a poll beats guessing. Doodle and When2Meet both let people mark availability in their own local time and show you the slot with the most votes. When2Meet is plain and still does the job, while Doodle handles more group logic; free scheduling links in Google Calendar or Outlook do the same thing for one-to-ones.
How you tell it worked: every attendee can state the meeting time in their own local time and it matches.
Step 3: Convert the Meeting Time Accurately
Pick one zone as the anchor and convert into it once. Most teams use their headquarters zone, which stops the meeting from shifting every time the organizer changes.
Watch for offsets that are not whole hours. India is UTC+5:30, Nepal is UTC+5:45, and Australia’s Central zone is UTC+9:30. This is the single most common conversion error and it produces meetings that are 30 or 45 minutes off — technically scheduled, completely wrong.
Here are the offsets you will meet most often:
| Location | Standard offset | Daylight saving |
|---|---|---|
| US Eastern | UTC-5 | UTC-4 |
| US Pacific | UTC-8 | UTC-7 |
| London | UTC+0 | UTC+1 |
| Central Europe | UTC+1 | UTC+2 |
| India | UTC+5:30 | No change |
| Nepal | UTC+5:45 | No change |
| Singapore | UTC+8 | No change |
| Sydney | UTC+10 | UTC+11 |
| Chatham Islands | UTC+12:45 | UTC+13:45 |
India, Nepal and Singapore do not observe daylight saving, so a call with a US team shifts by an hour for part of the year even though nothing about the invite changed. Recurring meetings drift for the same reason: the series keeps the local clock time while the offset moves underneath it. Check recurring invites after both transitions.
Step 4: Create a Clear Calendar Invitation
The invitation itself does the conversion for you, if you fill it in properly. Include the meeting title, date, start and end time, time zone, duration, video link, agenda, and any attachments.
Setting the time zone field explicitly matters more than it looks. If you leave it blank, your calendar assumes your own zone, and an organizer travelling for a week will silently book everything an hour or several hours off.
Ask guests to confirm. It costs one click and it surfaces a conflict before the day of the call rather than at the start of it.
Step 5: Send the Time in More Than One Format
Put the time in the body of the email or chat message, repeat it in the calendar invitation, and keep the subject line specific enough that the event is recognisable in a crowded inbox.
Show both zones. This template does most of the work for you:
Subject: Q4 roadmap sync — Tue 14 Oct, 2:00 PM ET / 11:00 AM PT
Body: Tuesday 14 October, 2:00–3:00 PM Eastern (UTC-4) / 11:00 AM–12:00 PM Pacific (UTC-7) / 8:00 PM India (UTC+5:30). Video link below. Agenda: roadmap risks, launch date, open owners. Please confirm you can make it.
When you write that 2:00 PM ET, everyone recognises the number without running a conversion. That is the whole trick.
Step 6: Confirm and Reschedule Responsively
Send a short reminder a day or two ahead with the time in both zones again. Use the same calendar event rather than a fresh message thread — editing the event updates it on every attendee’s calendar at once.
If you need to move the meeting, change the original event rather than sending a new invite. Editing one event beats sending a correction that leaves the old entry alive on someone’s phone.
Record recurring meetings and post the recording where everyone can reach it. It is the fairest option for the colleague whose 6 a.m. is your midnight.
How you tell it worked: no one asks what time the call is, and nobody joins an hour late.
Common Mistakes When Scheduling Meetings Across Time Zones
- Using abbreviations like EST or CST. These are reused across countries. Write the full zone name or the offset, for example “Eastern (UTC-4)”.
- Forgetting half-hour and 45-minute zones. India at UTC+5:30 and Nepal at UTC+5:45 are where a whole-hour assumption quietly breaks.
- Overlooking daylight saving. A slot chosen in January can be an hour off in July. Check recurring meetings after both transitions.
- Treating an empty calendar as availability. People book their own working hours. Check the actual working hours, not the absence of events.
- Sending a new invite instead of editing the old one. The old event stays live and someone shows up at the wrong time.
- Always landing on the same inconvenient slot. Rotate it. Repeatedly imposing the early or late slot on one region burns people out, even when the calendar shows no conflict.
- Holding the meeting at all. If the only workable slot is 5 a.m. for someone, a shared document or a recorded update often serves the goal better.
Frequently Asked Questions
What is the easiest way to schedule meetings across time zones?
Use a planner that shows several zones on one grid, pick a slot inside everyone’s working hours, then anchor it to one named zone and put that time in the invite with the zone name. Free options include timeanddate’s World Clock Meeting Planner and World Time Buddy. The booking itself happens in your own calendar, which converts the time automatically for each attendee.
How do I write a meeting time so nobody gets confused?
Write the date, the time, the zone name and the offset, then repeat the same time in the other zone each attendee will recognise. For example: Tue 14 Oct, 2:00 PM Eastern (UTC-4) / 11:00 AM Pacific (UTC-7). Avoid bare abbreviations, and avoid times like 9:00 without a date, because overnight time differences push some regions into the next or previous day.
Should I use EST, EDT, or UTC in calendar invitations?
Use the zone your attendees know rather than a generic offset. UTC is the safest neutral anchor for technical or international groups because it never changes, but it is harder to read for people who think in local time. Whatever you choose, spell it out and include the offset, and set the time zone field in the calendar event rather than relying on the abbreviation alone.
How do I schedule a recurring meeting for people in different countries?
Pick a time in the anchor zone, confirm everyone can attend that time at least twice a year, and set the recurrence in your calendar so it keeps local clock time. Daylight saving shifts the offset twice a year while the clock time stays fixed, so the meeting moves an hour for one region. Add a reminder to re-check the series after each transition and tell the team in advance.
What should I do if there is no convenient time for everyone?
Shorten the meeting and pick the slot that hurts least, then rotate it so the same region is not always waking early or joining late. If the gap is more than a few hours, record a short update or write it up asynchronously instead. Recording the meeting for people who could not attend fairly is usually better than moving the call to an hour nobody can make.
How do I handle a daylight-saving change after scheduling a meeting?
Check the meeting date against both the standard and daylight saving offsets for every location, then confirm in writing which offset applies. For recurring series, the clock time stays the same while the offset changes, so review the series after each transition. Tell attendees in advance rather than adjusting silently, and never assume a region that does not observe daylight saving will shift with you.
Conclusion
Start with the first action, not the tool: ask every participant for the city they are working from, pick a slot inside those working hours, and write the date, time and zone into the calendar event and the message body. Once that habit is in place, which planner you use stops mattering.