Scheduling a meeting with colleagues in New York, London, and Singapore sounds simple — until you realize one person's 9 AM is another's midnight. With 40% of knowledge workers now in fully distributed teams, cross-timezone scheduling has become a daily challenge. This guide walks you through the practical steps to find meeting windows that work, handle daylight saving time traps, and keep remote teams connected without burning anyone out.
Advertisement
Why Cross-Timezone Scheduling Is Hard
Common Pitfalls
- Forgetting DST changes (2–4 weeks/year, different dates per country)
- Confusing UTC offsets ("GMT+5:30" is India, not just "+5")
- Half-hour and 45-minute offset zones (India, Iran, Nepal, Australia)
- Always scheduling in the host's preferred time, burning out other attendees
- Not accounting for Friday afternoon = early Saturday in Asia-Pacific
The True Cost of Bad Scheduling
- Missed meetings due to timezone miscalculation
- Attendee burnout from repeated early morning or late evening calls
- Reduced participation from teams in "unfavorable" time slots
- Lost trust and collaboration in distributed teams
- Productivity loss from rescheduling and confusion
✨ Find Meeting Times Instantly — Two Free Tools
Use our free schedulers to find overlapping working hours across any number of time zones with full DST support.
Advertisement
Step-by-Step: Finding the Best Meeting Time
Step 1: List All Participants' Time Zones
Don't assume — confirm the actual time zone for each person, including whether DST is currently in effect. The same country can observe different offsets at different times of year:
US Eastern: UTC-5 (EST, winter) / UTC-4 (EDT, summer)
UK London: UTC+0 (GMT, winter) / UTC+1 (BST, summer)
India: UTC+5:30 (no DST)
Singapore: UTC+8 (no DST)
Australia Eastern: UTC+10 (AEST) / UTC+11 (AEDT, summer)Step 2: Define Working Hours for Each Person
The default 9–5 assumption is often wrong. Ask each participant their actual available window. Remote workers in particular may have flexible hours — some may start at 7 AM, others prefer 10–7.
Step 3: Find the Overlap Window
This is where a calculator saves you from mental arithmetic. Using the Working Hours Overlap tool:
- Add each participant with their time zone
- Set their working hours (start and end time in their local timezone)
- Select the target date (important for DST-accurate results)
- The tool shows all windows where everyone is simultaneously available
- Copy a shareable link to send the schedule to your team
Example: NYC + London + Singapore
Working hours: all 9:00–17:00 local
- NYC (EST, UTC-5): 9:00–17:00 = 14:00–22:00 UTC
- London (GMT, UTC+0): 9:00–17:00 = 09:00–17:00 UTC
- Singapore (UTC+8): 9:00–17:00 = 01:00–09:00 UTC
- ❌ No overlap! A compromise call at 14:00 UTC means 14:00 London, 09:00 NYC (early but OK), 22:00 Singapore (after hours)
Step 4: Propose a Fair Compromise
When no perfect overlap exists, rotate the inconvenience. Keep a record of who took the early/late call and alternate over time. This prevents the same team from bearing the scheduling burden every week.
Daylight Saving Time: The Hidden Trap
DST changes happen on different dates in different countries, meaning the offset between two cities can shift by 1–2 hours for 2–4 weeks per year. In 2026:
| Region | DST Starts | DST Ends | Offset Change |
|---|---|---|---|
| USA (most states) | Mar 8, 2026 | Nov 1, 2026 | UTC-5 → UTC-4 (EST → EDT) |
| UK & Ireland | Mar 29, 2026 | Oct 25, 2026 | UTC+0 → UTC+1 (GMT → BST) |
| Europe (most) | Mar 29, 2026 | Oct 25, 2026 | UTC+1 → UTC+2 (CET → CEST) |
| Australia (NSW/VIC) | Oct 4, 2026 | Apr 5, 2026 | UTC+10 → UTC+11 (AEST → AEDT) |
| India, China, Japan | No DST | — | Fixed offset year-round |
Tip: Between March 29 and April 5, 2026, the USA has already switched to EDT (+4h) but Australia hasn't ended AEDT yet. During this window, the Sydney–New York gap is temporarily different from the rest of the year. Always use a DST-aware tool when scheduling a meeting near these transition dates.
Best Practices for Global Teams
Always Specify UTC in Invites
Include the UTC time in calendar invites (e.g., "3 PM UTC / 10 AM EST / 4 PM CET"). This eliminates ambiguity when recipients are in different DST states.
Use Asynchronous Alternatives
Not every discussion needs a live meeting. Loom videos, shared docs, and async standup tools can replace many cross-timezone meetings entirely.
Establish a "Golden Hour"
Teams with regular global calls benefit from a standing overlap window — a 1-hour block that works for everyone, reserved exclusively for cross-team sync.
Record All Meetings
When someone must attend outside their core hours, recording the meeting with a transcript lets them catch up asynchronously without being penalized.
Rotate the Inconvenience
Track who took the early or late call. If it's always Sydney taking the midnight call, rotate monthly so each team absorbs some of the burden.
Plan Around Overlap Windows
For recurring meetings, check the specific date — a recurring "Friday 3 PM EST" becomes a very different experience for APAC in summer vs winter.
Frequently Asked Questions
What is the best time to meet between US, Europe, and Asia?
There is no single answer — it depends on the specific cities. A New York + London + Singapore combination has no clean overlap during standard business hours. The most common compromise is 9:00 AM New York (14:00 UTC in winter) which lands at 14:00 London and 22:00 Singapore — manageable for Singapore if meetings are brief and infrequent. Use the overlap calculator to visualize the exact window for your specific cities and dates.
How do I send a calendar invite that shows the correct local time for everyone?
Google Calendar and Outlook automatically convert times to each recipient's local timezone when you create an event with the correct timezone set. Always set the event timezone to the organizer's local timezone, not UTC, to ensure automatic conversion works for DST.
What is the difference between the Working Hours Overlap and Meeting Time Calculator tools?
The Working Hours Overlap tool is focused on finding windows where multiple people's working hours intersect — great for initial planning. The Meeting Time Calculator converts a specific proposed time across many cities simultaneously, showing exactly what time it would be locally for each participant. Use both for thorough scheduling.