Worked examples, in Distributed Teams
Time Zone Overlap Examples
Hire across four time zones and you can end up with a 0-hour shared window — meaning every blocking decision requires async and a 24-hour delay. How much overlap you actually have shapes hiring strategy, on-call rotations, and when real-time collaboration is even possible. These examples calculate the numbers for concrete team setups.
4 examples. Published Mar 12, 2026. Updated Oct 5, 2026. By AI Biz Hub.
Worked examples
See the inputs and outcome together
Each scenario keeps the starting point, the outcome, and the actual lesson in one place so the page reads like a decision notebook, not a data dump.
- 1
Baseline case
Try to schedule a 60-minute meeting across New York, London, and Bangalore using each office's standard 9-to-5 hours (Bangalore 10-to-7).
The planner returns 0 candidate slots and the warning: no overlap windows found under current working-hour constraints. The three offices share only 0.5 hours a day (13:00 to 13:30 UTC), too short for a 60-minute meeting.
Participants
New York 9-17, London 9-17, Bangalore 10-19
Meeting Duration Minutes
60
Start Date
2026-03-10
Range Days
5
New York, London, and Bangalore barely share a standard-hours window. The honest answer is to run this collaboration asynchronously or have one office flex its hours, which the next case tests.
- 2
Two-region team
Drop Bangalore and schedule just New York and London at standard 9-to-5 hours.
The planner finds 35 slots across the five days and lists the best 20. The top slot at 13:00 UTC puts New York at 09:00 and London at 13:00, scoring 100 with zero inconvenience for either side.
Participants
New York 9-17, London 9-17
Meeting Duration Minutes
60
Start Date
2026-03-10
Range Days
5
Two regions five hours apart share a clean four-hour daily window (13:00 to 17:00 UTC). A two-zone team almost never needs anyone to work odd hours, which is the easy case to plan around.
- 3
Three regions with flexed hours
Bring Bangalore back, but let New York start at 08:00 and Bangalore stay open until 20:00 to manufacture an overlap.
An overlap now exists. The best slot at 12:00 UTC scores only 73.64: New York joins at 08:00, London at 12:00, and Bangalore at 17:30 with a total inconvenience score of 2.5.
Participants
New York 8-17, London 9-18, Bangalore 8-20
Meeting Duration Minutes
60
Start Date
2026-03-10
Range Days
5
Flexing two offices opened a window, but the 73.64 score is the cost: Bangalore takes an early-evening slot and New York an early start. A three-zone meeting is possible, just never free of compromise.
- 4
Longer meeting, two regions
Return to New York and London only, but stretch the meeting to 120 minutes.
The planner still returns a perfect-score slot at 13:00 UTC: New York 09:00 to 11:00 and London 13:00 to 15:00, scoring 100 with zero inconvenience.
Participants
New York 9-17, London 9-17
Meeting Duration Minutes
120
Start Date
2026-03-10
Range Days
5
Doubling the meeting length costs nothing here because the four-hour shared window comfortably absorbs two hours. Only when a meeting approaches the width of the overlap does duration start forcing trade-offs.
Patterns
Run the numbers next
- Make the Call Commute vs Remote Cost & Time Calculator
Compare office, hybrid, and remote schedules in cash and time.
- Run the Numbers Employee Cost Calculator
Calculate the true total cost of an employee beyond salary — taxes, benefits, and overhead.
Sources
- The Culture Map: Breaking Through the Invisible Boundaries of Global Business , PublicAffairs
- Remote: Office Not Required , Crown Business
Keep the topic connected
- Learn What Is Async Communication? Simply Explained
Async communication explained for distributed teams. Discover how it boosts productivity, reduces meeting fatigue, and enables smooth global collaboration.