1. Home
  2. Guides
  3. Schedule across time zones without daylight-saving mistakes
Dates & time

Schedule across time zones without daylight-saving mistakes

Use a city-based time zone and an actual date, handle repeated or missing local times, and check whether a meeting lands on a different day.

Illustration of a globe between two clocks and a calendar, representing meetings scheduled across time zones.

A local clock reading is not yet a unique instant

A meeting time needs a date, a clock time and a time zone. Saying “nine in the morning” does not identify the same instant for people in different locations. Even an abbreviation can be ambiguous, because several regions may use similar names or change their offset seasonally.

Choose a city-based IANA identifier such as America/Chicago instead of guessing a permanent offset. Calculator Simply resolves the source local time to an instant and then formats that instant in the destination zone. This preserves the meeting itself while allowing the destination clock reading and calendar date to differ.

Worked exampleJanuary 1, 2024 at 12:00 UTC becomes January 1 at 06:00 in America/Chicago. The same fixed six-hour difference must not be assumed for every date.

Convert the intended meeting date, not today’s offset

Daylight-saving changes mean the offset that works today may not work on a future meeting date. Different regions can change clocks on different weekends or not change at all. A recurring event may therefore shift in the other participant’s local time even when the organizer keeps the same local hour.

Enter the actual occurrence date when checking a meeting. For a recurring schedule, review dates around clock changes in both locations rather than testing only the first occurrence. The converter uses the browser’s time-zone database; outdated software or a newly changed regional rule can require an additional confirmation.

Worked example: the weeks when New York and London drift

According to NIST, US daylight saving time starts at 2:00 a.m. local time on the second Sunday of March and ends on the first Sunday of November, under the Energy Policy Act of 2005. In 2026 that means March 8 and November 1. Under EU rules, summer time runs from the last Sunday in March to the last Sunday in October, which in 2026 are March 29 and October 25.

The two schedules do not line up. For about three weeks in spring and one week in autumn, the usual five-hour gap between New York and London shrinks to four hours. A weekly 9:00 a.m. New York call moves an hour earlier for London participants during those weeks.

Worked example9:00 in America/New_York → 13:00 in Europe/London on March 16, 2026 (4 hours), 14:00 on April 6, 2026 (5 hours), and 13:00 again on October 26, 2026 (4 hours).

Find the overlap in working hours

Converting one time is only half the job. To pick a slot that suits everyone, convert the start and end of each person’s working day into a single reference zone, often UTC or the organizer’s zone, and look for the hours they share.

Repeat the check for dates on both sides of a clock change. The overlap can grow or shrink by an hour for a few weeks, which may push a regular meeting outside someone’s working day without anyone noticing until it happens.

Worked exampleWorking hours of 9:00–17:00 in both New York and London overlap from 9:00 to 12:00 New York time (14:00–17:00 London) when the gap is 5 hours: 3 shared hours. During the 4-hour weeks the overlap is 9:00–13:00 New York time: 4 shared hours.

Places that do not change their clocks

Not every region observes daylight saving time. NIST lists Hawaii, Arizona, Puerto Rico, Guam, the US Virgin Islands and American Samoa as places that stay on standard time, while the Navajo Nation within Arizona does observe it. Phoenix and Denver share a clock in winter but differ by an hour in summer.

This is why a city-based identifier such as America/Phoenix is more reliable than a label like “Mountain Time”. The database records which places change and which do not, so the converter can apply the right offset for the date you enter.

Recognize missing and repeated local times

When clocks move forward, some local clock readings never occur. When clocks move backward, some readings occur twice and represent two distinct instants. These are not ordinary rounding errors. A calendar entry near a transition must specify a time that exists and resolve any ambiguity deliberately.

The calculator rejects nonexistent source times and requires an explicit policy for repeated times. Do not remove that warning by substituting a guessed offset. Choose the intended occurrence, or move the meeting away from the transition hour and reconfirm with the participants using an unambiguous date and zone.

Worked exampleMarch 8, 2026 at 02:30 in America/New_York does not exist, because clocks jump from 2:00 to 3:00. November 1, 2026 at 01:30 happens twice: the earlier occurrence is 05:30 UTC and the later one is 06:30 UTC.

Share the destination date as well as the time

A conversion can cross midnight, moving the meeting to the previous or next day for someone else. Include the full calendar date when sending the result. For travel, flights and appointments, distinguish the time shown by the operator from the local time at your current location.

Use the output as a check, then send a calendar invitation containing proper zone information when possible. Review the destination display before confirming, especially for deadlines. The tool does not determine an organization’s legal cutoff, operating hours or scheduling policy simply because it can convert the clock reading.

Worked exampleJune 10, 2026 at 17:00 in America/Los_Angeles is June 11 at 09:00 in Asia/Tokyo. A message that says only “5 p.m. Wednesday” would send the Tokyo participant to the wrong day.

Common scheduling mistakes

Writing “EST” in summer, when New York is actually on EDT, is a frequent slip; the safest fix is to name the city. Another is copying a fixed offset such as UTC−5 into a recurring invite, which stays correct for only part of the year.

People also check only the first occurrence of a weekly series, then miss the shift weeks later. For deadlines that cross time zones, state which zone governs the cutoff. To count the days between two dates rather than convert a clock reading, use the date-difference calculator instead.

Sources and further reading

Try the calculators