Pacific Time to Eastern Time is the arithmetic backbone of U.S. remote work. When someone in Portland says “let’s meet at nine,” a colleague in Raleigh hears noon in their head—or should. The conversion is simple until travel, daylight saving abbreviations, and recurring calendar series introduce silent errors. This guide gives remote teams concrete PST-to-EST examples, handoff patterns, and when to stop doing mental math.
The add-three-hours rule
During the months when the contiguous United States is on daylight saving time, Pacific Daylight Time (PDT) is three hours behind Eastern Daylight Time (EDT). Add three hours to Pacific to get Eastern: 7:00 a.m. in Los Angeles is 10:00 a.m. in New York.
During standard-time months, Pacific Standard Time (PST) is still three hours behind Eastern Standard Time (EST). The rule does not change: 7:00 a.m. in Seattle is 10:00 a.m. in Boston. What trips people up is naming, not math. “PST” in August is technically wrong even if the offset still works because both zones shifted together.
Quick reference for wall-clock thinkers:
- 6:00 a.m. Pacific → 9:00 a.m. Eastern
- 9:00 a.m. Pacific → 12:00 p.m. Eastern
- 12:00 p.m. Pacific → 3:00 p.m. Eastern
- 3:00 p.m. Pacific → 6:00 p.m. Eastern
Always anchor the conversion to a city pair when writing policy: Los Angeles and New York, Portland and Atlanta, San Diego and Miami. Cities survive DST; acronyms alone do not.
Standup and handoff examples
Daily standup. A team sets 9:30 a.m. Pacific / 12:30 p.m. Eastern. West Coast engineers join before lunch; East Coast PM joins after morning email. If standup creeps to 8:30 a.m. Pacific, confirm Eastern is willing to take 11:30 a.m. every day, not just this week.
Engineering handoff. West Coast closes tickets at 4:00 p.m. Pacific (7:00 p.m. Eastern). East Coast on-call picks up at 7:00 a.m. Eastern (4:00 a.m. Pacific) the next day. Document the nine-hour gap explicitly so nobody assumes instant coverage.
Customer demo. Sales schedules 1:00 p.m. Eastern for a prospect in Boston. Presenters in San Francisco must block 10:00 a.m. Pacific, not “after standup” without conversion.
Performance review conversations. HR defaults to Eastern business hours. A 3:00 p.m. Eastern slot is noon Pacific— workable. A 5:00 p.m. Eastern slot is 2:00 p.m. Pacific—still fine. Pushing to 6:00 p.m. Eastern hits 3:00 p.m. Pacific and collides with school pickup patterns; small shifts matter for equity.
Why the gap stays three hours in summer
Both Pacific and Eastern observe U.S. daylight saving rules on the same weekends. They spring forward and fall back together, so the difference remains three hours all year for the lower forty-eight. Summer does not shrink the gap to two hours the way some international pairs do when only one region moves.
Exceptions appear at the edges, not in the core PST/EST pair. Arizona stays on MST while Pacific uses PDT in summer, which temporarily makes Phoenix align with Los Angeles instead of being an hour behind. Hawaii never shifts. Neither case changes New York versus Los Angeles math, but it does matter if your “Pacific” teammate is actually in Phoenix for a month.
When someone is traveling
Travel overrides employment address. A developer based in Oakland who spends two weeks in Chicago operates on Central Time for meetings whether or not their HR profile still says California. The team channel should note travel weeks; the calendar entry should show the local zone they are physically in.
Common failure: recurring series tied to the organizer’s home zone while the organizer flies east and joins at the wrong local hour. Fix by editing the single instance with a comment, or by requiring travelers to decline and let a delegate host.
Jet lag also changes what “reasonable” means even when math is correct. A 8:00 a.m. Eastern call may be 5:00 a.m. Pacific body clock for someone who landed yesterday from Europe. Human scheduling still applies after correct conversion.
Using a converter page instead of mental math
Mental math fails when dates cross DST weekends, when you add days for deadlines (“EOD Pacific” versus “start of day Eastern”), or when stakeholders mix UTC with local shorthand. A dedicated PST-to-EST page encodes the rules for the exact date you pick, which matters the week clocks change.
Use a converter when:
- Setting a one-time executive meeting three months out
- Explaining handoff times in an incident postmortem
- Writing customer SLAs that reference both coasts
- Onboarding international staff who know UTC but not U.S. labels
Keep using mental math for daily standups at fixed hours once the series is verified. Reach for tools when the date is far, the stakes are high, or the roster includes Arizona, Hawaii, or offshore sites.
Slack reminders that say “in thirty minutes” follow the reader’s device zone, not yours. For coast-to-coast nudges, include the absolute time in both cities: “Demo at 10:00 a.m. Pacific / 1:00 p.m. Eastern” so nobody relies on relative countdowns alone.
Convert any Pacific–Eastern date and hour on the PST to EST page.
PST to EST is three hours, always, for the classic coast pair. Remote teams stay aligned when they write examples into playbooks, re-check travel weeks, and let calculators handle the edge cases while people focus on the meeting itself.