Study 4 of 5
The Meridian Rule
Working-hour overlap is governed almost entirely by longitude, not latitude. A team spread north–south keeps nearly the whole workday together; a team spread east–west loses it — and past about four hours of separation, it loses it almost completely.
Last updated July 2026
ClockJumper studies are produced with AI assistance and human review. · research methodology
- Grouped by circular time-zone separation (the shorter way around the globe), mean overlap falls in an orderly staircase (January): 8h at 0 hours, 7h01m at 1 hour, 6h04m at 2, 5h10m at 3, 4h06m at 4 — and 0h58m at 5+ hours.
- Between 4h and 5h of separation, overlap collapses from nearly four hours to under one — a hard threshold where live collaboration stops working and teams are forced into asynchronous handoffs.
- Latitude doesn't touch the clock. Stockholm ↔ Cape Town holds 7–8 hours; London ↔ Johannesburg keeps 6–7. Moving north or south changes the weather, not the time.
- The same distances run east–west and the workday vanishes: San Francisco ↔ Mumbai, New York ↔ Tokyo, London ↔ Auckland, Los Angeles ↔ Singapore — all zero.
Every hour of longitude costs an hour of overlap — until the cliff
Mean workday overlap across every city pair, grouped by absolute UTC-offset delta. The decline is smooth from 0 to 4 hours; at 5+ hours the shared workday collapses.
Between 4h and 5h of separation, mean overlap drops from 4h06m to 0h58m — the point where a shared 9-to-5 stops existing.
The relationship is close to mechanical. Group all 24,753 pairs by hours of time-zone separation (measured the shorter way around the globe), and the average overlap falls in an orderly staircase: 8 hours of shared workday at zero separation, 7 hours 1 minute one hour apart, 6 hours 4 minutes at two, 5 hours 10 minutes at three, 4 hours 6 minutes at four. Then it falls off a cliff. Beyond four hours of separation, average overlap collapses to under an hour — 58 minutes on average — across the entire 5-plus-hour range that contains most of the world's long-haul pairs. There is, in effect, a hard threshold: up to roughly four hours of offset, live collaboration is workable; past it, live collaboration effectively ends and teams are forced into asynchronous handoffs.
What makes this a rule about direction rather than distance is that latitude does not touch the clock. Consider the pairs that span whole hemispheres from north to south. Stockholm and Cape Town — a straight line from the Arctic edge of Europe to the tip of Africa — hold seven to eight hours of overlap. London and Johannesburg keep six to seven. Paris and Lagos, Helsinki and Nairobi: near-complete workdays, every one, because moving north or south changes the weather, not the time.
Now the same distances run east to west, and the workday vanishes. San Francisco and Mumbai: zero overlap. New York and Tokyo: zero. London and Auckland: zero. Los Angeles and Singapore: zero. Several of these pairs are closer in great-circle distance than the north–south pairs that keep a full day — but they're separated along the axis that actually moves the clock, and so they share no working hours at all.
Every region works with the band beneath it
| Corridor | Client region | January | July |
|---|---|---|---|
| New York ↔ Bogotá | North America | 8h | 7h |
| New York ↔ Mexico City | North America | 7h | 6h |
| New York ↔ São Paulo | North America | 6h | 7h |
| San Francisco ↔ Mexico City | North America | 6h | 7h |
| London ↔ Warsaw | Europe | 7h | 7h |
| Berlin ↔ Bucharest | Europe | 7h | 7h |
| Paris ↔ Casablanca | Europe | 8h | 7h |
| Frankfurt ↔ Cairo | Europe | 7h | 7h |
| London ↔ Lagos | Europe | 7h | 8h |
| Dubai ↔ Mumbai | Middle East | 6h 30 | 6h 30 |
| Dubai ↔ Bangalore | Middle East | 6h 30 | 6h 30 |
| Sydney ↔ Manila | Asia-Pacific | 5h | 6h |
| Tokyo ↔ Ho Chi Minh City | Asia-Pacific | 6h | 6h |
| Tokyo ↔ Manila | Asia-Pacific | 7h | 7h |
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
| Corridor | Client region | January | July |
|---|---|---|---|
| New York ↔ Mumbai | North America | 0h | 0h |
| San Francisco ↔ Manila | North America | 0h | 0h |
| Los Angeles ↔ Bangalore | North America | 0h | 0h |
| London ↔ Singapore | Europe | 0h | 1h |
| London ↔ Tokyo | Europe | 0h | 0h |
| Sydney ↔ London | Asia-Pacific | 0h | 0h |
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.
The proof: one hub, two very different experiences
Same destination. Same offshore teams, often the same buildings. The only thing that changed is which meridian the client sits on. For a company in California, Manila is a night-shift relationship held together by asynchronous handoffs. For a company in Sydney, the identical hub is a normal colleague you meet with every afternoon. “Offshore” was never one experience — it depends entirely on where you're standing east-to-west. The distance to Manila is almost the same in both cases; the overlap is the opposite.
How to use this
The rule for anyone building a distributed team is therefore simpler than it looks: the axis matters more than the distance. A company that wants its people working live together should grow along a meridian — north and south — and can span the globe pole-to-pole without losing an hour. A company that grows east–west should stop expecting to meet, and design deliberately for handoff instead. Geography sets the ceiling; you only get to choose which direction you build in.
Full methodology is on the methodology page.
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.
Figures: mean overlap by UTC-offset delta across all 24,753 pairs; contrast pairs drawn from the January/July dataset.
- 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.
Explore the live data
The numbers on this page are a static snapshot. Use the live tools below to check the current offset, overlap, and daylight-saving status for any city or pair.