Meeting Time Across Time Zones Calculator
Convert your preferred meeting time into a participant's local time and check whether it falls within business hours. Ideal for remote teams scheduling calls across continents.
About this calculator
When coordinating meetings globally, you need to translate your local time into each participant's local time by applying the UTC offset difference between the two zones. The core conversion is: target_hour = (meeting_hour + (target_offset − organizer_offset) + 24) mod 24. A result between 9 and 17 is considered standard business hours and scores 100. Outside that window, the score degrades based on how far the converted hour drifts from 12:30 (midday), weighted by the business_hours_weight factor: score = 100 − |target_hour − 12.5| × weight. This lets you compare multiple candidate times and pick the slot that imposes the least inconvenience on remote participants. The modulo-24 arithmetic ensures the result wraps correctly across midnight boundaries.
How to use
Suppose you are in London (UTC+0) and want to meet at 14:00, with a participant in Tokyo (UTC+9). Step 1 — offset difference: 9 − 0 = 9 hours. Step 2 — convert: (14 + 9 + 24) mod 24 = 23:00 Tokyo time. Step 3 — business-hours check: 23 is outside 9–17, so isBusinessHours = false. Step 4 — score: 100 − |23 − 12.5| × weight. With weight = 5: 100 − 10.5 × 5 = 47.5. That score tells you the 14:00 London slot is a poor choice for your Tokyo colleague — consider an earlier London time such as 09:00 (18:00 Tokyo) for a better balance.
Frequently asked questions
How do I find a meeting time that works for both Europe and the US West Coast?
The UTC offset gap between London (UTC+0) and Los Angeles (UTC−8) is 8 hours, leaving a narrow overlap. A 09:00 London meeting is 01:00 in LA — outside business hours. A 17:00 London slot converts to 09:00 LA, which is the most practical overlap. Use the calculator's score output to compare candidates; the higher the score, the closer the converted time sits to core business hours for both parties.
What does the business hours priority weight actually control in this calculator?
The business_hours_weight field scales the penalty applied when a converted meeting time falls outside the 9–17 window. A higher weight (e.g., 10) makes the score drop sharply for early-morning or late-evening slots, strongly favouring midday options. A lower weight (e.g., 2) produces a gentler penalty, useful when participants are comfortable with flexible hours. Setting it to 0 effectively makes all times score equally.
Why does the calculator add 24 before applying the modulo operation?
UTC offset arithmetic can produce negative intermediate values — for example, subtracting an 8-hour westward offset from a small hour like 06:00 gives −2. Adding 24 before the mod 24 operation shifts any negative result into a valid 0–23 range without changing positive results. This is a standard technique in clock arithmetic to prevent errors when times wrap backwards past midnight.