How to Schedule Meetings Across Time Zones
Dev Nexus5 min read
How to find overlapping working hours across time zones and pick a meeting slot that is fair to everyone - without the daylight saving and date-rollover slip-ups.
Scheduling a call for one city is easy. Scheduling one that works for teammates in three countries is where things fall apart - someone is always asked to dial in at breakfast, dinner or midnight. The goal is not just "a time", but a time that lands inside everyone's working day.
This guide shows how to find the overlapping working hours across zones, pick a slot that shares the inconvenience fairly, and avoid the daylight saving and date mistakes that quietly wreck recurring meetings.
The Problem
A distributed team's working hours only overlap for part of the day, and the window shrinks as zones spread further apart. New York and London share a comfortable afternoon; add Sydney and the overlap narrows to almost nothing. Finding that window in your head means juggling several offsets at once, which is error-prone.
Two things make it harder. Daylight saving shifts the overlap by an hour a few times a year, on dates that differ by country, so a slot that worked in June can be off in November. And for a recurring meeting, you are not choosing one time but a fair rotation, since someone usually has to take the early or late call.
The Solution
The reliable method is to convert everyone's working hours into a single view and look for the hours that fall inside the workday in every zone. The Time Zones tool makes this quick: add each participant's city, then scan the columns for a time that sits comfortably in all of them.
Because it follows the IANA database, it applies each region's current daylight saving rule for the date you are planning, so the overlap you see is the real one. And because it runs in your browser, attendee locations and meeting details stay on your device. Once you have the slot, converting the exact start time for each invite is a matter of reading it off - and if you are stamping a system event with an epoch value, the Timestamp Converter turns that into a readable local time.
Step-by-Step Guide
- 1
List every participant's zone and working hours
Write down each attendee's city and the hours they consider workable - for example
09:00 to 17:00local. Use cities rather than abbreviations so the correct offset and daylight saving rule apply. This defines the constraints you are solving for. - 2
Line the zones up side by side
Add each city to the converter so their local times sit in parallel columns. Now a single moment - say
15:00in London - shows instantly as the local time everywhere else, without any mental arithmetic. - 3
Find the overlapping window
Scan for the hours that fall inside the workday in every zone at once. That shared band is your candidate window. The wider the spread of zones, the narrower it gets, so identify the whole overlap before committing to a single time.
- 4
Pick a fair slot and rotate if needed
If the overlap forces someone into an early or late hour, share the burden - alternate the meeting time for recurring calls so the same person is not always inconvenienced. Aim for the middle of the overlap when you can.
- 5
Send the invite in each local time and check the date
Confirm the start time for each attendee and make sure the calendar date is right where the conversion crosses midnight. A well-configured calendar invite stores the zone, but stating each local time in the message removes any doubt.
Common Mistakes
Ignoring daylight saving on recurring meetings
A slot fixed in spring can drift by an hour once one country changes its clocks and another has not. Recheck recurring meetings around the transition dates, since countries switch on different days.
Always inconveniencing the same person
When the overlap is tight, defaulting to one time repeatedly means one region always takes the undefined a.m. or undefined p.m. call. Rotate the slot so the early-and-late burden is shared fairly across the team.
Forgetting the meeting can fall on a different day
Across wide gaps like the US to Asia, an afternoon call for one person is the next morning for another. Miss the date change and someone books the wrong day entirely.
Relying on 'my time' in the invite
Sending a time without naming the zone forces every reader to guess and convert. State each local time, or anchor to UTC, so nobody has to reverse-engineer what you meant.
Frequently Asked Questions
How do I find a meeting time that works across time zones?
List each participant's working hours in their own zone, line the zones up side by side, and look for the hours that fall inside everyone's workday at once. That overlapping window is where you should place the meeting.
What if there is almost no overlap between zones?
When zones are far apart the shared window is small, so pick the edge of the overlap and rotate the slot for recurring calls. Sharing the early-or-late burden across the team is fairer than fixing one inconvenient time forever.
How does daylight saving affect a recurring meeting?
Clock changes shift the overlap by an hour, and countries switch on different dates, so a fixed slot can drift out of everyone's working hours. Recheck the times around the transition dates and adjust the invite if needed.
Should I schedule the meeting in UTC?
Anchoring to UTC is a clear reference that avoids the "my time" problem, but most people find it easier to see the slot in each local time. A converter lets you do both - confirm in UTC, then show the local time for each attendee.
Are attendee locations kept private when I plan a meeting?
Yes with the Time Zones tool - it works entirely in your browser and uploads nothing, so the cities and times you compare never leave your device, and it keeps working offline.
Try the Tool
Time Zones
Line up every attendee's zone in your browser and spot the overlapping hours instantly - private, nothing uploaded.
Related Tools
Related Articles
How to Convert Between Time Zones
A step-by-step guide to converting a time from one zone to another accurately, including the daylight saving and date-rollover traps that catch people out.
Read articleAre UUIDs Really Unique?
In practice UUIDs never collide - here is the math behind why, and the one thing people get wrong: a UUID is an identifier, not a secret.
Read articleencodeURI vs encodeURIComponent Explained
The clear difference between encodeURI and encodeURIComponent, with examples showing which one to use for a value versus a whole URL.
Read article