When it's 2:00 PM Pacific Time (PT), it's 5:00 PM Eastern Time (ET). That three-hour gap dictates how teams collaborate, when markets close, and why your late-afternoon sync lands right at dinnertime for your East Coast colleagues. If you're managing bi-coastal projects or coordinating remote teams across North America, mastering this conversion prevents missed deadlines and exhausted staff.
The US operates across multiple time zones, but the transcontinental corridor between the West Coast (PT) and East Coast (ET) handles the heaviest volume of remote work and business communication. Daylight Saving Time complicates matters twice a year when clocks shift, but the baseline difference remains locked at three hours. Getting this right means looking past the simple math and building practical communication habits that respect both ends of the wire.
Understanding the Three-Hour Pacific to Eastern Gap
The math is straightforward: Eastern Time is always three hours ahead of Pacific Time. When your clock in Seattle or Los Angeles reads 2:00 PM, your partners in New York or Miami are already looking at 5:00 PM.
This creates a lopsided workday overlap. A standard 9-to-5 schedule in New York starts three hours before a standard 9-to-5 in San Francisco. By the time a West Coast employee logs on at 9:00 AM PT, their East Coast counterpart has already burned through the morning, eaten lunch, and is halfway through the afternoon at 12:00 PM ET.
Standard Time vs Daylight Saving Time
North America shifts clocks twice a year, but because both PT and ET observe Daylight Saving Time on the exact same schedule (coordinated by the National Institute of Standards and Technology), the three-hour gap never changes.
- Pacific Standard Time (PST): UTC-8 (November to March)
- Pacific Daylight Time (PDT): UTC-7 (March to November)
- Eastern Standard Time (EST): UTC-5 (November to March)
- Eastern Daylight Time (EDT): UTC-4 (November to March)
Even though the UTC offsets shift by an hour in the spring and fall, the relative distance between coasts stays fixed at three hours. You don't have to recalculate the gap seasonally, but you do need to remember that UTC offsets themselves change.
The Bi-Coastal Workday Window
Scheduling meetings across this divide requires strict discipline. If you drop a 2:00 PM PT meeting onto a calendar, you're asking your East Coast team members to join at 5:00 PM—often right as they're trying to wrap up their day and log off.
Conversely, scheduling an early morning meeting on the East Coast at 9:00 AM ET means dragging West Coast workers onto a call at 6:00 AM PT before their offices are even open.
To keep teams productive without burning people out, you need to rely on the shared overlap window:
- The Golden Overlap: 9:00 AM to 12:00 PM PT (which equals 12:00 PM to 3:00 PM ET).
- The Danger Zone: Anything after 2:00 PM PT on the West Coast hits 5:00 PM or later on the East Coast.
Practical Strategies for Cross-Coast Teams
If you're tired of timezone confusion messing up your project timelines, you need systems that remove mental math from the equation. Relying on people to remember conversions manually leads to missed calls and frustrated employees.
Standardize Your Calendar Tools
Set your primary calendar tools, like Google Calendar or Outlook, to display multiple time zones side by side. When you invite participants from different regions, the platform handles the conversion automatically, but you still need to look at the recipient's local time before hitting send.
- Always list meeting times in both formats on calendar invites: e.g., "2:00 PM PT / 5:00 PM ET".
- Default to asynchronous communication for updates that don't require an immediate back-and-forth.
- Use scheduling links like Calendly that automatically detect and display the booker's local time zone.
Respect the Edge Hours
When someone on the East Coast gets an email at 4:30 PM ET, they have thirty minutes left to reply before logging off. If you sent that email from the West Coast at 1:30 PM PT, you thought you gave them plenty of time. Misjudging that perception causes unnecessary friction.
- Send urgent requests before 11:00 AM PT (2:00 PM ET) to ensure same-day turnaround from East Coast staff.
- Avoid booking recurring meetings during the final hour of the East Coast workday.
- Set team norms around response expectations after 3:00 PM PT.
Common Mistakes When Converting Time Zones
Even experienced remote workers trip up on basic scheduling details. Here are the most frequent pitfalls and how to avoid them.
- Assuming UTC offsets never change: Failing to account for the exact dates when Daylight Saving Time begins or ends can throw international or cross-border partners off by an hour, even if domestic US coasts stay synchronized.
- Forgetting local closing times: Expecting a financial institution, government office, or vendor on the East Coast to respond to an inquiry sent at 2:00 PM PT (5:00 PM ET) when most offices close at 4:00 or 5:00 PM local time.
- Overusing 'EST' out of habit: Using Eastern Standard Time labels during summer months when the region is actually observing Eastern Daylight Time (EDT). While minor, precision matters in legal and financial scheduling.
Frequently Asked Questions
If it is 2:00 PM PT, what time is it in ET?
It is 5:00 PM ET. Eastern Time is always three hours ahead of Pacific Time throughout the year.
Does the three-hour gap change during Daylight Saving Time?
No. Both the Pacific and Eastern zones observe Daylight Saving Time and switch on the exact same weekends, keeping the three-hour difference constant year-round.
What is the best time of day for a cross-country meeting between PT and ET?
Between 10:00 AM and 1:00 PM PT. This corresponds to 1:00 PM and 4:00 PM ET, landing squarely in the middle of the workday for both coasts without eating into early mornings or late evenings.
How do I stop mixing up AM and PM during time conversions?
Adopt the 24-hour clock (military time) for internal scheduling documentation. Writing 14:00 PT / 17:00 ET removes ambiguity entirely.
