US Time Zones & DST Rules for Remote Work Scheduling

Picture this: You're a remote project manager based in Brooklyn, New York. You schedule a critical team sync for 10:00 AM Eastern Time. Your engineering lead in Denver logs in at 8:00 AM, coffee in hand, ready to go. Your designer in Phoenix shows up at 8:00 AM too — except Arizona doesn't do daylight saving time, so depending on the time of year, that could actually be 7:00 AM Mountain Daylight Time or 8:00 AM Mountain Standard Time. Your customer support lead in Honolulu? They're still asleep because it's 4:00 AM in Hawaii. By the time everyone is on the call, half the meeting is gone, and you're already behind schedule. If this sounds familiar, you're not alone. For millions of remote workers across the United States, time zone confusion is a daily headache that causes missed meetings, delayed deadlines, and unnecessary stress.

The problem only gets worse during daylight saving time transitions. Twice a year, the entire country (except Arizona and Hawaii) shifts its clocks forward or backward by an hour. But not everyone remembers. And because different devices update at different times — some automatically, some manually — you can end up with a team where half the people are on the new time and half are still on the old one. For remote teams that span multiple time zones, these transition weeks are particularly chaotic. A meeting that worked perfectly in March might be an hour off in November if you don't account for the shift. Getting time zones right isn't just about being punctual — it's about respecting your teammates' work hours, maintaining work-life balance, and keeping projects running smoothly.

Core Rules of US Time Zones and Daylight Saving Time

The continental United States is divided into four primary time zones, running roughly north-south from the Atlantic to the Pacific. From east to west, these are the Eastern Time Zone, Central Time Zone, Mountain Time Zone, and Pacific Time Zone. Each zone is approximately 15 degrees of longitude wide, which corresponds to a one-hour difference in solar time. In practice, time zone boundaries often follow state lines or other geographic features rather than strict meridians. Eastern Time is five hours behind Coordinated Universal Time (UTC-5) during standard time, Central is UTC-6, Mountain is UTC-7, and Pacific is UTC-8. Alaska and Hawaii add two more zones: Alaska Time at UTC-9 and Hawaii-Aleutian Time at UTC-10.

Daylight saving time is the practice of setting clocks forward by one hour during the warmer months to extend evening daylight. In the United States, DST starts on the second Sunday of March and ends on the first Sunday of November. The change happens at 2:00 AM local time — in March, clocks jump from 2:00 AM to 3:00 AM, and in November, they fall back from 2:00 AM to 1:00 AM. This schedule was established by the Energy Policy Act of 2005, extending DST from the previous schedule of first Sunday in April to last Sunday in October. The rationale was energy conservation, though studies on the actual energy savings have produced mixed results. During DST, the time zones shift to UTC-4 (Eastern Daylight Time), UTC-5 (Central Daylight Time), UTC-6 (Mountain Daylight Time), and UTC-7 (Pacific Daylight Time).

Not all parts of the United States observe daylight saving time. The most notable exceptions are Arizona and Hawaii. Arizona — with the exception of the Navajo Nation, which covers much of northeastern Arizona — stays on Mountain Standard Time year-round. The Navajo Nation does observe DST to align with the neighboring states of New Mexico, Utah, and Colorado. Hawaii stays on Hawaii-Aleutian Standard Time year-round with no DST observance. US territories including Puerto Rico, the US Virgin Islands, Guam, American Samoa, and the Northern Mariana Islands also skip DST. This means that depending on the season, the time difference between, say, California and Arizona changes: during standard time (November-March), both are UTC-7 and UTC-8 respectively (one hour apart), but during daylight saving time (March-November), California moves to UTC-7 while Arizona stays at UTC-7, making them the same time. This seasonal shift catches many remote workers off guard.

For remote teams, the practical implication is that the relative time difference between locations can change throughout the year. If you have team members in both DST-observing and non-DST-observing locations, your meeting schedule that works in January might not work in July. New York and Phoenix are two hours apart in January (Eastern Standard Time vs Mountain Standard Time) but three hours apart in June (Eastern Daylight Time vs Mountain Standard Time). That extra hour can mean the difference between a 9:00 AM start for your Arizona team and a 6:00 AM start — a significant impact on work-life balance and morning productivity. Smart remote teams plan for these shifts in advance and adjust meeting schedules accordingly, rather than forcing west coast or non-DST teammates to always accommodate east coast hours.

Common Mistakes and Pitfalls

• Forgetting about Arizona's no-DST status. This is by far the most common time zone mistake for remote teams. Most people know Arizona is in the Mountain Time Zone, but they forget it doesn't do daylight saving. Half the year, Arizona matches Mountain Standard Time (same as Denver in winter). The other half, Arizona is effectively on Pacific Daylight Time (same as Los Angeles in summer). If you schedule a recurring meeting with teammates in both Denver and Phoenix without accounting for this, one group will be an hour off for half the year. Always double-check Arizona times, especially around the March and November transitions.
• Mixing up standard and daylight abbreviations. Using "MST" when you mean "MDT" might seem like a minor detail, but it can cause real confusion. MST is Mountain Standard Time (UTC-7, winter), and MDT is Mountain Daylight Time (UTC-6, summer). If you send a meeting invite for "2:00 PM MST" in July, someone who pays attention to the abbreviation will show up an hour later than you intended because they correctly interpreted MST as standard time, which doesn't apply in summer. The safer approach is to use generic abbreviations like "MT" for Mountain Time, or better yet, specify the UTC offset or use a tool that handles the conversion automatically.
• Assuming all devices update automatically. In the age of smartphones and cloud-connected laptops, it's easy to assume every device updates its clock automatically when DST hits. But desktop computers, older phones, smart watches, kitchen appliances, car clocks, and office equipment might not update automatically or might update at different times. If someone relies on a manually-set desk clock or an older car stereo, they might show up to meetings an hour early or late during DST transition weeks. This is particularly common on the Monday after the spring-forward change, when people drag themselves in an hour late because their bedroom alarm clock didn't auto-update.
• Ignoring the human impact of early morning meetings. It's tempting for east coast managers to schedule meetings at 9:00 AM Eastern — that's 6:00 AM Pacific, 5:00 AM Alaska time, and 3:00 AM in Hawaii. Expecting west coast teammates to regularly join meetings before 8:00 AM their time is a recipe for burnout and resentment. The fairest approach is to rotate meeting times so no single team always bears the burden of early mornings or late evenings. For coast-to-coast teams, the sweet spot is typically 11:00 AM Pacific / 2:00 PM Eastern — that's 10:00 AM Mountain and 1:00 PM Central, all within reasonable working hours for everyone.

How to Schedule Across US Time Zones Confidently

The first step to mastering cross-time-zone scheduling is to get clear on what time zones all your participants are in and whether each location observes daylight saving time. Make a quick reference list for your team: who's in Eastern, Central, Mountain, Pacific, Alaska, or Hawaii? Who observes DST and who doesn't? Having this written down prevents the "wait, what time is it for you again?" dance at the start of every meeting. Share a team document that lists everyone's location, time zone, and working hours. This is especially important for distributed teams that hire across the country.

Next, find a meeting time that works for the majority of people without forcing anyone into unreasonable hours. A good rule of thumb is to keep meetings within 9:00 AM to 5:00 PM local time for as many attendees as possible. If you can't find a time that works for everyone within standard hours, rotate the meeting time so the same people aren't always stuck with the 7:00 AM slot. For teams that span all four continental time zones, 10:00 AM Pacific / 1:00 PM Eastern is often the most equitable — that's 9:00 AM Mountain and 12:00 PM Central, all comfortably within working hours. If Hawaii or Alaska team members are involved, you may need to be even more creative or accept that occasionally some people will join outside their preferred hours.

Once you've identified a candidate time, always verify it with a reliable conversion tool. Don't trust mental math, especially around daylight saving transitions. Use our Time Zone Converter to double-check that 10:00 AM Eastern really is 7:00 AM Pacific and 9:00 AM Central on the specific date of your meeting. No sign up, no registration, instant calculation. The tool automatically accounts for daylight saving time in each location, so you don't have to remember who observes it and who doesn't. This is particularly valuable for meetings scheduled months in advance — a time that works today might shift by an hour after the next DST transition.

When you send meeting invitations, always include the time zone in the subject line or at the top of the description. "Team Sync — Tuesdays at 10:00 AM ET / 7:00 AM PT" is much clearer than just "Team Sync — Tuesdays at 10:00 AM." For recurring meetings, note that times are in Eastern Time (or whatever your reference zone is) and remind people that daylight saving may affect local times. Most calendar apps like Google Calendar and Outlook handle time zones well if you set them up correctly, but it's still worth explicitly stating the time zone to avoid confusion. If you're scheduling with people outside your company who might use different calendar systems, this is even more important.

Around DST transition weeks — the second Sunday of March and the first Sunday of November — send a quick reminder to your team about the time change. A short email or Slack message on the Friday before the weekend transition can prevent dozens of "why is no one on the call?" moments on Monday morning. Remind people to check their devices, especially any manually-set clocks or older equipment. And if you have recurring meetings, take a moment to verify that the meeting time still makes sense for everyone after the shift. A meeting that was 9:00 AM Pacific in standard time becomes 8:00 AM Pacific for your Arizona teammates once DST kicks in — a change that might push it outside their agreed-upon working hours.

For project managers and team leads, building time zone awareness into your team culture pays dividends. Encourage people to put their time zone and working hours in their calendar profile and Slack status. Use tools that display everyone's local time at a glance. Respect working hours boundaries — just because someone lives in a different time zone doesn't mean they're available 24/7. When you use the Time Zone Converter to plan meetings thoughtfully, you show your team that you value their time and their work-life balance. That kind of respect builds trust and makes remote work sustainable for the long haul.

Conclusion

Time zones and daylight saving time are two of those everyday things that seem simple on the surface but get surprisingly complicated once you dig in. For remote teams spread across the United States, getting time zone scheduling right isn't just about avoiding missed meetings — it's about building a respectful, inclusive work culture where nobody feels like they're always accommodating someone else's schedule. The four continental time zones, DST transitions twice a year, Arizona's unique status, and Hawaii's year-round standard time create a maze of scheduling challenges that trip up even experienced managers.

The good news is that with a little knowledge and the right tools, you can navigate these challenges confidently. Know your time zones, understand when DST starts and ends, remember the exceptions, and always verify meeting times with a reliable converter. Building time zone awareness into your team's culture — with clear working hours, rotating meeting times, and explicit time zone labeling — will save countless hours of frustration and make your remote team stronger. The next time you're scheduling a cross-country meeting, take thirty seconds to double-check the conversion. Your teammates in Phoenix, Honolulu, and Denver will thank you.

Authoritative References

Time-zone and DST rules are maintained by time.gov (NIST/USNO). DST dates follow the Energy Policy Act of 2005. This article is informational only.