How long does daylight saving time affect meetings after the clocks change?

It affects cross-region meetings for weeks, not one day. Because the US and Europe usually change on different weekends, a meeting that fit in the morning for weeks suddenly lands with someone in a dark room for two or three weeks after the first switch.

Why does one DST date change my meetings but another one does not?

A meeting only shifts when the two zones are no longer synchronized. If both regions changed on the same weekend, their mutual difference stays the same. It is the staggered switch — the US moving while Europe waits — that changes the offset between them and moves the call.

What should I do the week after DST starts?

Re-verify every recurring cross-zone meeting in the first week and confirm each attendee saw the local time on their own calendar. Tighten the overlap window around the shifted times, and recheck the schedule again after the second region switches.

How DST Quietly Breaks Your Meeting Schedule

The second Sunday of March hits, the US springs forward, and for the next three weeks your Tuesday call silently moves. Same invitation, same start time on your calendar — but the person in Berlin is now one hour later relative to you. Nobody typed a wrong time. The clocks just disagreed.

DST is rarely a one-day event for a distributed team. It is a slow ripple that lasts weeks, and it bites the moment two regions switch on different weekends.

The staggered switch is the villain

Most of the US moves to daylight time on the second Sunday of March and back on the first Sunday of November. Most of Europe switches on the last Sunday of March and the last Sunday of October. That gap between the schedules is where meetings break.

Region	Clocks forward	Clocks back
United States	2nd Sun · March	1st Sun · November
Europe	Last Sun · March	Last Sun · October
Australia	1st Sun · October	1st Sun · April

From mid-March to late March, New York and London do not line up the way your calendar thinks. What was a comfortable overlap now has one side waking up an hour earlier, and the difference can last two to three weeks depending on your pair of zones.

Why your fixed meeting moves on its own

Most calendars store a recurring meeting as a single wall-clock time — 15:00 New York. When New York changes but London has not, that 15:00 suddenly means a different moment in London. Your invitation is technically correct; the global map around it is not. This is why "just keep the same time" is bad advice across a DST boundary.

The offset between the two zones is the only number that matters — see the offset versus DST distinction explained.

Surviving both weekends in three moves

Verify the week after each switch. Re-read every recurring cross-zone meeting within the first few days, while the mismatch is fresh.
Confirm the local time per attendee. A shared time without a zone is meaningless. Make each person read their own calendar so the on-screen time reflects their device.
Tighten the overlap. If the shifted window feels thin, shrink the meeting or rotate whose morning is eaten. Re-check once more after the second region flips.

You can check the current offset for any region in seconds on the HourSwift converter, where zones actually on DST are tagged and every target zone re-reads its live offset. For the broader fix, find a slot that survives US, Europe and Asia together.