Why Your Recurring Meeting with Europe Shifts by an Hour Twice a Year

If you have a recurring meeting across the Atlantic, it silently shifts by one hour twice a year. Not because anyone changed the invite — because the US and EU switch their clocks on different dates.

This is one of the most reliable causes of missed meetings between American and European teams, and it catches people every year.

The mismatch window

Spring:

• US moves clocks forward: second Sunday of March
• EU moves clocks forward: last Sunday of March

The gap is typically 2–3 weeks. During that window, the US is already on summer time but Europe is still on standard time — so a recurring meeting appears one hour earlier for the European participant than it did the week before.

Autumn:

• EU moves clocks back: last Sunday of October
• US moves clocks back: first Sunday of November

Same gap, same problem, in reverse.

What this looks like in practice

Say you have a recurring call at 4pm EST / 10pm CET every Tuesday.

For those 2–3 weeks in March, someone will be an hour off. Whether it’s the US or EU participant depends on how the invite was set up.

The same mismatch happens in late October / early November, with Europe switching first.

How to protect recurring meetings

Review all your recurring transatlantic calls in early March, before the US spring forward. If the invite is anchored to a local time (“4pm EST every Tuesday”), it will not auto-adjust for the mismatch window.

The most reliable fix: set the event in the calendar of the party who doesn’t move clocks, or anchor the invite to UTC and include both local times in the description.

At minimum, send a message the week of the US clock change reminding European participants that the meeting will appear one hour earlier for the next two or three weeks.

Use meetwhen to check the current live offset between your city and any European city — it always reflects the actual offset right now, not a cached calculation from when you last looked.