Finding a meeting time that works across multiple time zones is one of the most practically frustrating aspects of global work. And it's not just arithmetic — it's arithmetic with moving parts, since Daylight Saving Time shifts the offsets between zones several times a year. The team member in Sydney who was 16 hours ahead of New York in January is only 15 hours ahead in March. The London colleague who was 5 hours ahead of New York in February is only 4 hours ahead in the two-week gap before the UK changes its clocks in late March.
Finding Overlap Windows
The practical tool for finding meeting windows is identifying the "working hours overlap" — the range of time when all participants would be in acceptable working hours simultaneously. Working hours vary by individual, company culture, and country, but a reasonable starting assumption is 8 AM to 6 PM local time.
For US East Coast (EST/EDT) and Western Europe: there's a comfortable 4-6 hour overlap window in the morning, making 10 AM to noon Eastern / 3-5 PM CET an ideal regular meeting time. Both parties are solidly in business hours. For US West Coast and Asia: the windows are harder. San Francisco at 9 AM (UTC-8 in winter) overlaps with Tokyo at 2 AM (UTC+9) — no overlap within business hours at all. The best available option for SF-Tokyo meetings is typically late afternoon SF / early morning Tokyo, or early morning SF / end-of-day Tokyo.
For teams spanning three continents (Americas + Europe + Asia), there typically is no single time slot that falls in business hours for all three regions simultaneously. The US East Coast is the geographic pivot: it overlaps with European mornings and Asian evenings/early mornings, but never both simultaneously in business hours. Teams in this situation often hold separate regional meetings rather than attempting all-hands sessions.
International Meeting Etiquette
When meetings span inconvenient time zones, communication about the difficulty matters. Acknowledging that someone is joining at 7:00 AM or 10:00 PM for a meeting that's convenient for everyone else — and expressing appreciation — builds team goodwill. Rotating who takes the inconvenient slot for recurring meetings demonstrates fairness.
Recording important meetings is especially valuable for global teams because someone is almost always in an inconvenient time zone. Participants who can't comfortably attend at 5 AM can catch up on the recording on their own schedule. For decision-making purposes, distributing proposals in writing before the meeting and accepting asynchronous input allows participation from people who can't attend live without disadvantaging them.
Meeting length considerations change with time zone span. A 90-minute call that starts at 7 AM for your team in Singapore is less burdensome than a 3-hour working session. Keeping cross-timezone meetings focused and shorter (under 60 minutes where possible) reduces the burden on participants in disadvantaged time zones and typically produces better outcomes than sprawling multi-hour calls where international participants tune out after hour one.
Building a Time Zone Meeting Framework
The most reliable approach for cross-time-zone scheduling is converting all times to UTC first, then translating to each participant's local time. UTC doesn't change with seasons — it's the fixed reference against which everything else is measured. If your proposed meeting time is 3:00 PM UTC, you then simply apply each participant's UTC offset at the time of the meeting.
A meeting at 15:00 UTC on a November date (US in standard time, UK in standard time): New York (EST, UTC-5) = 10:00 AM, London (GMT, UTC+0) = 3:00 PM, Berlin (CET, UTC+1) = 4:00 PM, Singapore (SGT, UTC+8) = 11:00 PM, Sydney (AEDT, UTC+11) = 2:00 AM next day. That 15:00 UTC time slot gets someone in an uncomfortable position regardless of which direction you push it.
The fundamental reality for teams spanning East Asia and the Americas: there is no time slot that falls within business hours (roughly 9 AM to 6 PM) for all participants simultaneously. Teams working across this span must accept rotating inconvenience — sometimes alternating who takes the early or late call, or adopting a rotating schedule that distributes the burden equitably over time.
Tools for Cross-Timezone Scheduling
World Time Buddy is one of the most effective dedicated tools for visualizing time zone overlaps. It displays multiple time zones as horizontal bars color-coded by working hours, allowing you to drag a time indicator and instantly see what time it is in each zone. The visual interface makes identifying overlap windows much faster than doing offset arithmetic.
Calendly and similar scheduling automation tools handle time zone conversion automatically when configured correctly. When someone books a meeting through Calendly, available time slots display in the booker's local time zone. The meeting invitation then appears in each participant's calendar at their correct local time. This eliminates the "what time is that in my time zone?" confusion from scheduling emails.
When scheduling manually via email, explicitly specify the time zone in your meeting request. "3:00 PM on Thursday" is ambiguous. "3:00 PM Eastern Time (UTC-5) on Thursday, March 20" is unambiguous. Include the UTC offset alongside the time zone abbreviation because abbreviations can conflict — CST refers to Central Standard Time in the US (UTC-6) and China Standard Time (UTC+8) in different contexts.
Related Calculators
Standard Time vs. Daylight Saving Time Complications
Daylight Saving Time is a genuine source of scheduling errors because transitions happen on different dates in different countries and regions. The US typically changes on the second Sunday of March (spring forward) and first Sunday of November (fall back). Most of Europe changes on the last Sunday of March and last Sunday of October. Australia's DST (in states that observe it) changes in October and April — opposite hemisphere timing.
This creates several annual windows when the time difference between zones changes unexpectedly. US spring forward (second Sunday of March) happens before European spring forward (last Sunday of March). For roughly 2 weeks in March, New York is UTC-4 (already in EDT) while London is still UTC+0 (in GMT). The usual 5-hour gap between New York and London becomes 4 hours. An automatic calendar system that doesn't account for this will show the wrong time for recurring meetings during this window.
Consider a recurring weekly Monday 9:00 AM New York / 2:00 PM London meeting. In winter: correct. In the two-week gap in March when New York has changed but London hasn't: the meeting shows as 2:00 PM London but the New York clock says 9:00 AM, which is actually 1:00 PM UTC — meaning London would need to meet at 1:00 PM, not 2:00 PM, to be synchronized. Someone will arrive an hour late unless they check the actual UTC time.
DST-Resistant Meeting Scheduling Strategies
Scheduling recurring international meetings in UTC eliminates DST confusion entirely. A meeting "every Monday at 14:00 UTC" changes local times when clocks change, but the UTC time is constant and the calendar entry updates automatically if meeting software is properly configured. Participants need only know their current UTC offset (which changes with their clock change, not the other day's clock change) to calculate local time.
Some international teams adopt a reference time zone that doesn't observe DST for recurring meetings. UTC itself, GMT, or specific time zones that don't observe DST (like India Standard Time at UTC+5:30, which never changes) serve as stable anchors. Phoenix (Arizona) doesn't observe DST either, though using a city name creates confusion about whether other US time zones are currently aligned.
For one-off meetings with international attendees, sending calendar invitations using a standards-compliant calendar system (Google Calendar, Outlook with proper configuration) handles time zone conversion automatically. The invitation stores the meeting in UTC internally and displays it in each recipient's configured local time zone. The meeting moves on the local clock when DST changes, but participants see the correct updated local time.
