The 2026 rules need a fresh comparison

The bundled IANA 2026f data gives Vancouver UTC−08:00 in January and UTC−07:00 in July, October, and November 2026. Unlike Los Angeles, Vancouver does not return to UTC−08:00 in the November sample. This is why the planner keeps America/Vancouver as a named rule set rather than treating it as a synonym for another Pacific city.

A dated view of the local clock

Four examples at 13:00 UTC, calculated with IANA 2026f. These are selected dates, not a live clock.
UTC dateUTC offsetAbbreviationLocal date and time
2026-01-15UTC−08:00PSTThu, 15 Jan 2026 · 05:00
2026-07-15UTC−07:00PDTWed, 15 Jul 2026 · 06:00
2026-10-27UTC−07:00PDTTue, 27 Oct 2026 · 06:00
2026-11-03UTC−07:00MSTTue, 3 Nov 2026 · 06:00

Check both sides of the continent

At 09:00 Vancouver on 3 November 2026, Toronto reads 11:00 and Los Angeles reads 08:00. A plan copied from the previous week may therefore need a different local start in either city. Save the date and zone with the plan, and recheck when time-zone data is updated.

Build a plan for this city

Select Vancouver, add the other participants, and enter the actual meeting date. The planner uses America/Vancouver; the abbreviation in the table is a display label. Adjust working days, hours, and meeting length before choosing a shared window. The supported planning range is 2026–2035.