Best Time for a Global Meeting
Last reviewed: January 2026
Find the best meeting time across up to 3 time zones with business hours overlap check. This calculator runs entirely in your browser — your data stays private, and no account is required.
Finding meeting times that work across time zones requires identifying overlapping business hours. The golden rule is to keep meetings within each participant reasonable working hours (8 AM - 7 PM local time) — scheduling a 6 AM or 10 PM call creates resentment and reduces participation quality.[1] For teams spanning more than 8 time zones, synchronous meetings become impractical and async communication (recorded updates, collaborative documents, threaded discussions) should be the default, with live meetings reserved for critical decisions and relationship building.[2] When recurring meetings must cross zones, rotate the inconvenient time slot so the burden is shared equally among participants rather than always falling on one region.[3] Use the Time Zone Calculator to convert specific times between zones.
| Cities | Overlap Window | Best Slot |
|---|---|---|
| NYC + London | 9 AM–12 PM ET | 10 AM ET / 3 PM GMT |
| NYC + LA | 12 PM–5 PM ET | 1 PM ET / 10 AM PT |
| London + Tokyo | 8–9 AM GMT | 8:30 AM GMT / 5:30 PM JST |
| NYC + Sydney | 7–9 PM ET | 8 PM ET / 10 AM AEST |
| All three (US/EU/Asia) | Very limited | Rotate or async |
Coordinating meetings across multiple time zones is one of the most common logistical challenges in modern business. The world spans 24 primary time zones, each nominally 15° of longitude wide, but political boundaries create numerous exceptions. China, despite spanning five geographic time zones, uses a single time zone (UTC+8) nationwide. India uses UTC+5:30, one of several zones at half-hour offsets. Nepal uses UTC+5:45, and the Chatham Islands of New Zealand use UTC+12:45. These non-standard offsets complicate scheduling and explain why "just subtract the hours" is an oversimplification that fails for many international combinations.
Finding a mutually convenient time between participants in, say, New York (UTC−5/−4), London (UTC+0/+1), and Tokyo (UTC+9) requires identifying overlapping business hours. New York's 9 AM–5 PM maps to London's 2 PM–10 PM and Tokyo's 11 PM–7 AM. The only overlap of all three during standard business hours is roughly New York 8–9 AM / London 1–2 PM / Tokyo 10–11 PM — a single hour that still requires one participant to join late at night. With participants in four or more distant time zones, finding any overlap of reasonable hours may be impossible, necessitating rotation of meeting times so the inconvenience is shared rather than borne repeatedly by the same individuals.
Rotating meeting times is the fairest approach for regularly scheduled calls involving distant time zones. If a weekly meeting alternates between two times — one convenient for the Americas and Europe, another convenient for Europe and Asia-Pacific — each group takes an occasional off-hours call rather than one group always suffering. Recording meetings and sharing agendas and notes asynchronously ensures that participants who cannot attend live can still contribute. Many teams have shifted toward asynchronous communication (documented decisions, recorded updates, shared project boards) supplemented by synchronous meetings only when real-time discussion is essential.
Calendar tools that display multiple time zones simultaneously prevent conversion errors, which are especially common around daylight saving time transitions. The US and EU change clocks on different dates (March and November in the US; March and October in the EU), creating periods of 2-3 weeks when the time difference between, say, New York and London is 4 hours instead of the usual 5. Australia transitions in October and April (opposite season from the Northern Hemisphere), and some jurisdictions — Arizona, Hawaii, most of Saskatchewan, and Iceland — do not observe daylight saving time at all. A meeting that works year-round must account for all these shifts, which is why automated scheduling tools that access current time zone databases (like the IANA Time Zone Database) are far more reliable than manual calculations.
Research consistently shows that meeting productivity declines sharply after 30-45 minutes for working sessions and after 60-90 minutes for collaborative workshops. Parkinson's Law of Triviality suggests that meetings expand to fill the time allotted, meaning a 60-minute slot will rarely finish early even when the content could be covered in 30 minutes. Defaulting to 25-minute or 50-minute meetings instead of 30 or 60 creates buffer time between back-to-back calls and subtly pressures participants to stay focused. Standing meetings (where all participants remain on their feet) naturally limit duration and are correlated with faster decision-making in organizational research. For cross-timezone calls, shorter meetings reduce the impact on participants joining outside normal hours.
The mathematical problem of finding meeting times across multiple participants is a constraint satisfaction problem — identifying time slots that satisfy all participants' availability constraints, timezone requirements, and preference orderings. For two participants, this is trivial (overlay two calendars). For groups of 8-12 in multiple time zones, the solution space shrinks rapidly. Doodle-style polling tools crowdsource availability but require manual input from every participant. Calendar-integrated tools that read free/busy data (like Google Calendar's "Find a Time" or Microsoft Outlook's Scheduling Assistant) automate the process but require all participants to use the same calendar system or share interoperable free/busy data.
When no single time works for all participants, the optimal strategy depends on the meeting's purpose. For information-sharing meetings, recording and distributing asynchronously may be better than forcing an inconvenient time. For decision-making meetings, identifying the minimum quorum of essential decision-makers and scheduling for their availability — while recording for others — produces better outcomes than either delaying the decision or holding a poorly-attended meeting at an unpopular time. For brainstorming or creative sessions, synchronous participation is most valuable, justifying occasional off-hours meetings with the understanding that the burden rotates fairly.
See also: Time Zone Converter · Business Days Calculator · Countdown Timer
→ US East Coast to Western Europe has a 5–6 hour overlap during business hours. ET to CET is a 6-hour difference. Meetings between 9 AM ET (3 PM CET) and 12 PM ET (6 PM CET) work for both sides during standard hours. Morning ET / afternoon Europe is the most common pattern for transatlantic teams.
→ US to Asia-Pacific has almost no business-hour overlap. PT to JST (Japan) is a 17-hour difference. When it's 9 AM in San Francisco, it's 2 AM in Tokyo. The only options are very early morning US (7 AM PT = 11 PM JST) or very late evening Asia. Rotating the inconvenient time slot between teams is the fairest approach.
→ Daylight saving time shifts overlaps twice a year. The US, Europe, and Australia change clocks on different dates. During the 2–3 weeks when one region has changed but another hasn't, your usual meeting time shifts by an hour. Always confirm the time in each zone near DST transitions. Track shifts with our Time Zone Converter.
→ Recording meetings and sharing notes is essential for async-first global teams. If overlap is too limited for everyone to attend live, record the meeting, share detailed notes, and give absent team members a structured way to provide input asynchronously. A 30-minute recording is better than a 2 AM meeting that no one remembers clearly. See our Meeting Cost Calculator.
See also: Meeting Cost Calculator · Time Zone Converter · World Clock · Event Time Announcer