US–UK DST mismatch: check each recurring meeting date
New York and London change their clocks on different dates. A meeting anchored at 09:00 New York usually appears at 14:00 London, but appears at 13:00 during the mismatch intervals. The number of affected weeks changes by year.
Worked example to check against your calendar
| Year | 09:00 New York displays 13:00 London | Mismatch duration at that hour |
|---|---|---|
| 2026 spring | 8–28 March | 21 days |
| 2026 autumn | 25–31 October | 7 days |
| 2027 spring | 14–27 March | 14 days |
| 2027 autumn | 31 October–6 November | 7 days |
Use the actual year’s transition dates
US Naval Observatory guidance describes the US changes on the second Sunday in March and first Sunday in November. GOV.UK lists the UK dates: 29 March and 25 October in 2026; 28 March and 31 October in 2027.
For a 09:00 New York occurrence, the spring mismatch dates are 8–28 March 2026 and 14–27 March 2027, inclusive. The autumn dates are 25–31 October 2026 and 31 October–6 November 2027. A weekly meeting is affected only if it actually occurs within those ranges.
Decide which wall clock is anchored
Inspect the event’s own time zone, not just the organizer’s location or your calendar grid. An explicitly New York-zoned series can hold 09:00 there while London’s display changes. A UTC-anchored series follows a different rule. Do not infer the anchor from the person who sent the invitation.
Google’s computer help documents an event Time zone control. For other providers, inspect their event details and documentation rather than assume the same path. If both offices want unchanged local hours, no single instant can preserve both hours while the offset changes; agree which occurrence needs an exception.
Check before changing the series
Open an ordinary occurrence and one inside each mismatch interval, then compare both cities and the calendar date. Send the organizer the specific date, zone and expected local time rather than a vague one-hour correction request.
If you own the event and make an agreed exception, verify its edit scope and the next ordinary occurrence. Do not shift the whole series to fix one week. The examples use current rules and a time after each transition; recheck future policy changes.
What it looks like
Cloud Calendars overview, using our product images. Provider settings and protocol examples described in this guide are separate from the screens shown here.
What to do
- Identify the event’s zone and the year.
- Open one ordinary and one affected occurrence in both cities.
- Agree which city’s wall clock takes priority.
- Check the scope of any exception and the following occurrence.
Questions
- Are there always four mismatch weeks?
- No. These ranges total four weeks in 2026 and three weeks in 2027.
- Will setting the organizer’s calendar to London fix it?
- A display setting is not the event’s recurrence anchor. Inspect the actual event time zone.