Best Time to Schedule Meetings Across US Time Zones

Scheduling meetings across US time zones is one of the most common challenges for American businesses. Whether you're coordinating between New York and Los Angeles, or managing a team spread across all four major US time zones, finding the right meeting time requires more than just basic time zone conversion. The good news: the mainland US spans only three hours end to end, so a workable window always exists—you just need to know where it is, and how daylight saving time and a couple of stubborn exceptions (looking at you, Arizona) can quietly move it.

The Four Mainland US Time Zones

The contiguous United States spans four primary time zones. Each observes daylight saving time from the second Sunday in March to the first Sunday in November—with exceptions we'll get to shortly.

Zone	Standard offset	DST offset	Example cities
Eastern (ET)	UTC-5 (EST)	UTC-4 (EDT)	New York, Atlanta, Miami
Central (CT)	UTC-6 (CST)	UTC-5 (CDT)	Chicago, Dallas, Houston
Mountain (MT)	UTC-7 (MST)	UTC-6 (MDT)	Denver, Salt Lake City
Pacific (PT)	UTC-8 (PST)	UTC-7 (PDT)	Los Angeles, Seattle

Beyond the mainland four: Alaska runs on UTC-9/-8, and Hawaii runs on UTC-10 with no daylight saving time at all. Arizona (except the Navajo Nation) also skips DST, staying on Mountain Standard Time (UTC-7) year-round—which means Phoenix matches Denver in winter but matches Los Angeles in summer. If your team includes Phoenix, Honolulu, or Anchorage, treat them as their own scheduling cases rather than lumping them into the nearest mainland zone.

The Overlap Math

Because all four mainland zones shift together on the same DST dates, the relative gaps between them never change: ET is always one hour ahead of CT, two ahead of MT, and three ahead of PT. That makes the core scheduling math stable year-round:

• A standard 9 AM–5 PM workday in New York runs 6 AM–2 PM in Los Angeles time.
• The mutual "everyone is at their desk" window across all four zones is 12 PM–5 PM ET, which is 9 AM–2 PM PT.
• If you also want to avoid lunch hours and the first/last 30 minutes of anyone's day, the practical sweet spot shrinks to roughly 12:30 PM–2 PM ET / 9:30–11 AM PT.

That three-hour east-west spread is why so many US companies default to "late morning Pacific / early afternoon Eastern" for anything involving both coasts. It's not a convention—it's arithmetic.

Optimal Meeting Windows by Team Spread

East Coast and West Coast (3-hour difference)

Best window: 11 AM–2 PM ET, which is 8–11 AM PT. Both teams are in morning or early afternoon, and nobody is asked to dial in before 8 AM or stay past mid-afternoon. Avoid 9–10 AM ET (6–7 AM PT) and anything after 5 PM ET unless the West Coast team has explicitly opted into early starts.

Central and Pacific (2-hour difference)

Best window: 10 AM–1 PM CT / 8–11 AM PT. The two-hour gap is forgiving; the only real trap is late-afternoon Central meetings (a 4:30 PM CT call is 2:30 PM PT—fine) versus late-afternoon Pacific requests (a 4 PM PT call is 6 PM CT—not fine).

Eastern, Central, and Pacific together

Best window: 12–2 PM ET / 11 AM–1 PM CT / 9–11 AM PT. This keeps every participant between 9 AM and 2 PM local. If the meeting must recur daily, 12 PM ET is the least painful anchor: lunch-adjacent in the East, mid-morning in the West.

All four zones

Best window: 12–2 PM ET / 11 AM–1 PM CT / 10 AM–12 PM MT / 9–11 AM PT. A 1 PM ET anchor lands at 10 AM MT and 11 AM CT—comfortable everywhere. For a standing daily stand-up, many all-zone teams settle on 11 AM ET / 8 AM PT as the earliest time that doesn't force pre-8 AM starts on the West Coast.

Pro tip: Use a timezone converter to visualize these windows in real time and account for DST automatically, rather than re-deriving the math for every invite.

Daylight Saving Time: The Twice-a-Year Trap

All four mainland zones spring forward at 2 AM local time on the second Sunday in March and fall back at 2 AM on the first Sunday in November (March 8 and November 1 in 2026). Because they all move together, meetings between mainland US zones are not affected—your 1 PM ET / 10 AM PT call stays 1 PM ET / 10 AM PT all year.

Where DST does bite US schedulers:

1. Arizona and Hawaii. A 1 PM ET meeting is 11 AM in Phoenix during winter but 10 AM during DST months, because Phoenix never moves. Recurring invites that hard-code "11 AM Phoenix time" drift by an hour twice a year relative to the rest of the country.
2. International participants. India (UTC+5:30, no DST) shifts relative to every US zone twice a year: 10 AM ET is 8:30 PM in Bengaluru during EST months but 7:30 PM during EDT months. Europe changes on different dates than the US (last Sunday of March and October), creating a few "shoulder weeks" each year when the usual New York–London gap of 5 hours temporarily becomes 4. If that affects your team, our full daylight saving time guide for global teams walks through every transition.
3. The transition weekends themselves. In March, the 2–3 AM local hour simply doesn't exist; in November, 1–2 AM happens twice. If you run overnight support or batch jobs, those two nights need explicit handling—an "8-hour" overnight shift is actually 7 hours in March and 9 in November.

Common Scheduling Mistakes

1. Pinning recurring meetings to the wrong reference. A meeting created in a proper calendar tool pinned to "1 PM Eastern" stays correct for all mainland participants year-round. Problems arise when someone circulates a PDF schedule listing fixed local times for multiple cities, or pins a US meeting to UTC—UTC never shifts, so the meeting lands an hour off for every US participant half the year.
2. Assuming everyone observes DST. Arizona doesn't. Neither does Hawaii, India, China, or Japan. Never extrapolate one participant's offset from another's.
3. Ignoring local rhythm. 8 AM PT is technically inside the window, but a West Coast parent doing school drop-off will miss it weekly. Conversely, East Coast attendees fade after 4 PM ET. The mathematically valid window and the humanly sustainable window are not the same thing.
4. Booking over lunch in one zone forever. A 12 PM ET recurring call permanently eats lunch for the East Coast. If a slot burdens one zone, rotate it—or at least acknowledge the trade openly.

A Worked Example: Weekly Stand-Up Across All Four Zones

Scenario: You need a weekly 30-minute stand-up with participants in New York, Chicago, Denver, and San Francisco.

1. Add all four cities to your timezone converter and set working hours to 9 AM–5 PM local.
2. The tool highlights the shared window: 12–5 PM ET / 9 AM–2 PM PT.
3. Screen out lunch (12–1 local anywhere) and end-of-day fade: you're left with roughly 1–2 PM ET.
4. Book 1 PM ET / 12 PM CT / 11 AM MT / 10 AM PT. Nobody starts before 10 AM local, nobody runs past 1 PM local, and because all four zones shift together in March and November, the invite never drifts.

Total effort with a visual tool: about a minute. Total effort by hand, checked twice because you don't quite trust your own subtraction: considerably more.

Practical Scheduling Tips

• Use visual tools: A timezone converter with working-hours display shows all times side by side, making overlap windows obvious instead of implied.
• State times in multiple zones: Write "1 PM ET / 10 AM PT" in every invite and message. Redundancy prevents the silent off-by-three error.
• Rotate the pain: If no slot is comfortable for everyone (common once Hawaii or international teammates join), rotate meeting times monthly so the same people aren't always inconvenienced.
• Save your configurations: If you repeatedly coordinate the same cities, save that group in your converter for one-click reuse.
• Audit recurring meetings each March and November: Two minutes of checking beats a month of half the team showing up an hour off.

Frequently Asked Questions

What's the single best default time for an all-US meeting? 1 PM ET (12 PM CT / 11 AM MT / 10 AM PT). It keeps every mainland zone between 10 AM and 1 PM local and survives DST transitions untouched.

Does the time difference between New York and Los Angeles ever change? No. Both observe DST on the same dates, so the gap is exactly 3 hours every day of the year. The gaps that change are those involving non-DST locations like Phoenix, Honolulu, or international cities.

How should I handle a team member in Arizona? Treat Phoenix as Pacific time from March to November and Mountain time from November to March. Better yet, let a DST-aware converter do it—hard-coding either assumption fails half the year.

Is early morning or late afternoon better when someone has to compromise? Early morning on the West Coast usually beats late afternoon in the East. An 8 AM PT meeting catches East Coast colleagues at 11 AM—prime working time—while a 5 PM ET meeting hits the West at 2 PM but pushes Easterners into overtime territory. Energy and attendance data both tend to favor pushing the pain toward Pacific mornings rather than Eastern evenings, but ask the affected team rather than assuming.

What about Alaska and Hawaii? Anchorage (UTC-9/-8) is one hour behind Pacific and does observe DST. Honolulu (UTC-10, no DST) is 5 hours behind ET in winter and 6 in summer—meaning a 12 PM ET meeting is 7 AM or even 6 AM in Hawaii. For teams that include Hawaii, mornings ET are effectively off-limits; aim for 2–4 PM ET instead.

Conclusion

Scheduling across US time zones doesn't have to be complicated. The mainland spread is a fixed 3 hours, the shared window is midday Eastern / morning Pacific, and the only moving parts are DST exceptions like Arizona and any international teammates. With a visual timezone converter that handles DST automatically, the whole problem collapses into picking a slot inside a highlighted window.

For teams managing more complex operations—like contact centers with agents across multiple time zones—consider upgrading to a full workforce management platform that handles scheduling, attendance tracking, and compliance automatically.

Related Guides:

• Daylight Saving Time guide - Complete DST guide
• How to convert UTC to local time - UTC conversion methods
• Multi-client BPO operations - Advanced timezone management

---

Ready to schedule your next cross-timezone meeting? Try Timezone Assistant, a free timezone converter that makes US time zone coordination effortless.