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.
Australia/Sydney uses UTC+11:00 in the January sample and UTC+10:00 in July. An instruction to use a “summer offset” is incomplete without the location and date. The software resolves the IANA rule directly rather than borrowing the seasonal pattern of a northern city.
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+11:00
AEDT
2026-07-15
UTC+10:00
AEST
2026-10-27
UTC+11:00
AEDT
2026-11-03
UTC+11:00
AEDT
Resolve the wall time before exporting
On 5 April 2026, 02:30 occurs twice in this zone, at UTC+11:00 and UTC+10:00. On 4 October, 02:30 is missing. Review these local dates when a weekly meeting is anchored near the overnight change.
Use this identifier in a plan
Find Australia/Sydney in the zone directory or choose Sydney 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.