Daylight Saving Time and Recurring International Meetings: The Twice-Yearly Shift
You join your weekly sync at the usual time and the room is empty. Nobody is late. The meeting moved an hour for half the team and nobody told anyone, because nobody moved it. Your calendar did exactly what it was told. The clocks changed, on different weekends, in different countries, and your recurring meeting is standing in a spot that no longer means what it meant in February. This happens twice a year, it surprises the same teams every time, and it is almost entirely preventable.
Why the shift happens
The trap is treating a time zone as a fixed offset. It is not. America/New_York is a set of rules that swings between UTC-5 and UTC-4, and Europe/London swings between UTC+0 and UTC+1. The two regions do not swing on the same weekends. The US springs forward on the second Sunday of March and falls back on the first Sunday of November. The UK and the EU spring forward on the last Sunday of March and fall back on the last Sunday of October.
That leaves gap weeks. In 2026, the US moved forward on March 8 while London waited until March 29, so for three weeks the New York to London gap was four hours instead of five. In the fall, London falls back on October 25 while New York waits until November 1, so for that week the gap is four hours again. And half the world never swings at all: India, China, Japan, and most of Africa sit on fixed offsets year-round. A 9:00 a.m. Eastern standup lands at 7:30 p.m. in Mumbai in winter and 6:30 p.m. in summer, shifting under the India team twice a year without a single person touching the invite.
| Window | What happens | NY-London gap |
|---|---|---|
| Mar 8 to Mar 29 | US on DST, UK/EU not yet | 4 hours (normally 5) |
| Mar 29 onward | Both on DST | 5 hours |
| Oct 25 to Nov 1 | UK/EU off DST, US still on | 4 hours (normally 5) |
| Nov 1 onward | Both off DST | 5 hours |
The habits that stop the phantom meeting
First, make sure the recurring event carries a time zone, not an offset. Google Calendar and Outlook handle the transitions automatically when the event is anchored to something like America/New_York. They cannot do that if the invite was built on a bare UTC-5. Most phantom meetings are not calendar bugs; they are people who memorized "2 p.m. my time" in February and stopped reading the invite.
Second, review your recurring meetings in the week before each transition. It takes ten minutes and it catches the one meeting that matters: the one with the client, the candidate, or the team that has no flexibility. Put the UTC time in the invite description while you are at it. "14:00 UTC" means the same thing on every continent on every date, and it ends the "wait, which 9 a.m.?" argument before it starts.
Third, rotate the pain deliberately. The DST shift usually makes an already awkward slot slightly worse for the same side twice a year. If your Mumbai colleagues absorb the evening hour in winter and the slightly less bad evening hour in summer, they never get the good season. Move the slot when the clocks change and say why. It is a small gesture and teams remember it.
There is an open question hanging over all of this, which is whether daylight saving time survives the decade. The EU has debated ending the clock changes for years without acting, and US bills to make daylight time permanent surface every Congress and stall. If the changes ever stop, this whole category of confusion disappears overnight. Until then, the twice-yearly drift is a calendar fact, and the teams that handle it are the ones that check their invites instead of their memories.
Find a time that survives the clock changes
Compare working-hour overlap across your team's cities before you lock in the slot.
Run your own numbers with the free toolFrequently asked questions
Why does my recurring international meeting shift an hour?
Countries change clocks on different dates. The US and the UK/EU spring forward and fall back weeks apart, so the gap between them is one hour different during the in-between weeks. Countries that never observe DST, like India, see the shift in their local time whenever the other side changes.
Which countries skip daylight saving time?
India, China, Japan, and most of Africa and Southeast Asia do not observe DST. Meetings with those countries always shift in local terms when the DST side changes its clocks.
Does Google Calendar adjust automatically?
Yes, when the event carries a named time zone like America/New_York. Each participant sees the correct local time. The failures come from people trusting their memory of the old local time instead of the invite.
When are the 2026 US-Europe gap weeks?
March 8 to March 29, when the US is on DST and the UK/EU are not yet, and October 25 to November 1, when the UK/EU have fallen back and the US has not. The New York to London gap is four hours in those windows instead of five.
How should I schedule recurring meetings across DST changes?
Anchor the event to a named time zone, review recurring meetings before each transition weekend, put the UTC time in the invite, avoid the changeover Sunday, and rotate the slot if one side always takes the awkward hour.
Related: Best Meeting Time Between the US and India · Best Meeting Time: Los Angeles to London · Best Meeting Time for Teams Across the US, Europe, and Asia · US to Europe Meeting Scheduling: The Complete Guide
One time-zone guide a month: subscribe to the newsletter.