Calendar time, explained
PCT, PST, PDT and the zone ID are different things
Choose an identifier that preserves the location and date. A familiar three-letter label alone is not enough to diagnose a 2026 calendar mismatch.
Start with three separate fields
| Field | Example | What it says |
|---|---|---|
| Human label | PCT | The name shown to people |
| UTC offset | UTC−07:00 | A difference from UTC at an instant |
| Location identifier | America/Vancouver | A set of historical and future rules |
British Columbia’s official announcement uses Pacific Coast Time (PCT) for its permanent time designation. That name does not automatically become a new IANA identifier in calendar software. The location in this tool remains America/Vancouver. Other communities can use other identifiers; a province name is not a substitute for selecting the correct location.
The familiar PST and PDT labels usually express Pacific standard and daylight offsets. Labels can also reflect a software library’s naming conventions. Do not diagnose a one-hour error from an abbreviation alone: record the full date, numeric offset and location ID beside it.
A useful comparison: Vancouver and Los Angeles
Choose November 4, 2026 at 17:00 UTC in the browser probe. The pinned reference displays 10:00 for Vancouver and 09:00 for Los Angeles. Choosing a generic “Pacific” setting without checking its underlying location can conceal this difference.
Now choose October 31. Both reference displays show 10:00. A test conducted only before the transition can pass even when later appointments are wrong. Include dates on both sides of the boundary in a bug report.
For a fictional event intended for 09:00 in Vancouver on November 4, write all of these together: local date 2026-11-04, wall time 09:00, location America/Vancouver, expected offset UTC−07:00, and reference instant 16:00Z. This leaves less room for a sender and receiver to interpret “9 Pacific” differently.
In a calendar file
DTSTART;TZID=America/Vancouver:20261104T090000 DTSTART:20261104T160000Z
These two starts can refer to the same instant under the pinned rule, but they carry different information. The first includes a location; the second fixes UTC. A file can also embed a VTIMEZONE definition that disagrees with a modern location rule. Inspect that definition before concluding that the identifier itself is wrong.
Use the file checker to see the mappings separately. It recognizes a small documented set of location aliases; it does not guess a timezone from PCT, PST, an event title or a street address.
Sources: BC time-name announcement; iCalendar date-time forms; pinned data and scope.