Before and after show the boundary labels at the exact UTC transition. A missing or repeated local label still requires an explicit choice in the planner.
Why an identifier matters
An offset describes one moment. A named zone carries the date-specific rules used to calculate each meeting.
Planning dates run from Thu, Jan 1, 2026 through Mon, Dec 31, 2035. Future rules can be revised; review the data version when a distant schedule matters.
Europe/Paris is a date-sensitive rule identifier, not a permanent synonym for UTC+01:00. Its July 2026 sample is UTC+02:00. Other European cities may match these clock values on a chosen date, but keeping the intended named zone preserves the meaning of the plan.
Offsets in the bundled rules
Sampled at 12:00 UTC on each date, using IANA 2026f.
Date
UTC offset
Display abbreviation
2026-01-15
UTC+01:00
CET
2026-07-15
UTC+02:00
CEST
2026-10-27
UTC+01:00
CET
2026-11-03
UTC+01:00
CET
Resolve the wall time before exporting
On 25 October 2026, 02:30 occurs twice in this zone, first at UTC+02:00 and then at UTC+01:00. In spring, 02:30 on 29 March is skipped. A local clock label cannot choose the intended instant on its own.
Use this identifier in a plan
Find Europe/Paris in the zone directory or choose Paris from the city directory. Add the other meeting locations, enter their availability, and check the complete duration. The supported planning years are 2026–2035; future political rule changes may require a new data version.
A calendar export uses the resolved UTC start and end times. The zone remains part of the planning context, while the exported instant stays unambiguous when another calendar displays it in its own time zone.