Scheduling Meetings Across Time Zones Without Losing Your Mind

The Overlap Problem

I've managed distributed teams for over a decade, and the single biggest source of frustration is always the same: finding a meeting time that doesn't wreck someone's day. A 9 AM call in New York is 2 PM in London — fine. But it's 10:30 PM in Mumbai and midnight in Singapore. Someone always gets the short end.

The math is brutal. There are only about 1-2 hours of overlap between all three major business regions (Americas, Europe, and Asia-Pacific) during reasonable working hours. And "reasonable" is doing a lot of heavy lifting in that sentence.

I ran into this firsthand managing a product team split between San Francisco, Berlin, and Bangalore. We tried a standing Monday sync at 9 AM Pacific. Great for us in California. Tolerable for Berlin at 6 PM. Miserable for Bangalore at 10:30 PM. We lasted three weeks before the Bangalore team — rightly — pushed back. That experience forced me to actually think systematically about this problem instead of just defaulting to whatever time suited headquarters.

The Golden Windows

Here's a realistic overlap chart for the three major business zones:

For US-Europe meetings, the sweet spot is 13:00–16:00 UTC — morning in America, afternoon in Europe. For Europe-Asia, shift earlier to 07:00–10:00 UTC. A true all-hands with all three regions? That's where it gets painful. Around 08:00–09:00 UTC is the least bad option — early morning in Europe, afternoon in Asia, but the middle of the night in the Americas.

One thing the table doesn't capture: India's half-hour offset (UTC+5:30) throws a wrench into otherwise clean calculations. When you're trying to align with both London and Mumbai, that 30-minute offset means your neat "top of the hour" meeting doesn't land at the top of the hour for IST. It's minor, but it trips people up constantly when setting recurring calendar events.

The DST Trap

Twice a year, daylight saving time turns your carefully planned meeting schedule into chaos. The US springs forward in mid-March, Europe follows two weeks later, and most of Asia doesn't observe DST at all. During those two weeks in March, the US-London offset shrinks from 5 hours to 4 hours, then snaps back to 5 when the UK adjusts. I've watched entire teams miss calls because nobody realized the relative offset had temporarily changed.

My advice: always set recurring meetings in UTC, and let calendar apps handle the local conversion. If you set a meeting at "9 AM Eastern," the UTC equivalent changes twice a year. If you set it at "14:00 UTC," it stays at 14:00 UTC regardless of what clocks are doing locally. Yes, that means it'll show as 9 AM ET in winter and 10 AM ET in summer — but at least the meeting is consistent, and everyone's calendar app will reflect the correct local time automatically.

Australia makes this even messier. Different Australian states change clocks on different dates than the US or Europe, and some states (like Queensland and Western Australia) don't observe DST at all. If you have team members in Sydney and Brisbane — cities only an hour apart by plane — they're in the same timezone for half the year and different timezones for the other half. Good luck explaining that in a recurring invite.

Rotation Fairness

Here's a rule I insist on: no single timezone should always take the bad slot. If your Asia team is joining at 10 PM every week, that's not collaboration — it's exploitation. Rotate meeting times monthly. One month it's early for the US team, next month it's late for Europe. Document the rotation so nobody feels singled out.

Some teams use a "follow the sun" rotation where the meeting time shifts by 8 hours each week. It works better than you'd think. The key is making the rotation visible — post it in your team's shared channel, put it in the calendar series description, reference it in every invite. People accept inconvenient times much more graciously when they can see that the burden is distributed evenly.

I also recommend being honest about which meetings actually need everyone live. Your weekly team standup? Maybe. The quarterly planning session? Definitely. The "quick sync" that could have been a Slack thread? Almost certainly not. Audit your recurring meetings and ask: would two separate sessions (one for US-Europe, one for Europe-Asia) work better than one painful all-hands? Often the answer is yes, with a shared async summary bridging the two.

Async-First Is the Real Answer

The best meeting across time zones is the one you don't have. I'm a firm believer in async-first culture for distributed teams. Record a 5-minute Loom instead of a 30-minute sync. Use shared docs with comment threads. Save synchronous meetings for decisions that genuinely need real-time debate.

When you do schedule a meeting, always — always — include the timezone in the calendar invite. "Tuesday at 2 PM" means nothing without a timezone. Use UTC or include multiple zones: "Tuesday 14:00 UTC / 9:00 AM ET / 2:00 PM GMT / 7:30 PM IST." Your future self will thank you.

A practical async workflow that's worked well for my teams: the project lead records a 5-minute video walkthrough of the agenda topics and posts it by end-of-day in their timezone. Each team member responds with written comments or a short video reply within their own working hours. If a decision can't be reached asynchronously, then you schedule a live call — but only for the specific unresolved item, not the whole agenda. This typically cuts synchronous meeting time by 60-70%.

Calendar Etiquette That Actually Matters

A few hard-won rules from years of cross-timezone scheduling:

• Never schedule without checking. Before booking a time, look at what it translates to in every attendee's timezone. "Friday afternoon" in New York is Saturday morning in Tokyo. I've accidentally invited people to weekend meetings more than once — embarrassing every time.
• Default to 25 or 50 minutes. Google Calendar has a setting for this. If your meeting ends at :50 instead of :00, people in awkward timezones get a 10-minute buffer to grab food, stretch, or context-switch. This matters more than you'd think when someone's taking a call at 9 PM.
• Record everything. Every synchronous meeting with cross-timezone participants should be recorded and have written notes. Someone will miss it due to a timezone miscalculation. Someone else will be on PTO. The recording isn't optional — it's a courtesy to everyone who couldn't attend.
• Respect "no meeting" blocks. If someone in Singapore blocks 6 PM–9 AM as unavailable, don't override it because the only open slot on your calendar is their 7 PM. Their boundaries exist for a reason.

Tools That Help

World clock tools (like ours) let you compare times across cities instantly. I also recommend adding multiple timezone clocks to your phone's home screen. After a while, you develop an intuition for the offsets. The goal is to internalize the math so scheduling becomes second nature rather than a puzzle every time.

Some specific tools worth mentioning: Calendly and SavvyCal both handle timezone conversion automatically when sharing booking links — the recipient always sees times in their own zone. For team coordination, World Time Buddy gives you a visual overlap grid. And if you're a developer, the Intl.DateTimeFormat API in JavaScript handles timezone-aware formatting natively — no libraries needed for basic conversions.

Frequently Asked Questions

What is the best time for a US-Europe meeting?

Between 13:00 and 16:00 UTC works best — that's 8:00–11:00 AM Eastern and 1:00–4:00 PM in London. Most European and American colleagues are within normal working hours in that window.

How do you handle meetings with Asia-Pacific teams?

For Europe-Asia, aim for 07:00–10:00 UTC. For US-Asia, there's almost no comfortable overlap — rotate between an early morning US slot and a late evening Asia slot, and lean heavily on async communication.

Should calendar invites always include the timezone?

Absolutely. Every invite should specify the timezone explicitly. Most calendar apps auto-convert when you set the event timezone, but adding it to the title or description prevents confusion when people view invites on different devices.

What is the best time zone for global meetings?

UTC is the standard reference for global scheduling. Expressing meeting times in UTC eliminates ambiguity, especially during daylight saving transitions when local offsets change. Most calendar tools can display UTC alongside local time.

How do you rotate meeting times fairly across time zones?

Shift the meeting time by 8 hours each week or rotate monthly so a different region takes the inconvenient slot. Document the rotation schedule so every team sees it is equitable over time.

What does async-first mean for remote teams?

Async-first means defaulting to asynchronous communication — recorded videos, shared documents, and written updates — instead of synchronous meetings. Live meetings are reserved for decisions requiring real-time discussion, reducing the burden of cross-timezone scheduling.

How many hours of overlap exist between US and Asia-Pacific time zones?

There is virtually no comfortable business-hours overlap between the US East Coast and East Asia (e.g., Singapore or Tokyo). The gap is roughly 12-13 hours, so teams typically alternate between an early-morning US slot and a late-evening Asia slot.

Sources

• Harvard Business Review: "How to Collaborate Effectively If Your Team Is Remote" (2024)
• Buffer: State of Remote Work Report (2025)
• IANA Time Zone Database (iana.org/time-zones)