guide8 min read

How to Schedule Meetings Across Time Zones

A practical guide to finding overlap windows, avoiding scheduling mistakes, and using the right tools to coordinate teams across continents β€” with worked examples for the most common city pairs.

WT
WhatTimeIsIt.blog Editorial Team
Time zone researchers and data analysts
Published February 1, 2026Updated April 22, 2026Fact-checked April 22, 2026
Methodology: Data in this article is sourced from the IANA Time Zone Database, live weather from Open-Meteo, and our own dataset of 92 cities across 61 countries. All times are computed in real-time using browser-native Intl.DateTimeFormat APIs. This article is reviewed and updated quarterly.
Table of Contents

Remote and distributed teams have made international scheduling a daily reality for hundreds of millions of workers. Yet despite decades of globalization, scheduling a meeting across time zones remains one of the most reliably frustrating tasks in modern work life. Missed calls, confused attendees, and the dreaded "I thought it was 3pm your time" are universal experiences.

This guide covers the practical mechanics of cross-timezone scheduling: how to find overlap windows, how to handle DST transitions, which city pairs are easy versus nearly impossible to align, and the tools and habits that eliminate most scheduling errors.

Business Hours Overlap by City Pair

The first step in scheduling any international meeting is understanding how much overlap exists between standard business hours (9am–5pm) in each location. The table below shows the overlap for ten major city pairs β€” color-coded by difficulty.

City PairOverlap WindowHoursDifficulty
New York / London2pm–5pm GMT / 9am–12pm ET3heasy
New York / TokyoNone in business hours0hhard
New York / SingaporeNone in business hours0hhard
London / Dubai9am–5pm GMT / 1pm–9pm GST8heasy
London / Singapore9am–1pm GMT / 5pm–9pm SGT4hmoderate
London / Sydney9am–10am GMT / 8pm–9pm AEDT1hhard
Dubai / Singapore9am–5pm GST / 1pm–9pm SGT8heasy
LA / New York12pm–5pm ET / 9am–2pm PT5heasy
Berlin / Singapore9am–1pm CET / 4pm–8pm SGT4hmoderate
Sydney / Tokyo9am–5pm JST / 10am–6pm AEDT8heasy

The Impossible Pairs: New York–Tokyo and New York–Singapore

Zero Business-Hours Overlap

Some city pairs have zero business-hours overlap. New York (UTCβˆ’5) and Tokyo (UTC+9) are 14 hours apart in winter. When it's 9am in New York, it's 11pm in Tokyo. When Tokyo opens at 9am, it's 7pm the previous evening in New York. There is no time that is business hours in both cities simultaneously.

The practical solutions for these pairs are:

  • Early morning New York / Late evening Tokyo: 8–9am ET is 9–10pm JST. Tolerable for occasional calls, unsustainable as a recurring slot.
  • Asynchronous-first workflow: Use recorded video updates, detailed written briefs, and shared documents. Reserve live calls for high-stakes decisions only.
  • Rotating burden: Alternate who takes the inconvenient slot, so neither team always bears the cost.
  • Overlap days: Schedule live collaboration during the few weeks per year when teams are in the same location for offsites or conferences.

The DST Scheduling Trap

The Transition Week Problem

Daylight Saving Time creates a particularly nasty scheduling trap for recurring meetings. Consider a weekly call between New York and London, set for "3pm London time / 10am New York time" in January:

  • January–March 8: NY is UTCβˆ’5, London is UTC+0. Difference: 5 hours. Call is 10am ET / 3pm GMT. βœ“
  • March 9–30 (USA springs forward, UK hasn't): NY is UTCβˆ’4, London is UTC+0. Difference: 4 hours. The calendar invite still says 10am ET β€” but that's now 2pm London time, not 3pm. βœ—
  • March 31 onward (UK springs forward): NY is UTCβˆ’4, London is UTC+1. Difference: 5 hours again. 10am ET = 3pm BST. βœ“

The three-week window between the US and UK transitions catches teams out every single year. The fix: use calendar tools that store meetings in UTC and display them in local time, rather than storing them as a fixed local time.

Six Best Practices for Cross-Timezone Scheduling

πŸ•
Always state the time zone
Never say '3pm' β€” always say '3pm ET' or '3pm London time'. This single habit eliminates most scheduling errors.
πŸ“…
Use UTC for recurring meetings
For teams spanning DST and non-DST regions, anchor recurring meetings to UTC. 'Every Monday at 14:00 UTC' is unambiguous year-round.
πŸ”„
Watch DST transition weeks
During the 2–3 weeks when some regions have changed clocks but others haven't, verify the actual offset before each meeting.
βš–οΈ
Rotate the burden
For teams with no good overlap, rotate the inconvenient time slot. Don't make the same team always join at 6am or 9pm.
πŸŒ…
Prefer morning for East-West calls
For New York–Tokyo calls, early morning New York time (8–9am ET) is late afternoon Tokyo (9–10pm JST) β€” more tolerable than the reverse.
πŸ“§
Async-first for large time gaps
When overlap is less than 2 hours, consider async communication (recorded video, detailed written briefs) instead of forcing a live call.

The "Golden Hours" for Global Calls

Best UTC Windows for Multi-Region Calls

If you need to schedule a call that works for multiple regions simultaneously, the following windows are the closest to universally workable:

UTC WindowNew YorkLondonDubaiSingaporeSydney
07:00–09:002–4am βœ—7–9am βœ“11am–1pm βœ“3–5pm βœ“5–7pm βœ“
08:00–10:003–5am βœ—8–10am βœ“12–2pm βœ“4–6pm βœ“6–8pm βœ“
13:00–15:008–10am βœ“1–3pm βœ“5–7pm βœ“9–11pm βœ—11pm–1am βœ—
14:00–16:009–11am βœ“2–4pm βœ“6–8pm βœ“10pm–12am βœ—12–2am βœ—

βœ“ = business hours  |  βœ— = outside business hours  |  Times shown in winter (standard time)

Tools for Cross-Timezone Scheduling

Several tools make cross-timezone scheduling significantly easier:

  • WhatTimeIsIt.blog Timezone Converter: Convert any time between any two cities with live DST awareness.
  • WhatTimeIsIt.blog City Compare: See two cities' times side by side with full timezone and weather context.
  • World Time Buddy: Visual overlap planner for up to four cities simultaneously.
  • Calendly / Cal.com: Scheduling links that automatically convert to each attendee's local time zone.
  • Google Calendar: Displays events in local time and supports multiple time zone display in the day/week view.

Check Current Times

Before scheduling your next international call, check the current local time in each city:

Sources & References

  1. Harvard Business Review: Managing Across Time Zones
  2. Buffer: State of Remote Work
  3. IANA Time Zone Database
  4. WhatTimeIsIt.blog City Data (92 cities)

Editorial Standards

All articles on WhatTimeIsIt.blog are written by our editorial team of time zone researchers and data analysts. We use primary data sources including the IANA Time Zone Database, government meteorological agencies, and our proprietary dataset of 92 cities. Articles are fact-checked before publication and reviewed quarterly for accuracy. If you find an error, please contact us.

Explore Live City Clocks

More Articles