TimeZone

ToolByte Blog

Sign in

The Golden Overlap: Finding the Best Meeting Window Between the US, Europe, and Asia

If you've ever tried to schedule a meeting between San Francisco, London, and Singapore, you know the pain. Someone is going to be unhappy. The question is: who, and how unhappy?

The good news is that there's usually a window โ€” sometimes as narrow as one hour โ€” where everyone is at least reasonably awake. We call it the golden overlap. Finding it requires a bit of arithmetic and a willingness to compromise, but it's absolutely doable.

๐Ÿ—บ๏ธ The Three-Hub Problem

Let's set up a concrete scenario. You have three teams:

That's a 16-hour spread in winter (from UTCโˆ’8 to UTC+8). In summer, when London and San Francisco both shift forward, the spread is still 15 hours. Either way, there's no time of day that's convenient for all three simultaneously.

But there is a time that's acceptable โ€” and that's what matters.

Winter scenario (Northern Hemisphere)

Let's look at the overlap windows during standard time:

So where's the golden overlap? It doesn't exist in a single hour for all three. But there's a window where everyone is at least awake โ€” and that's around 7โ€“8 AM San Francisco time, which is 3โ€“4 PM London and 11 PMโ€“12 AM Singapore.

Not great. Singapore is up late, but not absurdly so. SF is up early, but manageable. London is in the sweet spot.

๐Ÿ’ก The compromise: 7 AM SF / 3 PM London / 11 PM Singapore. It's not perfect, but it's the least-bad option โ€” and it's usually the one that works.

๐Ÿ“Š The General Principle

The golden overlap almost always exists at the edges of the workday, not the middle. Why? Because time zones are offset in a way that pushes the overlap to the margins.

If you imagine the 24-hour clock as a circle, the "workday" for each region is an 8โ€“10 hour arc. When you have three regions spread across 15โ€“16 hours, those arcs barely touch. The point where they all intersect โ€” if they do at all โ€” is at the very start or end of someone's day.

In practice, this means:

๐Ÿงฎ How to Find Your Golden Overlap

Here's a step-by-step method you can use for any set of cities:

  1. List the UTC offsets for each location, accounting for daylight saving.
  2. Convert everyone's working hours to UTC. For example, 9 AMโ€“5 PM in London (UTC+0) is 9:00โ€“17:00 UTC. 9 AMโ€“5 PM in SF (UTCโˆ’8) is 17:00โ€“01:00 UTC. 9 AMโ€“5 PM in Singapore (UTC+8) is 01:00โ€“09:00 UTC.
  3. Find the intersection. In this example, there is no intersection โ€” the windows don't overlap at all.
  4. Widen the acceptable hours. If "working hours" means 7 AMโ€“7 PM, the windows expand. SF: 15:00โ€“03:00 UTC. London: 7:00โ€“19:00 UTC. Singapore: 23:00โ€“11:00 UTC. Now the intersection is 23:00โ€“03:00 UTC โ€” which is 3 PMโ€“7 PM SF, 11 PMโ€“3 AM London, and 7 AMโ€“11 AM Singapore.
  5. Pick the slot that minimizes pain. The best compromise is usually the hour where the "outlier" is least inconvenienced.

If you don't want to do this by hand, our Time Zone Converter Hub does it automatically. You can add multiple cities, scroll the 24-hour grid, and see exactly where the green (1st choice) bands line up.

๐ŸŽฏ Practical Tips for the Actual Meeting

Finding the window is half the battle. The other half is making the meeting itself bearable for everyone. A few things that help:

1. Rotate the pain

If Singapore is always the one on the 11 PM call, they're going to burn out. Rotate the slot so the inconvenient time moves around. Maybe one week it's 7 AM SF, the next it's 11 PM Singapore, the next it's 6 AM London. Everyone shares the burden.

2. Keep it short

A 30-minute meeting at 7 AM is much more tolerable than a 90-minute one. Respect the fact that someone is outside their normal hours and cut the agenda accordingly.

3. Record it

If someone genuinely can't attend โ€” or if attending would be harmful to their health โ€” a recording plus a written summary is a perfectly good substitute. Don't force attendance just because it's technically possible.

4. Provide food (if in person)

If you're asking someone to come into the office at 7 AM, at least provide breakfast. Small gestures go a long way.

5. Make it optional

If the meeting is informational, make attendance optional. People will self-select. The ones who show up will be the ones who actually need to be there.

๐ŸŒ Fun fact: The "golden overlap" for USโ€“Europeโ€“Asia is sometimes called the "dead zone" by remote workers, because it's the only time everyone can be reached โ€” but it's also the time when nobody wants to be reached. The term was popularized in a 2019 study on distributed team productivity.

๐Ÿ”„ When There Is No Overlap

Sometimes the math just doesn't work. If your team spans more than 16 hours, there may be literally no time that's reasonable for everyone. In that case, you have three options:

  1. Split the meeting. Hold two sessions โ€” one for the western hemisphere, one for the eastern โ€” and have a rotating representative from each.
  2. Go fully async. Record video updates, use shared documents, and rely on written communication. It's slower, but it's fair.
  3. Accept that someone will be inconvenienced. If the meeting is truly critical, pick the time that works for the most people and make it up to the outliers with comp time or a flexible schedule.

None of these are perfect. But they're better than pretending the problem doesn't exist.

๐Ÿง  The Bigger Picture

The golden overlap isn't just a scheduling trick โ€” it's a reminder that distributed work requires compromise. You can't optimize for everyone's convenience all the time. What you can do is be transparent about the trade-offs, rotate the burden, and make sure the people who are sacrificing their mornings or evenings know that it's appreciated.

Teams that handle this well are the ones that treat time zones as a shared constraint, not a personal problem. And that's what makes them work.


Ready to find your golden overlap? Try our Time Zone Converter Hub โ€” it's free, and it shows you exactly where the green zones line up.

โ† Back to Blog