Daylight Saving Time Impact on Schedule
See a time zone's daylight-saving transition dates, the next clock change (spring forward / fall back), and how it affects schedules. Live IANA data. Runs in your browser.
- โฉ Spring forwardMar 8, 2026
- โช Fall backNov 1, 2026
- โฉ Spring forwardMar 14, 2027
Transition dates are detected from your browserโs IANA time-zone data by finding where the UTC offset changes. Spring forward skips an hour (a 23-hour day; a 02:00โ02:59 appointment doesnโt exist), and fall back repeats an hour (a 25-hour day; 01:00โ01:59 happens twice). When scheduling across the change, recurring meetings tied to a fixed local time shift by an hour relative to other zones until they also transition. Everything runs in your browser.
About this tool
Daylight saving time (DST) shifts the clock twice a year in many regions, and those transitions quietly wreak havoc on schedules, recurring meetings, alarms, and any system that assumes every day has 24 hours. This tool shows, for a chosen time zone, whether it observes DST at all and, if so, the dates of its clock changes for this year and next, highlighting the next upcoming transition and what it does. It works by reading your browser's IANA time-zone database and scanning forward day by day to detect where the UTC offset changes โ so it reflects each region's actual current rules rather than assumptions, and correctly reports zones that don't observe DST (much of Asia, Africa, Arizona, Hawaii) as having no transitions. Two kinds of transition matter. 'Spring forward' moves clocks ahead an hour, producing a 23-hour day in which a slice of local time simply doesn't exist โ in the US that's typically 02:00 jumping to 03:00, so a meeting set for 02:30 that day has no valid moment. 'Fall back' moves clocks back an hour, a 25-hour day in which an hour repeats โ 01:30 happens twice โ which can double-fire schedulers or create ambiguity in timestamps. The schedule impact people most often hit is cross-zone drift: because regions change on different dates (the US and EU switch on different weekends, and the Southern Hemisphere is offset by six months), a recurring call pinned to a fixed local time will shift by an hour relative to participants in other zones during the gap between their transitions. Knowing the exact dates lets you warn attendees, re-confirm international meeting times, and avoid scheduling anything in the non-existent or doubled hour. Everything runs in your browser; nothing is uploaded.
How to use it
- Select a time zone.
- See whether it observes DST and the next clock-change date.
- Note whether it's a spring-forward (lose an hour) or fall-back (gain an hour).
- Review the year's transition dates to plan recurring and cross-zone meetings around them.
Frequently asked questions
- When does the clock change in my time zone?
- Select your zone to see the transition dates. The tool reads your browser's IANA data and reports the next spring-forward and fall-back dates, or tells you the zone doesn't observe DST.
- What is the difference between spring forward and fall back?
- Spring forward moves clocks ahead one hour (a 23-hour day; an hour of local time is skipped). Fall back moves them back one hour (a 25-hour day; an hour repeats). The tool labels which is next.
- How does DST affect scheduling across time zones?
- Because regions switch on different dates, a meeting fixed to one zone's local time drifts by an hour relative to other zones until they also change. Re-confirm international meeting times around the transition weekends.
- What happens to a meeting set during the skipped hour?
- On spring-forward day, times like 02:30 (in US zones) don't exist โ schedulers may move it forward or error. Avoid scheduling in the transition hour, and check anything already set there.
- Which places don't observe DST?
- Much of Asia and Africa, plus US locations like Arizona (except the Navajo Nation) and Hawaii. The tool flags these as having no transitions and a fixed year-round offset.
- Is anything uploaded?
- No. Transition detection uses your browser's built-in time-zone data and runs entirely locally.