How to Find the Best Meeting Time Across Time Zones (Without the Guesswork)
Scheduling a call across time zones usually goes one of two ways: someone eyeballs it and gets it wrong, or someone opens three different tabs to cross-check. Neither scales past a couple of time zones. Here’s a more reliable way to think about it.
Start from overlap, not from either person’s clock
The instinct is to ask “what time works for me?” and then convert. That puts one person’s convenience first by default. A better starting point is the overlap window — the hours where both people (or both offices) are inside normal waking hours, say 8 a.m. to 8 p.m. locally.
For two cities roughly 8–9 hours apart, like New York and London or San Francisco and Berlin, that overlap is usually a 2–4 hour window in the respective mornings and afternoons. For cities 12 hours apart, like New York and Singapore, there often isn’t a comfortable overlap at all — someone is taking the call early morning or late evening no matter what. Knowing this up front changes the conversation from “let’s find a time” to “let’s agree on who takes the inconvenient slot this time, and rotate next time.”
The three most common scheduling mistakes
1. Assuming the time difference is fixed.It isn’t, for any pair of cities where at least one observes daylight saving time. The US and Europe change clocks on different dates, so the gap between them shifts by an hour twice a year, for a few weeks each time. A meeting time that was correct in February can be an hour off in April.
2. Scheduling by clock time instead of UTC.If a recurring meeting is saved as “9:00 a.m. New York time” in a calendar that doesn’t timezone-aware convert it, attendees in other time zones will see it shift unexpectedly whenever New York’s DST status changes but their own doesn’t. Most modern calendar tools handle this correctly if the event is created with each attendee’s own time zone attached — but it’s worth checking, especially for recurring meetings set up manually.
3. Ignoring the work week mismatch. Friday afternoon in California is already Saturday morning in much of Asia-Pacific. If a team spans US West Coast and, say, Sydney or Tokyo, the realistic shared work week is Tuesday through Thursday, not five days.
A simple process that works for most teams
- Anchor on the two hardest time zones, not the easiest ones. If your team spans San Francisco, London, and Singapore, find the overlap between San Francisco and Singapore first — that's the tightest constraint. London usually fits somewhere inside whatever window works for those two.
- Convert once, then reuse it.Once you’ve found a slot that works, note it in UTC so it doesn’t need to be recalculated every time someone new joins.
- Rotate the inconvenient slotif there genuinely isn’t a comfortable overlap. Alternating who takes the early or late call keeps it fair and avoids the same person always losing an evening.
- Re-check recurring meetings after DST changes. Twice a year, spend five minutes confirming that standing meetings still land where everyone expects.
When there’s no good overlap
For time differences of 10+ hours, the honest answer is often to reduce how often you need a live call at all — async updates, recorded video, or shared documents cover more ground than people expect, and the live call gets reserved for the handful of things that actually need real-time back-and-forth.
If you need the exact current difference between two specific cities, including whether either is currently in daylight saving time, use the time zone comparison pages to check the live offset rather than relying on a number from memory — it’s the part that changes without anyone announcing it.