Date & Time
Time Zone Meeting Planner
Convert organizer local start to UTC, participant A and B local starts, and UTC meeting end. The world-clock visualization shows all four clocks and explicitly marks local date rollover when an offset crosses midnight.
Meeting start in UTC hour-
Participant A local start hour-
Participant B local start hour-
Meeting end in UTC hour-
Decision view
World meeting clocks
World meeting clocksOrganizer time is anchored to UTC and then translated into participant clocks using the entered fixed offsets.
Exact scenario comparisonOrganizer local start hour (0-23.99) changes while all other entered assumptions remain constant.
| Organizer local start hour (0-23.99) | Meeting start in UTC hour | Participant A local start hour | Participant B local start hour | Meeting end in UTC hour |
|---|
How to use Time Zone Meeting Planner
- Choose the meeting date first and verify each location's actual UTC offset on that date.
- Enter organizer local hour and offsets, including half-hour or quarter-hour offsets as decimals where needed.
- Check local date rollover and working hours before sending a calendar invitation with a named time zone.
Calculator guide
Understanding Time Zone Meeting Planner
A time-zone meeting is anchored to one UTC instant and then displayed in each participant's local clock. The entered numeric offsets provide a transparent conversion but cannot determine daylight-saving rules for a particular date.
Calculation method
How the calculation works
Convert the organizer's local hour to UTC and then apply each participant's entered UTC offset. Subtract organizer UTC offset from organizer local hour and wrap to 24 hours for UTC. Add each participant offset to UTC and wrap to 24 hours. Add meeting duration to UTC for the displayed end hour.
Scheduling
Avoid daylight-saving surprises
Offsets can change independently across countries and dates.
Worked situations
Practical examples
- An organizer at UTC-5 scheduling 09:00 corresponds to 14:00 UTC.
- A participant at UTC+8 sees 22:00, while a participant at UTC+0 sees 14:00.
- A one-hour meeting ends at 15:00 UTC, but the local end date may differ when the meeting crosses midnight.
Better inputs
Useful tips
- Use named IANA zones in the final calendar invitation instead of fixed offsets.
- Recheck recurring meetings across daylight-saving transition dates.
- Rotate inconvenient slots across a distributed team rather than repeatedly burdening one region.
Before relying on the result
Limitations and common mistakes
- The calculator uses fixed offsets and does not know the date, daylight-saving rule, or local calendar.
- It displays wrapped clock hours without explicitly calculating previous-day or next-day labels.
- Public holidays, working hours, ambiguous transition times, and recurring-event changes are excluded.
Reference
Key terms
- UTC offset
- Difference in hours between a local clock and Coordinated Universal Time.
- Local rollover
- A conversion that lands on the previous or next calendar day.
- Named time zone
- Region-based zone with historical and future daylight-saving rules.
- DST
- Seasonal clock adjustment used in some jurisdictions.
Important note
Calculated directly from the entered values using the displayed formula and rounding settings.
Frequently asked questions
How do I enter a half-hour offset?
Use a decimal such as 5.5 for UTC+5:30 or -3.5 for UTC-3:30.
Does the planner know daylight saving time?
No. Enter the actual offset for the meeting date and verify it with a named-zone calendar.
Why can 23:00 plus two hours display 01:00?
The clock wraps after 24:00, indicating a next-day local time even though the current result does not print the date label.
Can this schedule recurring meetings?
It can compare one offset set. Recurring meetings need date-aware time-zone rules.