Understanding San Francisco Time
San Francisco sits in the Pacific Time Zone, which means it switches between Pacific Standard Time and Pacific Daylight Time twice a year. Most people just check their phone and don't think about it again until they miss a meeting by an hour. I've been scheduling cross-country calls for over a decade, and I still occasionally mix up whether daylight saving is active or not. The short version is that PST is UTC-8 and PDT is UTC-7. California stays on PDT from the second Sunday in March through the first Sunday in November. Outside that window, it's PST. That's the whole mechanism. Nothing fancy about it. Here's what most guides leave out: the switch days are the same across the entire Pacific Time Zone, but not everyone in the US observes daylight saving. Arizona (except the Navajo Nation) and Hawaii don't change their clocks. So if you're coordinating with Phoenix or Honolulu and someone says "we're on Pacific time," clarify immediately. I learned that the hard way when I scheduled a quarterly sync with a Phoenix-based vendor who assumed PST would apply year-round. The call happened at 3 AM my time instead of 12 PM because they were actually observing Mountain Standard Time while thinking they matched our zone. We switched to shared calendar invites with explicit offset notation after that.
How The Switch Actually Works
Daylight saving time begins at 2:00 AM on the second Sunday in March. Clocks jump forward to 3:00 AM. That means you lose an hour of sleep, but more importantly for remote work, any automated systems set to fire at 2:00 AM during that window get skipped entirely. If you have cron jobs or scheduled scripts running at that hour, they won't execute. I ran into this when a data pipeline scheduled for 2:15 AM PST disappeared on switch day and didn't resume until I manually triggered it. Since then I always mark the transition in my calendar with a reminder to verify automated processes. The fall back happens at 2:00 AM on the first Sunday in November. Clocks go back to 1:00 AM. This time you gain an hour, but duplicate timestamps become a problem. An event scheduled for 1:30 AM is ambiguous unless you specify AM or PM explicitly. Some older scheduling tools interpret both occurrences as the same time and drop one. I use ISO 8601 format for everything now—2024-11-03T01:30:00-07:00 instead of just writing 1:30 AM—to avoid any confusion regardless of how the receiving system parses it.
What This Means For Scheduling
If you're in New York and calling San Francisco, the offset is usually three hours during standard time and two hours during daylight saving. That reversal trips people up constantly. In January it's 9 AM to 6 PM overlap. In July it's 10 AM to 7 PM overlap. The overlap window shifts by an hour every six months, which means your recurring weekly standup time drifts relative to the coasts unless you anchor it to a UTC timestamp. When booking meetings with multiple zones, use Coordinated Universal Time as the reference point and let each person's client convert locally. I stopped asking "what time works for you" years ago. Instead I calculate the overlap window in UTC, pick a slot inside it, and send the UTC time with a note that recipients should view it in their own timezone. It removes the back-and-forth and eliminates the DST mix-ups that used to cost me at least one rescheduled call per quarter. There's no perfect solution here. The US daylight saving system itself is the bottleneck. Other countries have different switch dates or don't observe it at all, which compounds the problem for international teams. But once you lock into UTC as your scheduling baseline and stop treating Pacific Time as a fixed offset, the daily friction drops significantly.
Get the Full Details
