United States daylight saving time still moves clocks twice a year for most states and territories that observe it. For 2026, the spring-forward and fall-back Sundays are fixed by federal rule: clocks advance on the second Sunday in March and return on the first Sunday in November. If your team schedules across U.S. zones or explains American meeting times to colleagues abroad, those two weekends deserve a place on the calendar long before they arrive.
This guide lists the 2026 dates, names the places that opt out, and covers the failure modes that turn a one-hour mistake into a missed flight or a standing call at the wrong time.
2026 spring-forward and fall-back dates
In 2026, daylight saving time in most of the U.S. begins at 2:00 a.m. local time on Sunday, March 8, 2026. Clocks skip from 1:59 a.m. to 3:00 a.m. in participating areas. That night, Americans lose an hour of sleep and gain an extra hour of evening daylight until autumn.
Daylight saving time ends at 2:00 a.m. local time on Sunday, November 1, 2026. Clocks fall back from 1:59 a.m. to 1:00 a.m., repeating the 1:00–1:59 a.m. hour once. Sunrise feels earlier; afternoon darkness returns sooner.
These dates follow the Energy Policy Act pattern used since 2007. They are not tied to Easter, school terms, or weather. Mark them now for recurring meetings, on-call rotations, and travel connections that span multiple U.S. zones on the Monday after each transition.
Who does not change clocks
Not every U.S. location springs forward. Hawaii observes Hawaii-Aleutian Standard Time year-round and does not use DST. Most of Arizona stays on Mountain Standard Time all year; Phoenix does not shift with the rest of the Mountain zone in summer. The Navajo Nation in northeastern Arizona does observe DST, which creates a local patchwork worth remembering if you drive or meet across tribal boundaries.
Puerto Rico, the U.S. Virgin Islands, Guam, American Samoa, and the Northern Mariana Islands also skip the twice-yearly change. A remote worker in San Juan keeps the same offset relative to UTC all year, while a colleague in Atlanta does not.
Indiana historically confused outsiders; today most of the state follows DST with the rest of the eastern United States, but older documentation still lingers online. When in doubt, label invites with a city name and verify against a current zone map rather than memory from a decade ago.
How calendar apps get this wrong
Calendar software usually handles DST correctly when events store a proper time zone identifier. Problems appear at the edges. Editing a recurring series on the transition weekend itself can duplicate or drop an hour depending on client bugs. Floating times (“10:00 with no zone”) follow the device clock and drift when the laptop time zone is set to “automatic” while traveling.
All-day events sometimes shift for viewers in other regions because providers interpret midnight boundaries differently. Video conferencing links rarely break, but the human-readable time in email notifications can disagree with the join button for one week after a bad edit.
Mitigations that actually work: create recurring meetings with an explicit zone such as America/New_York, not a generic EST label; avoid bulk-editing series on the Sunday clocks change; and spot-check March and November instances individually after saving. For critical external calls, send a confirmation that states both local times and UTC once each quarter.
What to tell international teammates
Colleagues outside the United States often experience American DST as sudden one-hour shifts in overlap with no local change on their side. A standup that was comfortable at 6:00 p.m. in London may become 7:00 p.m. local for two weeks until Europe starts its own summer schedule, or vice versa in autumn.
Plain-language briefing you can paste into Slack:
- Most U.S. states advance clocks one hour on March 8, 2026, and revert on November 1, 2026.
- Arizona (except Navajo Nation) and Hawaii do not move.
- Our meeting series labeled America/Chicago will shift automatically; if your tool shows only “CST,” ask us for a city-labeled invite.
- UTC times on the wiki stay stable; local U.S. wall times jump once on each date above.
International teams should prefer UTC in runbooks and incident channels, then translate to local for customer comms. That split reduces surprise when only the American half of a roster moves.
Quick checklist the week before the change
One week before March 8 and again before November 1, run through this list:
- Open the next four instances of each recurring U.S. meeting and confirm start times in every participant city.
- Update on-call handoff docs if shifts are described in local time without zone IDs.
- Reconcile flight and hotel confirmations; airline systems know DST, but human-written itineraries often do not.
- Notify customers who join from non-DST regions if your support hours shift on the wall clock.
- Check automated reports and cron jobs that use local timestamps instead of UTC.
- Post a single team reminder with both transition dates and a link to your canonical U.S. zone reference.
See current U.S. offsets and city lists on the United States time zone page.
Daylight saving time in 2026 is predictable if you treat March 8 and November 1 as infrastructure events, not surprises. Document who opts out, fix calendar labels before they drift, and tell international partners exactly which American clocks move so everyone stays aligned for the rest of the year.