How to Schedule Meetings Across US Time Zones

Scheduling a meeting should be simple, but it becomes a surprisingly easy thing to mess up when you are working with people all over the country. A 9:00 AM call may feel reasonable to someone in New York while requiring a colleague in California to join at 6:00 AM. Add daylight saving time, travel, and loosely written calendar invitations, and a small misunderstanding can lead to missed calls or late arrivals.

The good news is that scheduling across US time zones does not require memorizing every possible conversion. Once you understand the four main continental time zones and follow a consistent process, it becomes much easier to choose a time that works for everyone regardless of if you’re a manager working remotely or an associate onsite.

The Four Main US Time Zones

The continental United States is commonly divided into four major time zones: Eastern, Central, Mountain, and Pacific. Moving west from one zone to the next usually moves the local clock back by one hour.

If it is 3:00 PM Eastern Time, it is normally 2:00 PM Central, 1:00 PM Mountain, and 12:00 PM Pacific. This basic pattern handles most everyday scheduling within the continental United States.

Alaska and Hawaii use additional time zones, and a few states are split between zones. However, the four-zone pattern above is the most useful starting point for remote work, interviews, webinars, customer calls, and nationwide events.

EST, EDT, PST, and PDT: What the Labels Mean

One of the most common sources of confusion is the difference between labels such as EST and EDT. These abbreviations identify whether standard time or daylight time is being observed.

Eastern Standard Time is abbreviated EST and uses UTC-5. During daylight saving time, the same region uses Eastern Daylight Time, or EDT, at UTC-4. Pacific Standard Time is PST at UTC-8, while Pacific Daylight Time is PDT at UTC-7.

The same distinction applies to Central and Mountain Time:

For ordinary scheduling, it is often clearer to write ET, CT, MT, or PT. These broader labels cover both standard and daylight time. Writing “2:00 PM ET” lets the date determine whether the local clock is observing EST or EDT.

Specific abbreviations still have a place. They are useful when discussing fixed offsets, technical records, historical timestamps, or a period when standard or daylight time definitely applies. For a future meeting invitation, however, the general regional label is usually less likely to confuse people.

How Daylight Saving Time Affects Meetings

Most of the United States moves clocks forward in the spring and back in the fall. Under the current federal schedule, daylight saving time begins on the second Sunday in March and ends on the first Sunday in November. The National Institute of Standards and Technology publishes the applicable dates and explains how the clock changes work.

When Eastern and Pacific locations follow the usual daylight saving schedule, the difference between them remains three hours. New York and Los Angeles change their clocks on the same dates, so a 2:00 PM Eastern meeting remains an 11:00 AM Pacific meeting.

Problems are more likely to appear when one location does not observe daylight saving time, when someone is traveling internationally, or when a calendar is configured to use a fixed abbreviation instead of a geographic time zone. These situations are why the meeting date matters. A simple hour calculation may be correct in January but wrong for a participant in Arizona during July.

The US Department of Transportation notes that Hawaii, most of Arizona, and several US territories do not observe daylight saving time. The official daylight saving time guidance is useful when a meeting includes one of these locations.

A Reliable Way to Schedule Across Time Zones

A repeatable process is more dependable than calculating the difference from memory. The following approach works for one-time calls, recurring meetings, interviews, remote teams, and public events.

Start with the attendees, not the organizer

List where the required participants will actually be on the date of the meeting. Do not assume that a remote employee will be in their usual state or that a traveling client will use the time zone shown in an old email signature.

If attendance is optional for some people, separate them. Meeting participants whose schedules must be protected should also be isolated to their own meeting to avoid confusion. Large invitation lists can be scary for many of us. This approach prevents large invitation lists from making it impossible to find a reasonable time.

Choose one reference time zone

Select a primary zone for planning. This is often the organizer’s time zone, the company headquarters, or the zone containing most attendees. Use it as the reference point while comparing the others.

For a team split between the East and West coasts, you can use BitFern’s PST to EST converter to check the exact Eastern equivalent of a Pacific time on the meeting date. Using the date is important because it allows the tool to apply the appropriate standard or daylight-time rules.

Compare normal working hours

Do not stop after finding a technically possible time. Compare the proposed meeting against each person’s local working hours. A call at 8:00 AM may be acceptable occasionally, but it should not become the default simply because it is convenient for the organizer.

For a typical 9:00 AM to 5:00 PM schedule, these are the broad overlap windows:

These windows show when everyone is nominally working, not necessarily when everyone is available. Lunch, school pickups, customer coverage, and existing meetings can narrow the practical window further.

Put the date and time zone in the invitation

Write the meeting time in a way that is easy to interpret. “Thursday at 2” is incomplete. “Thursday, August 20 at 2:00 PM ET / 11:00 AM PT” will be much clearer for your invitees.

The calendar event should also be assigned to a geographic time zone such as America/New_York or America/Los_Angeles when the platform offers that option. Geographic zones can account for daylight saving rules. A fixed UTC offset cannot always do that on its own.

Check the final calendar preview

Before sending the invitation, view the event in at least one other attendee’s time zone. Google Calendar, Outlook, and many scheduling platforms can display a secondary time zone or preview local times for invitees.

If the meeting time came from a system log, software release schedule, or global event listed in UTC, use BitFern’s UTC to EST converter to translate it into the correct Eastern time for the selected date.

Best Meeting Times for Eastern and Pacific Teams

Eastern and Pacific Time are separated by three hours in normal US scheduling. That’s simple enough right? The most practical overlap usually runs from noon to 5:00 PM Eastern, which corresponds to 9:00 AM to 2:00 PM Pacific.

The middle of that window tends to work best. A meeting at 1:00 PM or 2:00 PM Eastern becomes 10:00 AM or 11:00 AM Pacific. East Coast attendees avoid a late-afternoon call, while West Coast attendees have time to begin their day before joining.

Here are several common examples:

If a recurring meeting must happen outside the shared window, rotate the inconvenience instead of assigning it permanently to the same group. For example, one monthly meeting might favor Eastern attendees while the next favors Pacific attendees.

Common Time-Zone Scheduling Mistakes

Most scheduling problems come from unclear communication rather than difficult arithmetic. A few habits cause an outsized number of errors.

Writing a time without a zone

Messages such as “Can we meet at 10 tomorrow?” force the recipient to guess whose local time is intended. Add the zone every time people are in different regions, even when the difference seems obvious.

Using EST throughout the entire year

Many people write EST when they mean Eastern Time generally. During daylight saving time, cities such as New York and Washington are observing EDT. Using ET avoids making a technically incorrect statement while keeping the message easy to understand.

Forgetting that Arizona is different

Most of Arizona does not observe daylight saving time. During standard time, Arizona generally aligns with Mountain Standard Time. During the daylight-saving months, its local clock aligns with Pacific Daylight Time even though Arizona does not switch to PDT. For an Arizona attendee, always check the date and city instead of applying a permanent Mountain Time assumption.

Treating UTC as a local time zone

UTC is a global time standard and does not move forward or backward for daylight saving time. Eastern Time changes between UTC-5 and UTC-4, so the difference between UTC and the US East Coast changes during the year. The meeting date must be included when converting between them.

Ignoring the calendar date after conversion

Time conversions can cross midnight. This is especially common when international attendees are involved, but it can also affect late-night events within the United States. Always confirm both the local time and local date before sharing the result.

Trusting a recurring event through every clock change

Recurring events usually adjust correctly when they are attached to a geographic time zone. Problems occur when an event uses a fixed offset, when the organizer changes locations, or when attendees are in countries that change clocks on different dates. Review important recurring meetings near daylight saving transitions.

Tips for Remote Teams Working Across US Time Zones

Good scheduling is partly a time-conversion problem and partly a team practice. Remote teams can reduce unnecessary meetings by making more work asynchronous. Written updates, recorded demonstrations, shared documents, and clear task ownership allow people to contribute without joining every conversation live.

When a meeting is necessary, keep a consistent core window for collaboration. An Eastern and Pacific team might reserve 1:00 PM to 4:00 PM Eastern for live calls while protecting the rest of the day for focused work. A predictable window makes planning easier and reduces the chance of early or late invitations appearing without warning.

It also helps to display two time zones in internal announcements. Writing “Launch at 3:00 PM ET / 12:00 PM PT” is more considerate than expecting half the team to convert it. For larger events, add Central and Mountain times or let the calendar invitation automatically display each attendee’s local time.

Finally, ask before assuming that an early meeting is acceptable. Two employees in the same time zone may have different schedules because of customer coverage, childcare, commuting, or flexible working arrangements. The clock gives you a possible window, but the people involved determine whether it is a good one.

Frequently Asked Questions

What is the easiest way to convert US time zones?

Start with the one-hour difference between each neighboring continental zone. Central is one hour behind Eastern, Mountain is two hours behind Eastern, and Pacific is three hours behind Eastern. For a specific date, use a date-aware converter so daylight saving rules and exceptions are handled correctly.

Is Pacific Time always three hours behind Eastern Time?

For locations such as Los Angeles and New York, the difference is normally three hours because both follow the same US daylight saving schedule. The labels change from PST and EST to PDT and EDT, but the three-hour difference remains. Exceptions can arise when comparing fixed abbreviations or locations with different daylight saving practices.

Should I write EST or ET in a meeting invitation?

ET is usually better for future meetings because it covers both Eastern Standard Time and Eastern Daylight Time. Use EST only when standard time specifically applies. The same principle works for PT instead of using PST throughout the year.

What is the best time for a meeting between New York and California?

The broad shared business-hours window is 12:00 PM to 5:00 PM in New York, which is 9:00 AM to 2:00 PM in California. Meetings around 1:00 PM or 2:00 PM Eastern often provide the best balance for both coasts.

Does every US state observe daylight saving time?

No. Hawaii and most of Arizona do not observe daylight saving time. Several US territories also remain on standard time throughout the year. Check the specific location and date when one of these areas is involved.

How should I list multiple time zones in an invitation?

Use the date followed by the most relevant local times, such as “Thursday, August 20 at 2:00 PM ET / 1:00 PM CT / 11:00 AM PT.” If the calendar platform converts the event automatically, listing two primary zones in the description can still reassure attendees that the schedule was checked.

Make the Time Clear Before You Send

Scheduling across US time zones becomes much easier when you stop relying on mental calculations. Identify where attendees will be, choose one reference zone, compare local working hours, and confirm the result for the actual meeting date. Then place the time zone directly in the invitation so nobody has to guess.

For East Coast and West Coast scheduling, BitFern’s Pacific to Eastern time converter provides a quick way to check the local time before sending an invitation. A few extra seconds of verification can prevent a missed meeting and make the schedule more considerate for everyone involved.