Understanding Time Zones Along the West Coast
Pacific Standard Time runs UTC-8 during standard time and shifts to UTC-7 for daylight saving. That's the basic fact most people need. The reality is messier than a two-line Wikipedia entry, especially if you're coordinating anything across multiple cities or dealing with cross-border logistics between the US and Canada. I spent several years working in logistics for a shipping company that moved goods through Portland, Seattle, and Vancouver. The biggest headaches weren't about tracking containers or managing crews. It was always the time zone edge cases. One particular problem I remember involved a warehouse in Bellingham, Washington, right on the border with British Columbia. Our scheduling software defaulted to PST for the entire route, but Vancouver observes Pacific Time only during the summer months when daylight saving is active. In the winter, they switch to Pacific Standard Time while the US side stays on PDT for another week because Canada adopted daylight saving on a different schedule back then. This created a situation where Bellingham and Vancouver were technically in different effective time zones for about a week every spring and fall. Dispatchers would call warehouses and get wrong answers because the internal system didn't account for this overlap. The workaround was straightforward once I figured it out: I stopped relying on the software's automatic time conversion and built a manual lookup table that checked the exact date against whether daylight saving was in effect in both jurisdictions. It took maybe ten minutes to set up and saved us from what used to be three to four scheduling errors per month. Each error meant a truck waiting around for nothing or a delivery window missed entirely.
There's a common misconception that everyone on the West Coast stays on the same time year-round. That's not true. California, Oregon (mostly), Washington, and Idaho's Panhandle all observe Pacific Time, but Nevada and parts of Oregon actually sit in the Mountain Time zone. If you're planning something that crosses those county lines, you need to verify which side of the boundary you're dealing with. A quick map check costs you thirty seconds and prevents significant confusion later. Daylight saving time itself is another layer of friction. The Uniform Time Act of 1966 standardized when clocks change in the United States, but Arizona and Hawaii don't participate. If you're coordinating with someone in Phoenix or Honolulu while based in Los Angeles, you can't assume the clock shift happens at the same moment. During the transition weeks, the time difference between LA and Phoenix effectively changes by one hour for about two months each year. I've lost track of the meetings that got scheduled for the wrong hour because of this. Now I just explicitly confirm the time zone abbreviation with anyone I work with during March and November, rather than assuming. For practical purposes, if you're living or working along the Pacific coast, the useful facts are: PST is UTC-8, PDT is UTC-7, and the switch typically happens on the second Sunday in March and the first Sunday in November. Most smartphone and computer systems handle this automatically now, which is why the old headaches are less common than they used to be. But if you're running something that depends on precise timing across the region, a little manual verification goes a long way.
The deeper reason this matters beyond logistics has to do with how the coast actually functions. Fishing boats, ferry schedules, airport operations, and even restaurant opening times all align to Pacific Time as a practical necessity. You don't build a community's infrastructure around multiple time zones when everyone's economy ties back to a single coastal corridor. The uniformity isn't a technical choice, it's an economic one.
Get the Full Details
