How to Schedule Meetings Across Time Zones (Without the Headache)

Remote work made the whole planet your potential meeting room — and made "wait, what time is that for you?" a daily question. Scheduling across time zones isn't hard once you have a system. Here's how to pick times that work, dodge the classic mistakes, and confirm them so nobody shows up an hour late.

Start from a single reference

The root of most scheduling chaos is everyone thinking in their own local time. The fix is to anchor on one neutral reference, then translate outward. Many distributed teams agree on UTC as that anchor: "the sync is at 15:00 UTC" means the same instant for everyone, and each person converts it once to their local time. If UTC feels abstract, anchor on one person's city instead — just be explicit about which one.

Find the overlapping working hours

Before proposing a time, figure out when participants are actually awake and working. List each person's location and their typical 9-to-5, then look for where those windows overlap.

• Small spread (1–4 hours apart): easy — most of the workday overlaps.
• Medium spread (5–8 hours, e.g. US and Europe): the overlap is usually the European afternoon / American morning. Aim there.
• Large spread (9+ hours, e.g. US and Asia): there may be almost no shared working hours. Someone will have to take an early-morning or late-evening call — so rotate who makes the sacrifice.

Watch out for daylight saving time

This is the single most common cause of missed meetings. The gap between two cities isn't fixed — it shifts when one region springs forward or falls back and the other doesn't. For a few weeks each spring and autumn, the difference between, say, London and New York is briefly an hour off its usual value. Never assume last month's offset still holds. A converter that applies each region's daylight saving rules automatically removes this risk entirely.

Confirm the time clearly

However careful you are, the way you write the time can still cause a miss. A few habits that prevent it:

• Always name the zone. "3 PM" is useless across borders; "3 PM EST (20:00 UTC)" is unambiguous.
• Use 24-hour time in writing to avoid AM/PM mix-ups — see our guide on the 12 vs 24-hour clock.
• Include the date. A time near midnight can fall on a different calendar day in another zone.
• Let the calendar do the work. Tools like Google Calendar store the event in a fixed zone and display it in each guest's local time automatically — the safest option for recurring meetings.

Be considerate with recurring meetings

A weekly call at a comfortable hour for you might land at 6 AM for a teammate. For anything recurring, check what the time feels like on the other end, and if there's no fair option, rotate the inconvenient slot between people. Small gestures like this matter more than any tool.

The fast way to do all of this

You don't need spreadsheets. Use the time zone converter to instantly see what a proposed time looks like in every participant's zone, with daylight saving handled for you. Glance at the world clock to see who's currently in their workday, and set a countdown or alarm so you don't miss the call yourself.