The 3-Week DST Gap: Why Your US-Europe Meetings Break Every March (and How to Fix It)

Here's a scenario that plays out in thousands of Slack channels every March: your 3 PM London / 10 AM New York standup runs fine on Monday. By Tuesday it's mysteriously become a 3 PM London / 11 AM New York meeting. Nobody moved it. Nobody sent an update. The calendar still says 10 AM. But the clocks disagree.

This is the DST gap — a recurring scheduling trap that hits every remote team working across the US and Europe. It happens because the two regions change their clocks on different dates, creating a multi-week window where the time difference is temporarily off by one hour. And because most calendar tools anchor meetings to local times rather than UTC, they silently shift on one side without showing any change on the other.

What is the DST gap, exactly?

Daylight Saving Time (DST) isn't a global event — different countries change their clocks on different dates, governed by their own laws. The United States typically springs forward on the second Sunday of March. Most of Europe follows on the last Sunday of March. That 2–3 week difference is the gap.

During the gap, a New York–London pair that's normally 5 hours apart temporarily becomes 4 hours apart (because New York has moved forward but London hasn't yet). For teams with recurring weekly meetings, this means every meeting booked before the US transition hits at the wrong local time for the US participants during the gap — then snaps back once Europe catches up.

The same gap, in reverse, happens in autumn. The US falls back first (first Sunday of November), and Europe follows about a week later. The window is shorter in autumn — about a week rather than three — but the disruption is identical.

2026 DST transition dates: the calendar you need

The following table shows the exact 2026 clock-change dates for the major regions that observe DST. Use this to identify which weeks your team is at risk.

Which timezone pairs are affected during the gap?

The disruption is not random — it follows a clear pattern based on which side of your pair observes DST and when. Here's a breakdown of the most common remote-work corridors and what happens to their offset during March 2026:

Which pairs are unaffected: the DST-free corridors

Some timezone corridors are much simpler to manage because one or both sides never change their clocks. These pairs have a stable, year-round offset with only a single shift point — when the DST-observing side changes.

• Any US city ↔ India (IST): India never changes. The offset simply shifts once when the US does (Mar 8 and Nov 1).
• Any US city ↔ Japan (JST): Japan never changes. Same single-shift pattern.
• Any US city ↔ Nigeria/Lagos (WAT): Nigeria never changes. The offset only moves when the US changes clocks. See our guide on scheduling meetings between New York and Lagos for a full breakdown.
• UK ↔ Germany / France / Spain: Both change on the same date (last Sunday of March / October), so the offset between them never changes.
• India ↔ Japan: Neither observes DST. The offset is fixed at 3.5 hours, always.

The 4-step fix for remote teams

You can't stop the clocks from changing, but you can stop recurring meetings from quietly breaking. Here's a simple process to run before each DST transition.

Step 1: Audit recurring meetings two weeks before each transition

Run a calendar search for all recurring meetings that involve people in different DST regions. Flag any that span a US-Europe or US-Australia boundary. These are your high-risk meetings.

Step 2: Visualise the new overlap window

Use a timezone overlap visualiser like SyncZones to see your team's shared business hours under the new offset. During the March 8–28 gap, the US-Europe overlap window narrows by one hour. For teams already squeezed into a 2–3 hour working overlap, losing an hour can mean losing your only viable meeting slot.

Step 3: Send a one-time heads-up to affected teammates

A simple Slack message goes a long way: "Heads up — from March 8, our 10 AM ET standup will feel like 3 PM your time instead of 4 PM (UK). This lasts until March 29 when UK/EU clocks catch up. No calendar change needed — just be aware the local time shifts for three weeks." Include a shared SyncZones link so everyone can see the overlap visually.

Step 4: Consider UTC-anchored scheduling for critical meetings

For meetings that must stay at a consistent time regardless of DST — engineering syncs, client calls, board updates — consider scheduling them in UTC. Any calendar app can display a UTC-anchored event in local time, and it will adjust automatically as clocks change. This doesn't fix the gap, but it moves the cognitive burden from "which slot survives the transition" to "what UTC time works for everyone year-round."

Frequently asked questions

Does the DST gap affect Google Calendar and Outlook?

Yes and no. Both apps anchor events to the local time of the creator by default. If you book a meeting as "10:00 AM New York" and share it with a London colleague, the London side will show the correct offset — but during the gap, that offset changes. Most calendar apps handle the transition date correctly once it passes; the problem is meetings booked before the transition that span the gap period without any human review.

My meeting time changed by an hour and I didn't change anything — what happened?

Almost certainly a DST transition occurred on one side but not the other. Check whether your location or your colleague's location recently changed clocks. If the offset is temporarily one hour different from usual, you're in the gap window described in this article.

Is the US ever going to stop changing clocks?

The US Senate passed the Sunshine Protection Act in 2022, which would have made DST permanent, but the bill stalled in the House and has not become law as of 2026. Until legislation passes and takes effect, US clocks will continue to change twice a year.

What about Arizona?

Arizona (except the Navajo Nation) does not observe DST. Phoenix stays on Mountain Standard Time (MST, UTC−7) year-round, so it behaves like a DST-free city for scheduling purposes. During US summer, Phoenix and Denver/Salt Lake City are actually in different effective offsets despite being in the same "Mountain Time" zone.