How do I schedule a meeting across 5 time zones?

Identify your overlap window by listing each participant working hours in their local time. Use a tool like the Best Meeting Time Calculator to score each hour based on how many people are within working hours.

What is a good overlap window for distributed teams?

A 2-3 hour overlap is generally sufficient for most teams. This allows one or two synchronous meetings per week while leaving time for focused work.

How does DST affect cross-time-zone scheduling?

DST changes the offset between cities twice a year. The US and Europe switch on different dates, creating a temporary offset shift. Always check the offset for the specific date of your meeting.

Scheduling Across Time Zones: A Practical Guide for Distributed Teams in 2026

If your team spans more than three time zones, you have probably felt the pain of scheduling. A 9 AM meeting in New York is 3 PM in Berlin and 10 PM in Tokyo. Someone is always inconvenienced. With the potential end of DST clock changes in the US and teams more distributed than ever, the problem is not going away.

This guide covers practical strategies for scheduling across time zones, from choosing the right meeting time to building a culture that does not burn out your remote team members.

The core problem: overlap windows

Every distributed team has an overlap window: the hours when all team members are working simultaneously. For a team spread across New York, London, and Tokyo, the overlap window might be as narrow as 1 hour (9 AM New York, 2 PM London, 10 PM Tokyo). For a team across New York, London, and San Francisco, the overlap is wider but still limited.

The first step is to identify your team's overlap window. List each team member's working hours in their local time, then find the intersection. If the overlap is less than 2 hours, you have a scheduling constraint that requires careful management.

New York (UTC-5/-4) and London (UTC+0/+1): 5-hour difference, overlap from 9 AM to 1 PM New York time
New York and Berlin (UTC+1/+2): 6-hour difference, overlap from 9 AM to 12 PM New York time
New York and Tokyo (UTC+9): 14-hour difference, almost no overlap during normal business hours
London and Sydney (UTC+10/+11): 10-11 hour difference, London morning equals Sydney evening
San Francisco and Berlin: 9-hour difference, SF morning equals Berlin afternoon

Strategy 1: Rotate the pain

If your team has a narrow overlap window, do not always make the same person take the inconvenient slot. Rotate meeting times so the burden is shared. One week, the New York team takes an early morning call. The next week, the Tokyo team takes an evening call. This prevents resentment from building up in one location.

A simple rotation schedule works like this: if you have a weekly team meeting, alternate between three time slots. Slot A is convenient for the Americas, Slot B for Europe, Slot C for Asia. Each region takes the inconvenient slot once every three weeks.

Track who took the last inconvenient slot. Without a system, the most accommodating team members end up always taking the bad times. Use a shared spreadsheet or your team's scheduling tool to keep it fair.

Strategy 2: Default to asynchronous

Not every meeting needs to be a meeting. Many discussions work better as asynchronous written updates. A daily standup can be a Slack thread. A project status check can be a shared document. Reserve synchronous meetings for discussions that genuinely require back-and-forth: brainstorming, conflict resolution, and complex decision-making.

The test is simple: if the meeting could be replaced by a document that everyone reads and comments on, it should be a document. You will get better input from people who have time to think, and you will free up the overlap window for meetings that actually need it.

Strategy 3: Record and share

When someone cannot attend a meeting due to time zone constraints, record it. Share the recording with a written summary and action items. This is not a replacement for attending, but it ensures that team members in incompatible time zones stay informed.

The key is the written summary. Nobody wants to watch a 45-minute recording at 11 PM. A 5-minute read with key decisions, action items, and links to relevant documents respects their time while keeping them in the loop.

Strategy 4: Use the right tools

A good scheduling tool shows multiple time zones side by side and highlights overlap windows. The Best Meeting Time Calculator on this site does exactly this: you select the time zones of all participants, and it scores each hour based on how many people are within working hours.

The Work Hours Overlap Visualizer takes this further by showing a heatmap of all 24 hours, so you can see the full picture of when team members are available. Use these tools before proposing a meeting time, not after.

Before scheduling, check the overlap window using the Best Meeting Time Calculator
For recurring meetings, use the Work Hours Overlap Visualizer to see if the chosen time stays in working hours after DST transitions
Always state meeting times in UTC or in each participant's local time. Never say '3 PM our time' without specifying which time zone 'our time' is.
Add time zone labels to your calendar invites. Google Calendar and Outlook both support this.

The DST complication

Daylight saving time makes scheduling harder because the offset between two cities changes twice a year. New York and London are 5 hours apart during standard time but only 4 hours apart during DST. And they do not switch on the same date.

The US switches to DST on the second Sunday of March. The EU switches on the last Sunday of March. For about two weeks in March, New York and London are only 4 hours apart instead of 5. Then in October/November, the reverse happens: the EU falls back first, creating a temporary 5-hour gap that becomes 4 hours again when the US falls back a week later.

If the US makes DST permanent in 2026, this problem gets simpler for US-based teams. The offset between US and European cities would be fixed year-round. But until then, always check the offset for the specific date of your meeting, not just the current offset.

Building a time zone-friendly culture

Tools and strategies only work if the team culture supports them. Here are practices that make distributed teams function better:

Set core hours, not strict hours. Define a 2-3 hour overlap window when everyone should be available, and let people flex the rest of their day around it.
Never schedule a recurring meeting outside someone's working hours without asking them first. What is convenient for you might be dinner time for them.
Be explicit about response time expectations. If someone is asleep when you send a message, they should not be expected to respond until their next workday.
Celebrate across time zones. If a team member in Tokyo hits a milestone, acknowledge it during their workday, not yours.
Track meeting burden. If one location consistently takes the inconvenient slots, rebalance.

A practical workflow

Here is a workflow that works for a team spread across 4 or more time zones:

Monday: asynchronous written updates from each region. No meeting.
Tuesday: one synchronous meeting during the overlap window. Rotate the time weekly so no region always takes the bad slot.
Wednesday: focused work day. No cross-region meetings.
Thursday: one synchronous meeting, different time from Tuesday if possible.
Friday: asynchronous wrap-up. Share wins, plan next week.

This gives you two synchronous touchpoints per week, which is enough for most teams. The asynchronous days respect time zone differences and give people focused work time.

Use the Time Zone Converter to check specific times across your team's locations, and the Best Meeting Time Calculator to find the optimal slot for your next cross-region meeting.