Schedule across time zones without the surprises

America/New_York, Europe/London, and Asia/Tokyo are IANA time-zone IDs. They identify regional rules for a particular date, including daylight-saving changes when applicable. “UTC−5” identifies only a fixed offset. New York is UTC−5 in winter but UTC−4 during daylight saving, so a recurring “9:00 UTC−5” call will drift away from 9:00 in New York for part of the year.

Abbreviations are a poor invitation format too. “EST” is often used casually when someone means Eastern time year-round; strictly, EST is standard time (UTC−5), not summer EDT (UTC−4). “CST” can mean different zones in different parts of the world. Write “9:00 a.m. in New York” or include America/New_York instead.

Daylight saving is not synchronized worldwide. In 2026, most of the United States moves clocks forward on March 8, while the United Kingdom does so on March 29. Between those dates, New York is UTC−4 and London is UTC+0: their difference is four hours rather than the usual five in much of winter. Regions that do not change clocks, such as Tokyo, can still have a changing difference from cities that do.

Check the actual meeting date, especially for a recurring event spanning a seasonal change. Rules also vary by jurisdiction and can be revised; a conversion made months ago is worth checking again before travel or an important call. The live world clock is useful for comparing what places show now, but today’s offset alone is not a promise about a future date.

When clocks spring forward, a block of wall-clock time is skipped. In New York on March 8, 2026, the clock jumps from 1:59 a.m. to 3:00 a.m.; 2:30 a.m. that day does not exist there. When clocks fall back on November 1, 2026, 1:30 a.m. occurs twice: once in daylight time and again in standard time. A date, city, and “1:30 a.m.” are not enough to distinguish those two instants.

Avoid scheduling inside a changeover hour. If it is unavoidable, specify an exact UTC instant or include the applicable UTC offset as well as the named zone. Ask your calendar to show the recipient’s local conversion before sending.

1. Pick a specific date and named zone for the organizer, not “next Wednesday at 9” without a place.
2. Convert that dated time to UTC and the attendees’ cities with a date-aware calendar or converter. Check working hours and the calendar date for each person.
3. Put the original zone and UTC instant in the invite. Ask attendees to confirm the time shown in their own calendars, especially around daylight-saving changes.
4. For a recurring meeting, review the series after each region’s clock change rather than assuming the local hour stays fixed for everyone.

The International Date Line is a useful geographic shorthand, but civil dates depend on each place’s time zone and local rules, not a perfectly straight line on a map. Even without crossing the Pacific, the same instant can be Tuesday evening for one attendee and Wednesday morning for another.

For example, Monday, January 5, 2026 at 15:00 UTC is 10:00 a.m. Monday in New York (EST) and 12:00 a.m. Tuesday, January 6 in Tokyo (JST). Include the weekday and date alongside the hour in any message that spans continents. When reading the world clock’s city dates, compare the date label as carefully as the hour.