Meeting time planner across time zones

Meeting Time Planner converts a proposed local date and time into three participants’ local times. It is a comparison aid, not an optimizer: it does not rank options or judge work hours, holidays, or preferences.

Use the reference location as the source, then compare all three participant results. A shared date does not guarantee a convenient hour, and a changed date is not an error: it is the same instant represented locally. The planner exposes date-specific offsets, daylight-saving changes, and rollovers. Include the full date, clock time, IANA timezone or city, and UTC offset. If a spring-forward time is rejected or a fall-back time is ambiguous, confirm it first.

How this is calculated

Enter the date, local time, reference location, and participant locations. The runtime preserves the instant and applies each location’s date-specific UTC offset, including daylight-saving rules. Read the date beside every clock time because conversion can cross midnight.

Assumptions and limits

• The entered date and 24-hour time are local to the reference location.
• The UI offers a fixed IANA timezone list, not free-form city search.
• The selected date controls seasonal and daylight-saving offsets.
• The result is a planning aid, not a legal determination.
• The comparison does not score availability or holidays.
• Invitations should retain the date, named timezone, and UTC offset.

Worked examples

Boundary cases

• Date rollover: a late reference time can become the next or previous local date. Invitations must carry the participant date, not only the clock time.
• Spring-forward gap: a local time that does not exist during a daylight-saving jump must be rejected. Choose a valid time.
• Repeated fall-back hour: a clock time can occur twice. Confirm the offset before sending the invitation.
• Half-hour offsets: Kolkata can produce 19:30 rather than a whole-hour result; do not round minutes.

Common mistakes

• Sharing a clock time without its date and named timezone.
• Reusing a remembered offset instead of recalculating the date.
• Calling the result the ‘best’ time when availability is not inspected.
• Ignoring a previous-day or next-day result when creating the event.
• Relying on an abbreviation instead of the IANA location and UTC offset.

Continue your planning

• Time zone converter
• Date rollover calculator
• Business hours overlap calculator

Time-Zone Planning for International Meetings Without the Guesswork

Content updated 2026-11-03 · Maintained by NoteMide · Report a correction

Frequently asked questions