How to Schedule Meetings Across Time Zones
Practical strategies for coordinating with remote teams around the world.
Scheduling a meeting across time zones sounds simple — but it's one of the most common sources of confusion in remote work. Here's how to do it right.
The Core Problem
When you say "let's meet at 2pm," you mean your 2pm. But "your 2pm" is meaningless without a timezone reference. This single omission causes thousands of missed meetings every day.
Always include the timezone when scheduling. Not just "2pm" but "2pm EST" or better yet, "2pm UTC-5 (New York)".
Finding Overlap Windows
The hardest part of cross-timezone scheduling is finding times that work for everyone:
Step 1: Identify Core Hours Most knowledge workers are productive from roughly 9am to 6pm their local time. List the working hours for each participant in UTC: - New York (UTC-5): 14:00–23:00 UTC - London (UTC+0): 09:00–18:00 UTC - Tokyo (UTC+9): 00:00–09:00 UTC
Step 2: Find the Overlap New York and London overlap from 14:00–18:00 UTC. Tokyo barely overlaps with either.
Step 3: Rotate the Pain If there's no good overlap, rotate who takes the inconvenient time week to week.
Tools and Best Practices
Use UTC in written communication. "10am UTC" is unambiguous. "10am" is not.
Calendar invitations handle this automatically. When you create a meeting and invite remote participants, the system adjusts the time to each recipient's timezone.
Confirm 24 hours before with the time in each participant's local timezone.
Daylight Saving Time Traps
Different countries change their clocks on different dates. During the 2–3 week windows when countries are "out of sync" on DST, a meeting at a fixed UTC time will appear to shift in local time for some participants. Always verify with a timezone converter around DST boundaries.