How to Schedule Meetings Across Time Zones (2026 Guide)

Why Time Zone Meetings Go Wrong

You send a calendar invite for "10 AM Thursday." Half the team shows up at 10 AM their time. The other half is still asleep. Sound familiar?

Time zone confusion costs global teams an estimated 2-3 hours per week per person in missed meetings, rescheduling, and follow-up emails. The root causes are always the same:

• Ambiguous invites. "10 AM" without specifying whose 10 AM.
• DST surprises. The time difference changed since the recurring meeting was set up.
• Assumption bias. "Everyone knows we use New York time" -- no, they don't.
• Unfair scheduling. The same person always takes the meeting at 6 AM or 10 PM.

The single most impactful thing you can do: always specify the time zone in every meeting invite. Every single time. No exceptions.

Time Zone Etiquette Basics

Before we get into the mechanics, let's cover the human side:

1. Rotate the Pain

If your team spans New York, London, and Singapore, don't always schedule at 9 AM New York time (which is 10 PM Singapore). Rotate meeting times so the inconvenience is shared.

2. Default to the Majority

If 8 of 10 attendees are in European time zones, default to European-friendly times. The two outliers can adjust (or join asynchronously).

3. Record Everything

For meetings where someone will inevitably be at an awkward hour, record it. This isn't just courtesy -- it's essential for async-first teams.

4. Respect "No-Go" Hours

Before 7 AM and after 10 PM in someone's local time should be reserved for true emergencies. If you're regularly scheduling outside this window for the same person, something is wrong with the process.

Finding the Overlap Window

The key concept is the overlap window -- the range of hours that fall within business hours for all participants.

Standard business hours are generally 9 AM to 5 PM local time. Here's how the math works for common combinations:

Common Scenarios (With Solutions)

Scenario 1: US + Europe (The Easy One)

Participants: New York, Chicago, London, Berlin

Best window: 10:00 AM – 12:00 PM Eastern / 3:00 PM – 5:00 PM UK / 4:00 PM – 6:00 PM Central Europe

Why it works: Morning for the US, late afternoon for Europe. Nobody is eating dinner or waking up.

Scenario 2: US + Asia (The Tough One)

Participants: San Francisco, New York, Tokyo, Bangalore

Best window: 5:00 PM – 6:00 PM Pacific / 8:00 PM – 9:00 PM Eastern / 9:00 AM – 10:00 AM Tokyo / 6:30 AM – 7:30 AM Bangalore

Why it's hard: Someone is always at the edge. The US West Coast person is leaving the office, the Eastern person is eating dinner, and the Bangalore person is waking up.

Better approach: Split into two meetings. US + India at one time, US + Japan at another. Share notes between groups.

Scenario 3: The All-Hands (5+ Time Zones)

Participants: New York, London, Dubai, Mumbai, Singapore, Sydney

Reality check: There is no good time. The overlap is essentially zero.

Solution: Rotate between two time slots. Week A: morning US / afternoon Europe / evening India. Week B: evening US / morning Asia-Pacific / afternoon Australia. Record both.

Use a Meeting Planner Tool

Doing this math in your head is error-prone. Our Meeting Planner tool lets you:

• Add multiple cities and see their business hours on a single timeline
• Instantly identify the overlap window
• Account for DST automatically
• Share the result with your team

Here's how to use it:

1. Go to the Meeting Planner
2. Add each participant's city
3. The tool highlights the overlapping hours in green
4. Pick a time within the green zone
5. Share the link or screenshot with your team

Writing Better Calendar Invites

The invite itself is where most people fail. Here's the right way:

❌ Bad Invite

Team Sync
Thursday, June 19
10:00 AM - 11:00 AM

✅ Good Invite

Team Sync (Global)
Thursday, June 19
10:00 AM - 11:00 AM Eastern Time (New York)
3:00 PM - 4:00 PM UK Time (London)
11:00 PM - 12:00 AM Japan Time (Tokyo, June 20)

🌐 Time zone converter: worldtimessync.com/#converter

Key elements of a good invite:

• Primary time zone clearly labeled
• Local times for each participant listed in the description
• Date clarification when the meeting crosses midnight ("June 20" for Tokyo)
• Link to a converter so people can double-check

Frequently Asked Questions

What's the best time for a US-Europe meeting?

10:00 AM – 12:00 PM Eastern (3:00 PM – 5:00 PM UK / 4:00 PM – 6:00 PM Central Europe). This is the sweet spot where both sides are in business hours.

How do I handle DST changes for recurring meetings?

Set your recurring meeting in a specific time zone (e.g., "10:00 AM America/New_York"), not in UTC. Calendar tools like Google Calendar and Outlook will automatically adjust when DST changes. But always double-check during the 2-week US-EU DST gap in March and October.

Is there a "universal" meeting time?

No. But 1:00 PM UTC (8:00 AM New York, 1:00 PM London, 6:30 PM Mumbai, 9:00 PM Singapore, 11:00 PM Sydney) is the most commonly used compromise for global all-hands. It's early morning in the US, afternoon in Europe, and evening in Asia.

How do I politely decline an inconvenient meeting time?

Suggest an alternative: "I'd love to join, but 6 AM is tough for me. Would 8 AM work for the group, or could I review the recording?" Most organizers appreciate the honesty and the alternative.

Should I use UTC for all team communication?

UTC is great for engineering teams and technical contexts. For general business communication, use the time zone of the meeting organizer and list conversions for others. UTC adds a mental step for most people.