Guide
How to Schedule Meetings Across Time Zones
An international meeting is one instant (or one elapsed interval) described in several civil clocks. If you treat it as “10 AM for everyone,” you have not scheduled anything. A meeting time planner should keep the interval fixed and translate start and end into each participant’s zone, including the local date.
Choosing an organizer time zone
Pick the zone you will type the start time in—often the host’s office. That does not make other zones less real. It only names the wall clock you will use to enter 10:00. IANA identifiers beat “Eastern” in the invitation body as well as in the tool.
Participant time zones
Add every region that must see a local start. Six participant slots plus the organizer cover a typical scattered team. If two people share America/Chicago, they share a row. If one is in Phoenix, do not reuse Denver; America/Phoenix does not follow the same seasonal offset as America/Denver in current rules.
Local working hours
Default 09:00–17:00 Monday–Friday is a convenience on this site, not a law. Use the overlap finder with each person’s actual preference window, including overnight shifts. The overlap is a comparison of those windows. It does not know vacation, holidays, or calendar conflicts, because this site does not read calendars.
Example: three locations, 60 minutes
Organizer America/New_York, 16 September 2026, 10:00, 60 minutes. Participants Europe/London and Asia/Tokyo. Generate meeting times. Every row is the same elapsed hour. Tokyo may show a different calendar date. Copy the table into the invite so nobody has to re-derive London from memory.
Example: checking overlap first
Keep New York 09:00–17:00, London 09:00–17:00, Tokyo 09:00–17:00 on a Wednesday. The common window in New York is typically morning, not late afternoon, because Tokyo’s afternoon has already ended. If the overlap tool reports no window, move the date or accept that “a quick late call” is outside published hours for someone.
Meeting duration and date changes
Duration is elapsed time. A 90-minute meeting that starts at 01:30 in a zone that springs forward at 02:00 does not end at 03:00 local by naive addition; the engine adds 90 minutes to the instant, then converts. Always show start and end local times, not “90 minutes after” in words alone. Date changes belong on the same line as the clock.
Daylight saving time
If the meeting sits on a transition date, open the DST checker for each zone and year. Do not assume the offset you used last month. Ambiguous or skipped local starts should be resolved in the converter before you announce a time.
Shared windows and clear communication
Write each time with a city, local date, local clock, and numeric offset or IANA id. Avoid “9 AM CST.” Prefer 24-hour time if the group is mixed. The share link on this site encodes only zones, date, time, and duration. It is not a calendar file and not a confidential agenda.
A good invitation repeats the same instant three ways: organizer local, each guest local, and UTC. People scan for their own city first. UTC is the tie-breaker when someone forwards the mail without the table. If you only send “10 AM Eastern,” a reader in Mumbai has to do the conversion you already had a tool for.
Overnight and early-morning slots are where wall-clock duration lies. Suppose a session starts at 01:15 in a zone that springs forward at 02:00. Adding 90 minutes on the clock face is not the same as adding 90 elapsed minutes. The planner’s end column is the latter. If you need people on a factory floor to watch a wall clock, tell them the displayed end time, not “an hour and a half later.”
Working-hour overlap is a filter, not a booking. After you find a common window, still ask whether that Wednesday is a public holiday in any of the regions. This site will not know. It also will not know that one participant only works Sunday–Thursday. Change the weekday checkboxes rather than forcing Monday–Friday on every row.
When six participant zones make the table long, keep the organizer at the top and sort the rest by how painful the local hour is. The person at 22:00 should be the reason you move the meeting, not a footnote. Copy the schedule once after the last zone change so an old paste does not survive in the thread. If you later change only the duration, generate again; elapsed time and wall-clock displays both move.
Checking the final schedule
Convert the organizer start with the converter as a second opinion. Compare live clocks only if the meeting is today. For a future Thursday, trust the named zones and the stated date, not a screenshot of “now.”
FAQ
Can this planner add the meeting to Google Calendar?
No. It does not create calendar events.
What if a participant has no seasonal change?
Their offset still comes from the database. Tokyo will not invent a summer shift just because London has one.
Should I schedule in UTC?
UTC is a clear reference. Still list local times; most people read their own wall clock.
Also read conversion basics and UTC versus GMT.