A Time Zone Needs a Date When Daylight Saving Is Involved

A time zone describes a region's rules for local time. A UTC offset describes the difference from Coordinated Universal Time at a particular moment. They are related, but a fixed offset does not always capture the region's rules throughout the year.

The date can change the conversion

Some places observe daylight saving time and others do not. Transition dates can differ between countries. As a result, the time difference between two cities may change for part of the year.

A remembered rule such as “they are always three hours ahead” can therefore fail around a clock change. Use the actual meeting date and a location-based time zone in a calendar or reliable conversion tool.

Avoid ambiguous abbreviations

Short labels can mean different things in different places, and people sometimes use a standard-time abbreviation when they mean local time generally. A city and date are clearer than an unexplained three-letter label.

For an invitation, include the date, local time, and named time zone. Let the calendar store the zone rather than manually adjusting a copy for every attendee. Ask recipients to check how the invitation appears in their own calendar if the event is important.

Recheck recurring events

A weekly meeting intended to remain at the same local time may shift relative to another region after a daylight-saving transition. A recurring event defined in UTC behaves differently. Decide which behavior the organizer intends.

NIST provides US time information, while time-zone rules are administered by the relevant authorities. Rules can change, so keep device time-zone data current and verify important future events. The missing ingredient in many conversion mistakes is not arithmetic; it is the date to which the rule applies.