The Meridian Rule

• Working-hour overlap is set almost entirely by east–west distance (longitude), not by total distance. Two cities 8,000 km apart can share a full workday if they sit in the same vertical band of the globe.
• This produces a clear pattern in who hires whom: every client region has a natural delivery partner to its north or south. North America works with Latin America; Europe with Central/Eastern Europe and North Africa; the Gulf with India; Asia-Pacific within its own band.
• The lanes that fail are the east–west ones — US–India, US–Philippines, Europe–East Asia — and they get run anyway, on an asynchronous handoff model where overlap is beside the point.
• The clearest proof is a single inversion: the US West Coast shares roughly zero working hours with Manila, but Sydney shares about six — the same offshore hub, opposite experience, decided entirely by which meridian the client sits on.
• One lane almost no one outside Australia discusses: Sydney and London share essentially no working day at all, which is exactly why Australian firms build teams in Manila and Ho Chi Minh City rather than Europe.

Remote-work maps are usually drawn as if distance were the enemy. It isn't. A team in New York and a team in Bogotá are thousands of kilometres apart and share almost the entire working day. A team in New York and a team in Mumbai are a similar distance apart on the globe and share none of it. The difference isn't how far — it's which direction. Overlap is governed by the gap in longitude, and longitude is what time zones are made of.

That gives global work a hidden grammar. If you want a partner region you can actually hold live meetings with, you don't look for the nearest one — you look for the one directly above or below you, in the same slice of the planet. We calculated the 9-to-5 overlap for the major client-to-hub corridors in every region to show how completely this rule holds.

Every region works with the band beneath it

Read down the client-region column and the rule is obvious. North America's natural workshop is Latin America — Bogotá sits in almost the same zone as the US East Coast, and Mexico City and São Paulo are only an hour or two off. Europe's is a broad southern arc: Poland and Romania are a single hour east, and Casablanca, Cairo, and Lagos sit almost directly beneath the continent. The Gulf's partner is India, barely ninety minutes apart despite the cultural distance — which is one reason the India–Gulf corridor is the largest labour relationship of its kind on earth. And Asia-Pacific quietly runs on its own internal band: Sydney to Manila, Tokyo to Ho Chi Minh City, all comfortably inside a shared afternoon.

None of these regions had to choose overlap-friendly partners on purpose. The geography chose for them. The corridors that feel natural are simply the ones where the meridians line up.

The lanes that don't work — and get run anyway

Every corridor here crosses a large slice of the globe east-to-west, and the overlap collapses accordingly — most sit at zero. Yet these are some of the most heavily travelled outsourcing lanes in existence, US–India above all. That isn't a contradiction. These relationships don't run on shared meeting hours; they run on the handoff. One side finishes and passes the work to the other, who picks it up as the first goes to sleep. Overlap isn't small on these lanes — it's structurally irrelevant, because the entire operating model is asynchronous by design.

Notice the corridor most people never think about: Sydney and London share essentially no working day. Australia sits too far east for Europe entirely. This is precisely why Australian companies don't offshore to the places American and British companies do — they look north into Asia, to Manila, Kuala Lumpur, and Ho Chi Minh City, which fall neatly into their own meridian band.

How to use this

If you're deciding where to build a distributed team, the Meridian Rule turns a vague question into a simple one: find your own vertical band first, then choose within it. If you need live collaboration, hire in the region directly north or south of you and you'll inherit most of the working day for free — Latin America if you're in North America, Central/Eastern Europe or North Africa if you're in Europe, South Asia if you're in the Gulf, Southeast Asia if you're in Australia or Japan. If your work can genuinely run on handoffs, you can reach clear across the globe east-to-west and let cost decide — but go in knowing you've chosen an asynchronous company, not a synchronous one that happens to be far apart.

Want the exact figure for your own pair of cities? Look up any two on the Clockjumper meeting planner, or download the full dataset to sort every pair yourself.

FAQ

Why does direction matter more than distance?

Time-zone offsets are a function of longitude, not total distance. Two cities can be 8,000 km apart and share an entire workday if they sit at similar longitudes, while two cities the same distance apart on an east–west line share none of it. Overlap is decided by the east–west gap alone.

Why do US companies still hire in India if the overlap is zero?

Because they've stopped trying to meet. US–India teams almost always run on an asynchronous handoff model: one side finishes their workday and hands off to the other. It's a different operating model, not a bad-overlap version of the synchronous one.

Where should an Australian company build a distributed team?

In the same meridian band — Manila, Ho Chi Minh City, Kuala Lumpur, or Jakarta. Sydney shares zero working hours with London and about six with Manila, so Southeast Asia gives Australian teams the live-collaboration experience that European hubs cannot.

What's the overlap between Dubai and India?

Dubai and Mumbai (or Bangalore) share about 6 hours and 30 minutes of the 9-to-5 workday, year-round. India is only 90 minutes ahead of the Gulf, which is why the India–Gulf labour corridor is the largest of its kind.

Does daylight saving change these corridors?

It shifts them by an hour in either direction, but it doesn't flip the rule. A corridor that shares six hours in January might share five or seven in July; a corridor that shares zero stays at zero. The January and July columns above show the full range.