Scheduling a meeting between two people in different timezones is annoying. Scheduling one between three or more? That's where things get genuinely hard. I've spent 15 years as a systems engineer working with distributed teams across North America, Europe, and Asia — and I've seen more missed meetings, confused calendar invites, and "wait, what time is it for you?" Slack messages than I can count.
This guide is the one I wish I'd had on day one.
Why Three Timezones Is a Different Problem
With two timezones, you have one gap to bridge. With three, you're triangulating — and the math gets exponential fast. The classic "NYC + London + Tokyo" triangle is the hardest combination in global business because:
- New York (EST, UTC-5) and London (GMT, UTC+0) have a 5-hour gap
- London and Tokyo (JST, UTC+9) have a 9-hour gap
- New York and Tokyo have a 14-hour gap
There is no time when all three cities are simultaneously in standard business hours (9 AM–6 PM). Someone is always at the edge — or outside — of their workday.
Step 1: Map the Overlap Window Visually
Before you pick a time, visualize it. Use QuickTZone to add all three cities and see their working hours side by side. The green bands show 9 AM–6 PM local time. Where they overlap — even partially — is your candidate window.
For NYC + London + Tokyo, the best options are:
| Time (EST) | London | Tokyo | Notes |
|---|---|---|---|
| 8:00 AM | 1:00 PM | 10:00 PM | Tokyo is late but workable |
| 9:00 AM | 2:00 PM | 11:00 PM | Tokyo is very late |
| 4:00 PM | 9:00 PM | 6:00 AM | London is late, Tokyo is early |
The 8–9 AM EST window is generally the least painful — it's morning in New York, afternoon in London, and late evening in Tokyo.
Step 2: Rotate the Inconvenient Slot
The biggest mistake teams make is always scheduling at the same time — which means the same region always gets the bad slot. If Tokyo is always on at 10 PM, that's not fair.
Rotation schedule example (monthly):
- January: 8 AM EST (Tokyo takes the late slot)
- February: 4 PM EST (London takes the late slot, Tokyo gets early morning)
- March: 8 AM EST again (rotate back)
Document this in your team handbook so everyone knows the rotation is intentional and fair.
Step 3: Use Async for Everything That Doesn't Need Real-Time
Not every meeting needs to be live. For a three-timezone team, I recommend:
- Live meetings: Weekly sync, critical decisions, onboarding
- Async: Status updates, code reviews, non-urgent questions
Tools like Loom (video), Linear (project tracking), and Notion (documentation) let you communicate effectively without requiring everyone to be online at the same time.
Step 4: Send Calendar Invites with Explicit Timezones
Never send a meeting invite that says "3 PM" without specifying the timezone. Always use your calendar app's timezone feature, or export an .ics file from QuickTZone that includes the correct timezone metadata.
Google Calendar and Outlook both display the meeting in each recipient's local time automatically — but only if the invite was created with a timezone attached.
Step 5: Build a "Meeting Window" Policy
For recurring meetings, define a policy upfront:
"Our global sync happens every Tuesday. The time rotates monthly between 8 AM EST, 3 PM CET, and 9 AM JST. The current month's time is posted in #announcements."
This removes the weekly "what time is it again?" confusion and sets expectations clearly.
The NYC + London + Tokyo Cheat Sheet
| Scenario | Best Time (EST) | London | Tokyo |
|---|---|---|---|
| Minimize Tokyo inconvenience | 8:00 AM | 1:00 PM | 10:00 PM |
| Minimize London inconvenience | 4:00 PM | 9:00 PM | 6:00 AM |
| Split the difference | 11:00 AM | 4:00 PM | 1:00 AM (next day) |
There's no perfect answer — but there are better and worse choices. The 8 AM EST slot is the most commonly used for good reason.
For the live version of this comparison, open the current reference pages for New York, London, and Tokyo, or add all three cities in QuickTZone. The exact offset can change around daylight saving transitions, so the best time in March is not always the best time in November.
A Practical Rotation Template
Here is a simple policy that works better than arguing every week:
| Month | Primary slot | Who flexes |
|---|---|---|
| January | 8:00 AM New York | Tokyo takes the late call |
| February | 4:00 PM New York | London takes the late call |
| March | 7:00 AM New York | New York takes the early call |
The point is not that these exact times are universal. The point is that the inconvenience is visible, documented, and shared. For global teams, fairness matters as much as the raw overlap.
Tools That Help
- QuickTZone — Visual overlap finder with calendar export
- Google Calendar — Timezone-aware invites
- Calendly — Shows your availability in the viewer's local time
- World Time Buddy — Quick overlap calculator
Author
Written by a systems engineer with 15 years of experience building and managing distributed teams across North America, Europe, and Asia-Pacific.