How to Schedule International Meetings Without the Confusion
Scheduling a meeting across time zones is one of the most common remote-work headaches. This guide covers overlap windows, naming conventions, and the right tools to eliminate the confusion.
Scheduling a meeting when everyone is in the same building is trivial. Scheduling one when participants are spread across New York, London, and Singapore is a genuine puzzle — someone is always at an awkward hour, DST shifts the overlap windows without warning, and a single ambiguous invite ("3 PM EST") causes someone to show up an hour late or not at all.
This guide covers the practical mechanics: how to find the least-bad overlap windows for common zone combinations, how to write an invite that cannot be misread, and what to do when there is no good time at all.
The Core Problem: No Universal "Daytime"
A standard workday runs roughly 09:00–18:00 local time. The challenge is that these windows overlap differently depending on the time zone pair. Europe and the US East Coast share about 5 hours of overlap on a good day (roughly 15:00–20:00 CET / 09:00–14:00 ET). The US West Coast and East Asia may share no overlap at all during conventional business hours.
Common Overlap Windows
| Zone Pair | Overlap Window (local times) | Notes |
|---|---|---|
| New York ↔ London | NY: 9:00 AM–1:00 PM / LON: 2:00 PM–6:00 PM | Shrinks by 1 hour during US/EU DST transition gaps in spring |
| New York ↔ Central Europe | NY: 9:00 AM–12:00 PM / CET: 3:00 PM–6:00 PM | Only 3 hours; afternoons NY are evenings Europe |
| London ↔ Mumbai | LON: 9:00 AM–1:30 PM / MUM: 2:30 PM–7:00 PM | India is UTC+5:30 — the half-hour offset trips people up |
| New York ↔ Singapore | NY: 8:00 AM–9:00 AM / SGP: 9:00 PM–10:00 PM | Near-zero overlap; someone must start early or end late |
| San Francisco ↔ London | SF: 9:00 AM–10:00 AM / LON: 5:00 PM–6:00 PM | Very narrow; early SF mornings and late LON afternoons only |
| New York ↔ Sydney | Reversed seasons complicate this further | Check a live tool; the window shifts dramatically with DST |
| London ↔ Singapore | LON: 9:00 AM–12:00 PM / SGP: 5:00 PM–8:00 PM | 8-hour gap means mornings in London, evenings in Singapore |
The "Pain Rotation" Strategy
When no good overlap exists, the fairest approach is to rotate the inconvenient slot. If a recurring meeting always requires someone to show up at 7 AM or 9 PM, rotate that burden across the team quarterly. Document the rotation explicitly so no one feels unfairly burdened. Some teams explicitly compensate the off-hours participant — a later start the next morning, for example.
Writing an Invite That Cannot Be Misread
- Always include the IANA time zone identifier, not just the abbreviation. Write "3:00 PM America/New_York" not "3:00 PM EST." EST is ambiguous — it means UTC-5 in the US but UTC+10 in Australia (AEST), and is often confused with EDT (UTC-4) during summer.
- Include the UTC equivalent. "3:00 PM ET (20:00 UTC)" gives every attendee an unambiguous anchor they can convert from.
- Use calendar apps that respect IANA zones. Google Calendar, Outlook, and Apple Calendar all accept IANA time zone names and will display the correct local time to each attendee automatically.
- For asynchronous teams using Slack or email, include a link to a time zone converter pre-set to your meeting time — it removes the mental math.
- When writing dates, use the ISO 8601 format (2026-04-22) or spell out the month name (22 April 2026). Numeric formats like 04/22 are ambiguous — Americans read it as April 22, Europeans as 4 February.
Handling DST Transition Weeks
In spring, the US and EU switch to summer time on different weekends — typically the US changes 2–3 weeks before Europe. During this gap, the usual US–Europe overlap shrinks by one hour. If you have a recurring meeting series, expect to receive a confused email from at least one European colleague on the Monday after the US transition asking why the meeting appears to have moved.
The safest calendar hygiene: always create recurring events in a named IANA time zone, never as a fixed UTC offset. A meeting set to "2:00 PM America/New_York" will automatically adjust for DST and display correctly to all attendees year-round. A meeting set to "2:00 PM UTC-5" will silently drift off by an hour the moment New York switches to EDT.
Find the best meeting time for any combination of cities and see everyone's local hours side by side.
Meeting Planner →Frequently asked questions
- What does "EST" mean vs "ET"?
- EST (Eastern Standard Time) specifically means UTC-5, used by the US East Coast in winter. EDT (Eastern Daylight Time) means UTC-4, used in summer. "ET" (Eastern Time) is the colloquial term that covers both, and is ambiguous about the exact offset. For an invite, write the full IANA name "America/New_York" to be unambiguous, or include the UTC equivalent.
- What is the best time to schedule a meeting between the US and India?
- India (IST, UTC+5:30) is 10.5 hours ahead of US Eastern Time in winter and 9.5 hours ahead in summer. The best overlap window is 8:00–9:30 AM ET (6:30–8:00 PM IST) — early morning on the US side and late afternoon/early evening in India. There is no window that falls comfortably within both standard working hours.
- How do I share a meeting time without ambiguity?
- Include three things in your invite: the local time in your zone, the IANA zone identifier (e.g., "America/Chicago"), and the UTC equivalent (e.g., "16:00 UTC"). Better yet, use a tool like the Meeting Planner to generate a link showing the time in every attendee's zone.
We build practical, free time and date tools at epochcalc.com — every calculation runs in your browser using IANA tzdb via Luxon, so DST and zone math are correct by construction.