Multi-Zone Conference Call Scheduler
Calculate the optimal call time for the host's local clock that best splits the difference across all participants' time zones. Use it when scheduling global all-hands meetings or client calls spanning east and west.
About this calculator
When participants are scattered from the easternmost to westernmost time zones, there is rarely a universally convenient hour. This calculator finds the host's local time that centres the call in the middle of the geographic spread using: optimal_host_time = (preferred_hour + host_UTC − (easternmost_offset + westernmost_offset) / 2 + 24) mod 24. The midpoint term (easternmost + westernmost) / 2 represents the UTC time equidistant between the two extreme participants. Subtracting this midpoint from the host's UTC offset and adding it to the preferred hour shifts the call towards the centre of the participant window. The mod-24 wrap ensures the result stays within a valid clock hour. This approach minimises the maximum inconvenience for the outlier participants rather than optimising for the majority.
How to use
Host is in UTC+1, prefers 10:00. Easternmost participant is UTC+8, westernmost is UTC−5. Step 1 — midpoint: (8 + (−5)) / 2 = 1.5. Step 2 — adjustment: 1 + (−1.5) = −0.5. Step 3 — raw result: (10 + (−0.5) + 24) mod 24 = 33.5 mod 24 = 9.5, which is 09:30 host time. At 09:30 UTC+1 (= 08:30 UTC), easternmost sees 16:30 and westernmost sees 03:30 — the call is centred as evenly as possible across the 13-hour span.
Frequently asked questions
How do I find the best conference call time for teams in New York, London, and Singapore?
New York (UTC−5), London (UTC+0), and Singapore (UTC+8) span 13 hours. The midpoint offset is (8 + (−5)) / 2 = +1.5 UTC, which corresponds to roughly 09:30 London time. At that moment New York sees 04:30 (outside hours) and Singapore sees 17:30 (just after close of business). No single time works perfectly for all three; the calculator surfaces the least-bad compromise, and you can then rotate meeting times to share the burden fairly.
Why does the formula use the midpoint of easternmost and westernmost offsets rather than averaging all participants?
Using the extreme offsets rather than the full average protects the outlier participants — the people who would otherwise always bear the worst inconvenience. An average of all offsets would pull the optimal time toward the majority, potentially leaving one distant participant permanently disadvantaged. By anchoring to the geographic midpoint between the two extremes, the formula distributes discomfort symmetrically between the farthest-east and farthest-west attendees.
What strategies can reduce the burden of recurring calls that span more than 12 time zones?
For spans exceeding 12 hours, no single call time can be within business hours for all participants simultaneously. Effective strategies include rotating the call time each week so the inconvenience is shared, splitting into regional calls with a delegate bridging the two groups, or using asynchronous video summaries for participants in the most penalised zone. The calculator can be run multiple times with different preferred_hour inputs to produce a rotation table that keeps the worst slot below a set threshold for any one region.