Cross-timezone meeting planner
The awkward truth of distributed work is that some pairs of time zones have no civilised overlap at all.
hours
hours
hours
Overlap across all three zones
0.00hours
- Overlap between the first two
- 0.00 hours
- Best meeting time in UTC
- 0:00:00
- That time in the first zone
- 0:00:00
- In the second zone
- 16:00:00
- In the third zone
- 5:30:00
Show the working
- First zone offset = 0
- Second zone offset = -8
- Third zone offset = 5.5
- Working day starts = 9
- Working day ends = 17
- a_start_utc = 9 - 0 = 9
- a_end_utc = 17 - 0 = 17
- b_start_utc = 9 - -8 = 17
- b_end_utc = 17 - -8 = 25
- c_start_utc = 9 - 5.5 = 3.5
- c_end_utc = 17 - 5.5 = 11.5
- start_ab = max(9, 17) = 17
- end_ab = min(17, 25) = 17
- Overlap between the first two = max(17 - 17, 0) = 0
- start_all = max(17, 3.5) = 17
- end_all = min(17, 11.5) = 11.5
- Overlap across all three zones = max(11.5 - 17, 0) = 0
- best_utc = 0 > 0 ? (17 + 11.5)/2 : 0 = 0
- Best meeting time in UTC = mod(0, 24) * 3600 = 0
- That time in the first zone = mod(0 + 0, 24) * 3600 = 0
- In the second zone = mod(0 + -8, 24) * 3600 = 57 600
- In the third zone = mod(0 + 5.5, 24) * 3600 = 19 800
Values are shown to six significant figures here; the arithmetic itself runs on exact fractions and is only rounded where a number is printed.
Scenarios & local history
Compare a saved scenario
Recent calculations
The formula
- each working day is converted to a UTC interval
- the overlap is the intersection of those intervals
- the suggested time is the midpoint of the overlap
A zero overlap means somebody has to take the call outside working hours. Rotating who does is the only fair answer.