Skip to content

Daylight saving changes and your meeting: the two weeks that break calendars

Why meetings go wrong twice a year, which regions change when, and a checklist for scheduling across a clock change.

Published 1 November 2026

Share this guide

Twice a year, a meeting that has run at the same time for months suddenly has half the room arriving an hour early or an hour late. Nobody changed the invitation. What changed was the clock in one country and not another, and for a stretch of two or three weeks the usual gap between two cities is simply wrong. This article explains why, says which regions change when as far as can be stated with confidence, and ends with a checklist for scheduling anything that falls inside a clock change.

Why the problem is the gap, not the change

If every place moved its clocks on the same night, daylight saving would be harmless for meetings: the time would shift for everyone at once and the relative positions would hold. The trouble is that regions change on different dates, and many regions do not change at all. So the offset between two cities is not a fixed number. It has a summer value, a winter value, and two awkward windows each year when one side has moved and the other has not.

Take London and New York. For most of the year they are five hours apart. In March, the United States moves its clocks forward about a fortnight before the United Kingdom does, so for those two weeks the gap is four hours. In the autumn the United Kingdom moves back a week before the United States, so for about a week the gap is again four hours. A weekly call set at 15:00 London, 10:00 New York, is correct for forty-eight or forty-nine weeks and wrong for three or four, and the wrong weeks are not the same each year.

Now add a city that never changes. Nairobi stays on the same offset all year. London is three hours behind Nairobi in winter and two hours behind in summer. A standing call at 13:00 Nairobi lands at 10:00 London from late October to late March and at 11:00 London the rest of the year. One side of that call sees the time move; the other sees it stay put; both are right.

Who changes when

The dates below are the rules in force at the time of writing for the regions where they are well established. Governments do change these rules, sometimes at short notice, so for anything important check the specific year rather than relying on the pattern. The time zone guide covers the same boundaries from the organiser's side; this article is about what happens to a meeting that straddles one.

  • European Union and United Kingdom: clocks go forward on the last Sunday of March and back on the last Sunday of October. The whole bloc changes at the same instant, so gaps within Europe hold.
  • United States and Canada: forward on the second Sunday of March, back on the first Sunday of November. A few places inside those countries do not observe it at all, so a colleague's city can matter more than their country.
  • Australia: some states change and some do not, and the ones that do run on the southern hemisphere calendar, going forward in their spring and back in their autumn. The gap between a changing Australian city and a changing European one therefore moves twice in each direction over the year. Check the dates for the year, and check the state as well as the country.
  • New Zealand: also changes on the southern calendar, on dates of its own that do not match Australia's. Check the dates for the year.
  • Most of Africa and Asia, and much of South America: no change at all. Nairobi, Lagos, Johannesburg, Delhi, Singapore, Tokyo and Shanghai keep the same offset all year. For these cities, the "change" they experience is entirely other people's.

Several countries have abolished or reinstated daylight saving in recent years. If a participant is somewhere not listed above, ask them or look it up for the specific date.

The two windows that break calendars

Put the northern hemisphere rules together and the danger zones are easy to name. From the second Sunday of March to the last Sunday of March, North America has changed and Europe has not. From the last Sunday of October to the first Sunday of November, Europe has changed and North America has not. Those are the two windows in which a meeting between the two regions is most likely to go wrong, and they are the windows in which a meeting with a non-changing region is wrong for one side only.

A concrete case. A team spread across Toronto, Dublin and Nairobi has a weekly call that everyone thinks of as "Tuesday at 14:00 Dublin". In the second half of March, Toronto has moved and Dublin has not, so the Toronto participants, whose calendar entry was created when the gap was five hours, now see the call an hour out. Nairobi has not moved and never will, so its participants see the Dublin time drift by an hour at the end of March and again at the end of October. Three cities, three different experiences of the same meeting, and no one did anything wrong.

Why calendar invitations usually cope, and when they do not

A proper calendar invitation stores the event in a named time zone, not as a bare clock time. When the organiser's zone changes its clocks, the calendar software on each attendee's machine recalculates the local time, and most of the time this just works. The failures come from three places.

  1. The time was shared as text. "Tuesdays at 2 p.m." in a chat message carries no zone. Each reader converts it once, writes it into their own calendar in their own zone, and from then on their entry and yours drift apart twice a year.
  2. The event was created in a floating or UTC time. Some tools store times without a zone, or in UTC, which never changes. An event stored that way stays fixed while everyone's local clock moves around it, so it appears to shift for everyone.
  3. The organiser's zone is not the meeting's real anchor. If the meeting exists to suit a participant in a non-changing city, and the invitation is anchored to a changing one, the meeting will move for the very person it was meant to suit.

The first failure is by far the most common and the easiest to prevent: never share a recurring time as text alone.

A checklist for scheduling across a clock change

  • Before proposing times, check whether any date you are considering falls inside a change window for any participant. The second half of March and the last week of October are the ones to watch for Europe and North America.
  • Name one city as the anchor and write it beside every time you propose: "Thursday 16:00 Berlin", not "Thursday at 4".
  • If the group includes a non-changing region, consider anchoring there, since that is the only place where the time will mean the same thing all year.
  • For a recurring meeting, decide in advance whether the time is fixed in the anchor city or fixed for everyone else, and say so. One of the two groups will see it move; pick which. (A group that polls afresh each cycle, as the guide to recurring meetings suggests, gets to revisit the choice twice a year.)
  • Send the final time as a calendar invitation with the zone embedded, and ask people not to retype it into their own calendars.
  • A week before each change window, send a one-line note to the group: "Clocks change in Europe this weekend; our call stays at 16:00 Berlin, so it moves an hour for Toronto and Nairobi." A sentence now saves an hour of confusion later.

When you use FINDaTIME to find the time in the first place, every proposed slot carries a named anchor zone and voters can view the slots in their own zone. The conversion is done once, correctly, before anyone votes, and the booked slot goes to the calendar with its zone attached. Create a free poll and let the zone travel with the time.

Share this guide