Meetings across cities: why a time needs a date
“The meeting is at nine” is incomplete for a team spread across countries. Add the city and date, and sometimes the UTC offset. The difference between two cities in summer need not match their winter difference.
A time zone is a rule set, not a fixed number
A UTC offset describes one time’s displacement from the reference. A time zone describes a location’s rules over time, including daylight saving and official changes. IANA updates time-zone data to reflect political decisions affecting those rules.
References: IANA — Time Zone Database
A time that never occurs, or occurs twice
When clocks move forward, some local times do not occur. When they move back, a local time can occur twice with different offsets. An ambiguity warning matters for a flight or other time-sensitive appointment.
The published UK schedule for 2026 moves clocks forward on March 29 and back on October 25. This is a dated example, not a rule to assume for every country.
References: GOV.UK — When Do the Clocks Change?
Write an invitation that is hard to misread
Include the day, date and city, then attach a calendar invitation with its time zone. Recheck distant appointments if rules change. For recurring meetings, decide whether the organiser’s local time or a fixed UTC time should remain constant; the effects on other attendees can differ.
- Avoid ambiguous zone abbreviations on their own.
- Do not infer a winter offset from a saved summer appointment.
- Show the destination’s date when the conversion crosses midnight.
- For elapsed duration, use two fully specified instants rather than subtracting clock-face numbers alone.
Dated example: the same UTC time in London
At 12:00 UTC on January 15, 2026, London reads 12:00. At 12:00 UTC on July 15, 2026, it reads 13:00 because of daylight saving.
London’s 01:30 on October 25, 2026 can mean 00:30 UTC before the clock change or 01:30 UTC afterwards. Stating UTC+01:00 or UTC+00:00 distinguishes those instants one hour apart.