Finance

Plan Meetings Across Time Zones and DST Changes

Convert a meeting time across cities, handle skipped or repeated clock times and read full shared working hours with winter and summer examples.

By the Criza Labs team · Updated · 5 min read

Key takeaways

  • Enter the meeting wall time in the first city's selected time zone.
  • Date-specific browser data handles DST; repeated times need an occurrence choice.
  • The overlap grid shows full UTC hours, with daily work intervals and no calendar checks.

The time zone converter and meeting planner converts one city’s local date and time into the corresponding instant in up to six selected time zones. It also compares daily working intervals in a 24-hour grid. Use it when a meeting that sounds convenient in one city may fall outside working hours or on a different calendar date elsewhere.

The conversion is based on named time zones rather than a fixed offset you have to remember. The selected date matters because an offset can change during the year. Your browser’s installed time zone data supplies those rules. Keep the browser current and recheck important future arrangements when the date or location changes.

Set the first city carefully

The first city defines the meaning of Meeting date and time in the first city. Select that city’s zone before entering the local time. If you later change the first city’s time zone, the entered wall time is reinterpreted in the new zone. The tool does not preserve the original instant while changing its input label.

Choose the appropriate location-based IANA zone, such as Asia/Kolkata or Europe/London. The dropdown uses the browser’s supported time zone list with a small fallback list. City-like names identify zone rules; they do not represent every municipality or a live location lookup. UTC is also available when your source time is already expressed in UTC.

The tool uses the browser’s Intl interface. The official ECMA-402 specification defines the relevant formatting API; checked 16 November 2026. The calculations do not call a remote time service. Output therefore depends on the time zone data installed in the runtime doing the calculation.

Follow the meeting controls

  1. Choose City 1 time zone, then set Meeting date and time in the first city. Supported years are 2000 through 2100.
  2. Leave Repeated clock time during DST change on Earlier occurrence unless the intended time is the later instance of a repeated clock reading.
  3. Set City 1 work starts and work ends. The end is exclusive, so a meeting exactly at the end is outside that interval.
  4. Use Add city and choose each additional zone and its work interval. The maximum is six cities; Remove city removes the numbered row.
  5. Read the converted local dates and times, the UTC instant and the within-work-hours labels.
  6. Read Overlapping working hours, remembering that its cells are labelled in UTC.

Working hours use whole-hour start and end controls. An end earlier than the start means an overnight shift. For example, 22:00 to 06:00 includes late evening and early morning. Identical start and end hours are rejected rather than guessed to mean either no work or a full day.

Two worked examples

Example 1: November in Kolkata and London. Set City 1 to Asia/Kolkata and enter 2026-11-16 15:00. Set City 2 to Europe/London. With the browser rules used in the tests, the resolved instant is 2026-11-16 09:30 UTC. Kolkata displays 15:00 and London displays 09:30 on the same date.

Set both work intervals to 09:00–18:00. Kolkata’s interval on this date corresponds to 03:30–12:30 UTC, while London’s is 09:00–18:00 UTC. Their continuous overlap is 09:00–12:30 UTC. The grid marks three full hours: 09, 10 and 11. The 12 cell covers 12:00–13:00 and therefore does not fit wholly inside Kolkata’s interval.

Example 2: the same wall time in July. Keep the same cities and work hours, then enter 2026-07-01 15:00. The UTC instant is still 09:30, but London displays 10:30 under the runtime’s date-specific summer rule. A fixed “Kolkata minus five and a half hours” conversion to London would therefore be wrong for this scenario.

The London work interval now corresponds to 08:00–17:00 UTC. Full shared grid cells are 08, 09, 10 and 11, giving four whole shared hours. Both seasonal examples, including the converted hour and the overlap cells, are reproduced in Node tests using Intl time zone data.

Skipped and repeated local times

A clock change can make a local reading nonexistent. When the requested local date and minute fall in a gap, the tool shows an error and asks for another time. It does not silently move the meeting forward. This matters because a plausible-looking clock reading can otherwise be interpreted differently by different systems.

A backward clock change can create two instants with the same local date and time. The Earlier occurrence and Later occurrence choices select between them, and the result flags the ambiguity. Check the displayed UTC instant when agreeing on such a meeting. Sharing only the repeated local reading leaves the intended occurrence unclear.

These controls handle the chosen meeting instant. They do not generate recurring invitations. A weekly meeting can move relative to another city’s working day when one location changes clocks before another. Recheck the actual occurrence date rather than assuming one comparison defines the entire series.

Limits of the overlap grid

The grid covers midnight to midnight on the entered calendar date in UTC. It is not the first city’s local day. Some cells can correspond to the previous or next local date in a selected zone. The converted meeting rows include local dates so that this difference stays visible.

Every cell represents a full hour, and partial overlaps are deliberately omitted. Half-hour and quarter-hour zones can therefore have useful partial availability that the filled cells do not express. Treat the bar as a coarse planning view, not a minute-by-minute availability scheduler.

Work intervals repeat every day, including weekends. The tool does not check holidays, personal calendars, booked meetings, travel, lunch breaks or a meeting duration. A selected meeting labelled within work hours describes its start instant; confirm the whole intended duration separately.

Common mistakes

  • Entering a device-local time while the first city is another zone.
  • Reusing a winter offset for a summer meeting.
  • Reading the UTC grid as a local clock.
  • Treating an unfilled partial hour as proof that no overlap exists.
  • Assuming work intervals exclude weekends or public holidays.
  • Sharing a repeated local time without its occurrence or UTC instant.

Questions and answers

Does the tool use my device’s current zone automatically?

The input uses the explicitly selected first city. Read that selection before entering a wall time, especially after adding, removing or changing city rows.

Why can the same local time be rejected?

A clock change may skip it on the selected date. Choose another valid minute. The tool reports the gap instead of inventing a replacement meeting time.

Why are only full hours highlighted?

Each cell covers one complete UTC hour. All of that hour must fit every work interval. This makes the grid conservative where work boundaries fall at half hours or quarter hours.

Can I plan an overnight shift?

Yes. Choose an end earlier than the start, such as 22:00 to 06:00. The interval repeats daily, without a weekend or holiday calendar.

Does this send invitations or save meetings?

No. All conversion happens in the current page. The tool does not contact calendar services, book time, save a meeting or send the entered details anywhere.

Use the timestamp converter to inspect a separate epoch value and the date calculator for calendar-date arithmetic.

Free tools for this

Calculators

Time Zone Converter and Meeting Planner

Convert a meeting date across browser-supported time zones, add up to six cities and compare working hours with date-specific daylight saving handling.

PDF & image

Unix Timestamp Converter

Convert Unix seconds or milliseconds to local time, UTC and ISO 8601. Inspect another time zone, use Now, or convert a date with an explicit offset.

Calculators

Date & Days Calculator

Count the days, weeks and working days between two dates, or add and subtract days from a date.

More guides

Free desktop app from Criza Labs

Bill every day? Get CrizaVoise free

GST invoices, thermal receipts, stock and payments in one offline app for Windows, Linux and macOS. No subscription, no sign-up, no ads, and your data stays on your computer.

  • 58 mm and 80 mm thermal printing
  • UPI QR on every invoice, WhatsApp sharing
  • Open source (Apache 2.0), English, Hindi, Gujarati and more
The CrizaVoise dashboard with quick bill and new invoice buttons, stock alerts and sample figures