Coordinating a call across the United States is easier when you compare local working hours rather than relying on city names or memory. This US meeting planner explains practical overlap windows, daylight saving time checks, recurring scheduling habits, and a simple checklist for arranging meetings across American time zones.
Overview
The United States spans several time zones, so a meeting that feels comfortably timed in New York may fall near the start or end of the workday in Los Angeles, Anchorage, or Honolulu. The most common business-planning pattern runs from Eastern Time through Central, Mountain, and Pacific Time. Alaska and Hawaii require an additional check because their local clocks sit farther west and do not always follow the same daylight-saving schedule as the mainland.
For a first pass, assume a local working day of 9:00 a.m. to 5:00 p.m. This is a planning convention, not a rule. Teams may have different hours, flexible schedules, school pickups, shift work, or customer-service coverage. Use the table below to identify a reasonable starting window, then confirm the participants’ actual availability.
| Participants | Practical overlap during a typical 9 a.m.–5 p.m. day | Best reference |
|---|---|---|
| Eastern and Central | 10:00 a.m.–5:00 p.m. Eastern; 9:00 a.m.–4:00 p.m. Central | Eastern Time |
| Eastern and Mountain | 11:00 a.m.–5:00 p.m. Eastern; 9:00 a.m.–3:00 p.m. Mountain | Eastern Time |
| Eastern and Pacific | 12:00–5:00 p.m. Eastern; 9:00 a.m.–2:00 p.m. Pacific | Eastern Time |
| Central and Mountain | 10:00 a.m.–5:00 p.m. Central; 9:00 a.m.–4:00 p.m. Mountain | Central Time |
| Central and Pacific | 11:00 a.m.–5:00 p.m. Central; 9:00 a.m.–3:00 p.m. Pacific | Central Time |
| Mountain and Pacific | 10:00 a.m.–5:00 p.m. Mountain; 9:00 a.m.–4:00 p.m. Pacific | Mountain Time |
| Eastern, Central, Mountain, and Pacific | 12:00–5:00 p.m. Eastern; 11:00 a.m.–4:00 p.m. Central; 10:00 a.m.–3:00 p.m. Mountain; 9:00 a.m.–2:00 p.m. Pacific | Eastern Time plus the local-time listing |
These examples describe a normal three-hour difference between Eastern and Pacific locations and the usual one-hour steps between the four major mainland zones. Always verify the date before sending an invitation, especially during the weeks when regions change clocks on different schedules.
For background on offsets, boundaries, and clock changes, see the US time zones guide. If your meeting is part of a journey, the US road trip time zone planner can help you anticipate clock changes along a route.
What to track
A dependable scheduling process tracks more than the time difference between two cities. Record the following details for each recurring meeting:
- Participant locations: Use the city or region where each person will actually be on the meeting date, not only the company headquarters.
- Local start and end times: Check whether the proposed slot is within each participant’s agreed working window. A technically possible meeting can still be inconvenient.
- Time-zone labels: Write “Eastern Time,” “Central Time,” or another named zone in the invitation. Avoid relying only on abbreviations that can be interpreted differently.
- Calendar settings: Confirm that every participant’s calendar is set to the correct location and that the event displays in local time.
- Daylight saving status: Check the specific date rather than applying a remembered offset from a previous month.
- Travel status: If someone is flying, driving across state lines, or working temporarily from another location, use the destination’s local time for that date.
- Meeting purpose: Reserve the most convenient overlap for customer calls, presentations, or decisions that require full attention. Routine updates may tolerate a less central slot.
For a simple two-city conversion, compare the locations directly. For several cities, list every local time in the invitation or scheduling note. This removes the need for participants to perform mental calculations and makes conflicts visible before the call begins.
Do not assume every state follows the same clock-change pattern. Some areas observe daylight saving time differently from neighboring states, and the mainland-to-Alaska or mainland-to-Hawaii comparison can create a much narrower overlap. If the meeting includes these regions, use a calendar or time-zone converter for the exact date.
Cadence and checkpoints
Recurring meetings deserve a recurring review. A quarterly check is a practical minimum for teams that work across US time zones. A monthly check is better when schedules, travel, or client coverage change frequently.
- Before creating the series: Choose a slot that works in every listed location and write the local times in the planning notes.
- Before a clock-change period: Recheck the first meeting after the transition. Do not assume a recurring calendar series will match everyone’s intended local hour unless the event is configured with the correct time zone.
- At each quarterly review: Confirm participant locations, working-hour preferences, holidays, and any seasonal operating hours.
- Before important meetings: Verify the exact date, local display, video-conference invitation, and dial-in details on the final agenda.
- After travel or team changes: Recalculate the overlap if someone relocates, joins from another state, or begins working a different shift.
A shared scheduling note can include the meeting’s reference zone, a list of participant cities, the agreed local start time, and the next review date. This is especially useful for distributed teams that do not meet every week.
How to interpret changes
If the overlap table changes, first determine whether the cause is a clock change or a real change in availability. Daylight saving adjustments can shift the apparent difference between locations for part of the year. A participant moving from Chicago to Denver, however, changes the normal relationship between that person’s schedule and the rest of the team.
When the overlap becomes narrow, rotate the inconvenience rather than assigning the earliest or latest slot to the same people every time. For example, alternate a morning meeting for western participants with an afternoon meeting for eastern participants. Document the rotation so expectations remain clear.
Separate “available” from “ideal.” A 9:00 a.m. meeting may be inside someone’s stated workday but still conflict with school drop-off, opening duties, or public transport. Ask participants to identify protected hours and use the remaining overlap for collaboration.
When a meeting includes Alaska or Hawaii, or when a date is close to a daylight-saving transition, display every local time explicitly. If the event crosses midnight for any participant, include the day as well as the time. This small detail prevents missed calls and mistaken travel plans.
When to revisit
Revisit this US meeting planner at least quarterly and immediately before a recurring series passes through a seasonal clock change. Return to it whenever a team member travels, a client changes location, a workday policy changes, or a meeting expands from two time zones to three or more.
Use this practical checklist before publishing an invitation:
- List each participant’s city or time zone for the meeting date.
- Check the exact calendar date for daylight-saving differences.
- Find the shared window within the team’s agreed working hours.
- Choose a reference zone and show each participant’s local time.
- Include the day when any location is near midnight.
- Confirm that the calendar event uses the correct time-zone setting.
- Send a reminder when the meeting follows a clock-change period or major travel schedule.
For a broader comparison of American cities, use the US time difference planner. If international participants are involved, pair this guide with the international flight time conversion guide to account for local arrival times and travel fatigue. Rechecking the details takes only a few minutes and is usually easier than repairing a missed meeting.
