Table of Contents
Scheduling a meeting across time zones is a problem of inequity. There is no universally convenient time when your team spans more than one continent. Someone is always at the edge — early morning or late evening — while others are in the comfortable middle of their working day. The goal is not to find a time that works perfectly for everyone. It is to find the least-bad time that distributes inconvenience fairly, or to recognize when a meeting is not the right medium.
This guide covers the practical steps: using a meeting planner to find time zone overlap, the strategies for distributing inconvenience across team members, the common time zone combinations and their specific challenges, how to handle DST transitions, and when to use asynchronous communication instead.
Finding Time Zone Overlap: The First Step
Before proposing a time, visualize the working hours of all participants simultaneously. A meeting planner tool (or a world clock with working hours highlighting) shows a 24-hour grid with working hours highlighted for each zone. The overlap — where all highlighted blocks align — is your feasible meeting window.
Common team configurations and their overlap:
US East + West Coast: 3-hour overlap minimum (12pm–5pm ET / 9am–2pm PT). Very manageable — a standing meeting at noon ET / 9am PT is comfortable for both coasts.
US East + UK: During standard time: the overlap is roughly 2pm–5pm ET / 7pm–10pm GMT — late in the UK. During summer (both on DST): the overlap is better — 2pm–5pm ET / 7pm–10pm BST, still late. The most common compromise is 9am ET / 2pm UK — workable for both, with the UK finishing at 5pm and the US starting at 9am.
US East + Central Europe: Similar to US + UK but with an additional 1–2 hours. 9am ET / 3pm CET is the standard compromise.
US West + India (8.5–9.5 hours apart): Very limited overlap. 6am PT / 7:30pm IST is the most common. Both extremes are at the edge of reasonable working hours.
UK + Singapore (7–8 hours apart): 9am SGT / 1am–2am UK (no good time). The least-bad option is early Singapore / early-morning UK: 8am SGT / midnight UK, or end-of-day UK / end-of-day SGT: 6pm UK / 1am SGT. Neither is good; rotating is more equitable.
Find overlap with the meeting planner— Add up to 8 time zones and see working-hour overlapWhen There Is No Overlap: The Rotation Strategy
For team configurations where no overlap exists within reasonable working hours — common with Asia-Pacific and Americas combinations — the rotation strategy is the most equitable solution.
How rotation works: Instead of always placing the meeting at a time convenient for the majority (which permanently disadvantages the minority), rotate the meeting time so that the inconvenience is shared.
Example for a US East / Singapore combination:
- Week A: 9am ET / 10pm Singapore (inconvenient for Singapore)
- Week B: 8pm ET / 9am Singapore (inconvenient for US East)
- Alternate each week.
Both parties take turns with the inconvenient time. Neither is permanently disadvantaged.
Documentation requirements for rotation: When rotating meeting times, team members need to know in advance which weeks require early or late participation. Add the schedule to the team calendar in advance. Never surprise someone with an early-morning or late-evening meeting without prior notice.
Bi-weekly over weekly: If the meeting frequency is high and the time zone gap is extreme, consider moving to bi-weekly meetings and using asynchronous communication for the other weeks. This reduces the number of inconvenient times overall.
Handling DST Transitions in Recurring Meetings
DST transitions are the source of unexpected meeting time changes in distributed teams. When one team's region observes a DST transition and another's does not, or when their transition dates differ, the effective overlap shifts.
Common problematic transitions:
US–UK gap shift (2–3 week window each spring): The US springs forward in mid-March; the EU springs forward in late March. In the window between these dates, the US is on EDT (UTC-4) but the UK is still on GMT (UTC+0) — the gap is 4 hours instead of the usual 5. A standing meeting at "9am ET / 2pm UK" becomes "9am ET / 1pm UK" in this window, then shifts back to 2pm when the UK transitions.
Australia–North America gap shift (October/November): Australia transitions in early October (southern hemisphere spring). North America transitions in early November. During this ~4-week gap, the gap between US and Australian time zones is different than usual.
Practical checklist for recurring meetings:
1. Set a calendar reminder 1 week before each DST transition in any participant's region
2. Verify the meeting time in all zones for the first occurrence after the transition
3. Update calendar invites if the local times have shifted
4. Communicate changes to participants at least one week in advance
When to Use Async Instead of a Meeting
The best solution to a difficult time zone meeting is often to avoid the meeting entirely.
Questions to ask before scheduling a meeting:
1. Is a decision required? If information can be shared and each person can respond independently without needing real-time discussion, an email or a Loom video update is faster and more accessible than a meeting.
2. Is the group larger than 5? Large groups rarely make decisions in meetings — they hear presentations and ask questions. For more than 5 people across time zones, a recorded video with a Q&A thread is more inclusive and preserves the content for later reference.
3. Is this the same meeting every week? Recurring status update meetings are the most commonly questioned meeting format. If the status update could be a written summary in Slack or Notion, the meeting is a ritual, not a requirement.
4. Are some participants always passive? If two people are always talking and four people are always listening, the meeting is a presentation. Record it. The listeners can watch at their own time.
Tools for async communication in distributed teams:
- Loom / Descript: Record screen + face videos for updates, walkthroughs, and presentations
- Slack / Teams: Asynchronous text communication with threads
- Notion / Confluence / Linear: Shared documentation and decision logs
- Loom Docs / Google Docs with comments: Collaborative async review
Best Practices for Cross-Timezone Meeting Hygiene
Once you have a meeting time, how the meeting is run matters as much as when it is scheduled.
Specify time zones explicitly in invites: Write "10am ET / 3pm GMT / 11:30pm IST" in the meeting invitation, not just "10am." This lets everyone double-check their calendar shows the right time. Use the Meeting Planner to generate these times and paste them into the invite description.
Record all cross-timezone meetings: Someone will be at an unusual hour and may struggle to be at their best. Recording lets them review key decisions afterward. It also serves as documentation for team members who join later.
Publish an agenda in advance: Cross-timezone participants who are in an early morning or late evening slot deserve to know what the meeting will cover before attending. An agenda lets them decide whether their attendance is critical, and prepare questions.
Start and end on time — always: For participants who have adjusted their schedule to attend at an unusual hour, running over time is particularly disrespectful. If the meeting runs over, cut content, not time.
Rotate facilitation: Have team members in different time zones take turns facilitating the meeting. This distributes the engagement and ensures that participants in the "inconvenient" slot have agency in the meeting rather than being passive late-night attendees.
Frequently Asked Questions
What is the best time for a meeting between New York and London?
How do I find the best meeting time for a US, European, and Indian team?
How do I communicate a meeting time unambiguously to an international team?
Should we have a fixed meeting time or rotate for global teams?
What tools are best for scheduling across time zones?
Summary
There is no universally good time for a global team meeting when the team spans more than 12 hours of time zone difference. The practical options are: find the least-bad overlap within reasonable working hours, rotate the inconvenience fairly, or replace the meeting with async communication that does not require real-time presence.
The tools — meeting planners, world clocks, time zone converters — make the first step (finding overlap) mechanical. The harder decisions are organizational: who rotates, how often, and when to admit that a recurring meeting would be better replaced by a written update and a thread for questions.
The best distributed teams are explicit about these trade-offs. They document their rotation schedules, record their meetings, write their decisions down, and use synchronous time sparingly for the work that actually requires it.