Daylight Saving Time: A Practical Scheduling Guide

DST was originally introduced to make better use of natural daylight during summer evenings, reducing the need for artificial lighting. Clocks 'spring forward' by one hour in spring and 'fall back' in autumn. The practice dates to World War I and was standardised in many countries throughout the 20th century.

Most of North America and Europe observe DST, but on different dates. The United States switches on the second Sunday of March (spring) and the first Sunday of November (autumn). The European Union changes on the last Sunday of March and the last Sunday of October. Australia observes DST in its southern states, but in the southern hemisphere — so their summer is our winter, meaning their clocks shift in October and return in April.

Here's the practical consequence: a meeting at 9 AM in New York is 10 PM in Singapore on Tuesday 12 January 2027, but 9 PM in Singapore on Tuesday 16 March 2027, after the US clocks moved forward on 14 March. Nobody changed the calendar event; New York moved its clocks and Singapore did not. If your calendar app is timezone-aware (using IANA names like 'America/New_York'), the event stays at 9 AM in New York. If you used a fixed UTC offset like 'UTC-5', the meeting lands at the wrong local time after the change.

In 2019, the European Parliament voted to end mandatory DST across the EU by 2021, allowing each member state to choose whether to stay on permanent summer time or permanent winter time. However, the reform stalled due to coordination issues — neighbouring countries feared ending up on different offsets — and the practice continues.

Each ZoneMeets card shows the time and UTC offset that apply to the moment on screen, using the IANA time zone rules built into your browser. When you pin 'America/New_York', you see the correct local time whether it is currently standard or daylight time. A reminder banner at the top of the home page appears when your own device's time zone is due to change its clocks within 7 days. It does not watch the other cities you pin, so check their dates in the table below. The main converter starts from the current moment (the slider reaches 12 hours either side), so use the dated examples here to plan a meeting on a specific later date.

Always create calendar events using named IANA timezones, never fixed UTC offsets. Set reminders for the weeks around each region's clock change (in 2027: 14 March and 7 November in the US; 28 March and 31 October in the UK and EU) to audit any meetings that cross DST-active regions. And when in doubt, confirm the current time with ZoneMeets before dialling in.

Because the United States and the European Union change their clocks on different dates, there are a few weeks each year when the usual gap between their cities shrinks by an hour. In 2027 the US moves its clocks forward on Sunday 14 March, while the UK and EU wait until Sunday 28 March. For those two weeks New York is only four hours behind London instead of the usual five. In autumn the pattern reverses: the UK and EU fall back on Sunday 31 October and the US follows on Sunday 7 November, so for one week the gap is again four hours. Transatlantic meetings are the ones most likely to go wrong in these windows. An invite created with a fixed offset will appear an hour off, and attendees who memorized the normal five-hour difference will join at the wrong time. The fix is the same every time: use named time zones and double-check any US and Europe meeting that falls in the mismatch weeks.

The dated example further down shows a weekly 9:00 AM New York call with attendees in London and Singapore. The call did not move for its organizer; it moved for everyone else. That is correct behavior, but it surprises people who did not know a colleague's region was about to change its clocks. A short note to the group a week before each transition, explaining what will change for whom, prevents most of the confusion.

Even within countries that use daylight saving, there are exceptions. Arizona and Hawaii do not change their clocks, although the Navajo Nation inside Arizona does. In Australia, New South Wales, Victoria, Tasmania, South Australia, and the Australian Capital Territory observe daylight saving, while Queensland, Western Australia, and the Northern Territory do not. Lord Howe Island shifts by thirty minutes rather than a full hour.

Several countries have also abandoned the practice in recent years. Brazil ended daylight saving in 2019, most of Mexico ended it in 2022, and Turkey stays on a permanent UTC+3 offset. Because these rules are set by governments and can change with little notice, any tool that hard-codes a region's behavior will eventually be wrong. This is why ZoneMeets relies on the IANA time zone database, which is updated several times a year as governments change their rules.

Use this list in the two weeks before any transition that affects your team:

1. Identify which of your regions change their clocks, and on which dates. The US and EU dates differ.
2. List recurring meetings that include people from those regions.
3. Confirm each series was created in a named time zone, not a fixed offset.
4. Check which attendees will see the meeting move, and by how much.
5. Send a one-paragraph heads-up to those attendees.
6. After the change, open the first affected meeting and confirm that it shows the time you expected.

The table shows a meeting at 9:00 AM New York time on four Tuesdays in 2027. Singapore never changes its clocks (UTC+8). New York changes on 14 March and 7 November, London on 28 March and 31 October, so the three cities line up differently on each date.

Between January and March the meeting moves from 10:00 PM to 9:00 PM in Singapore, although nobody edited it. New York's offset changed from UTC−5 to UTC−4, so 9:00 AM New York became an hour earlier in UTC.

The table is computed from the time zone database in your browser, so it shows the rules your device knows. Dates move from year to year and governments can change the rules, so confirm anything important with your calendar.

The 2027 dates follow the published rules for each region. Dates in the table are computed in your browser from the IANA database.