When Europe turns its clocks back on Sunday, October 25, 2026, recurring meetings with U.S. colleagues can appear an hour earlier or later on one side of the Atlantic. The reason is a one-week gap: most European locations that observe seasonal clock changes switch to standard time on October 25, while most of the United States stays on daylight saving time until Sunday, November 1.
The invitation may still be correct. A calendar that knows the event’s time zone usually converts the same meeting into each attendee’s local time; the difference between those local clocks changes for a week. The practical check is to open the actual October occurrence and compare both cities’ times before you edit a recurring series.
The European Union’s current rule keeps seasonal clock changes: member states move to summer time on the last Sunday in March and return to standard time on the last Sunday in October. In 2026, that October date is the 25th. The United Kingdom follows the same autumn Sunday this year; its clocks go back at 2 a.m. British Summer Time to 1 a.m. Greenwich Mean Time. The EU’s plan to end seasonal clock changes has not become law: the Council says it has not agreed its position on the proposal, so the current directive still applies. The Council of the EU explains the current seasonal-time rule, and the UK government lists October 25, 2026, as its clock-change date.
Most U.S. locations that observe daylight saving time change later. The National Institute of Standards and Technology (NIST) lists the 2026 U.S. daylight-saving period as March 8 through November 1; at 2 a.m. local time on the first Sunday in November, clocks return to 1 a.m. The United States is not uniform, however: Hawaii, most of Arizona, and several U.S. territories do not observe daylight saving time. Confirm the city or time-zone label for each U.S. attendee instead of assuming that every American colleague follows the New York schedule. NIST’s 2026 schedule and exceptions are the authoritative reference.
It depends on which European and U.S. cities are involved. For a clear example, compare a 9:00 a.m. meeting in New York with London and Paris. New York is on Eastern Daylight Time (EDT, UTC−4) until November 1. London returns to Greenwich Mean Time (GMT, UTC+0) on October 25, while Paris and much of Central Europe return to Central European Time (CET, UTC+1) on that date.
| New York meeting time | London time | Paris time | What is happening |
|---|---|---|---|
| 9:00 a.m., through Friday, October 23 | 2:00 p.m. | 3:00 p.m. | Both sides still observe daylight saving time |
| 9:00 a.m., Monday, October 26–Friday, October 30 | 1:00 p.m. | 2:00 p.m. | Europe has changed; New York has not |
| 9:00 a.m., from Monday, November 2 | 2:00 p.m. | 3:00 p.m. | New York has also returned to standard time |
This is a worked example, not a promise that every calendar entry will show these exact labels. It assumes the meeting is anchored to 9:00 a.m. in New York and the European attendee is in London or Paris. During the workweek of October 26, the New York–London gap is four hours instead of the usual five; the New York–Paris gap is five instead of six. On November 1, the U.S. change restores those usual gaps for the cities in this example.
Usually, what changes is the local display for attendees in different zones, not an organizer manually moving the invite. A time zone is a named region with rules for its seasonal offsets, such as America/New_York or Europe/London. A properly zone-aware calendar can show one shared meeting at the corresponding local time for each person. Microsoft says Outlook stores meeting start and end times in Coordinated Universal Time (UTC) and displays them in each attendee’s local zone. Google Calendar likewise says an event appears in the invitee’s local time and converts event times to UTC.
That does not mean every calendar entry is immune to problems. The event may have been created with the wrong time zone, a fixed UTC offset, or a device whose time-zone data is outdated. Google also warns that some past or future events may not reflect daylight-saving changes correctly, particularly when time-zone rules have changed. Calendar behavior can vary by app and by how a recurring series was originally set up. Google’s time-zone guidance and Microsoft’s Outlook time-zone documentation explain how these conversions are handled.
Example: If a weekly call is defined as 9:00 a.m. in New York, that local start time can stay at 9:00 a.m. for its New York organizer. A London attendee may see 2:00 p.m. before Europe’s change, 1:00 p.m. during October 26–30, and 2:00 p.m. after the U.S. change. The invitation has not necessarily been rescheduled; the cities’ offsets temporarily differ by one hour.
First, open the specific occurrence dated October 26–31, not just the series summary. Read the time-zone label in the event details and compare the time shown for the organizer’s city with your own. If the event is a weekly series anchored to the organizer’s local time, the other city’s display may shift temporarily by one hour and then shift back when the United States changes clocks.
Next, check whether the organizer intended to preserve a local wall-clock time or a fixed instant. Those are different choices. “Every Friday at 9:00 a.m. New York time” means the event follows New York’s local clock; its UTC time changes when New York switches from EDT to Eastern Standard Time (EST). A meeting fixed to a particular UTC time instead stays at the same instant, but its local clock time changes when either city changes offset. If the invite does not make that distinction clear, ask the organizer before editing the series.
Finally, confirm the time directly with the other person if the meeting is important. A short note such as, “For Friday, October 30, I have 9:00 a.m. New York / 1:00 p.m. London. Is that what your invite shows?” catches misunderstandings without creating a duplicate or moving the whole series unnecessarily. If a meeting really must move, the organizer should update the invite so all attendees receive the same change.
For a New York–London meeting, expect the London display to be one hour earlier during the workweek of October 26–30 if the recurring event remains anchored to 9:00 a.m. New York time. From November 2, the usual five-hour difference returns. Check the event’s named time zone and the actual dated occurrence; do not manually move the full series just because one week looks different. Information checked September 28, 2026.
Europe turns clocks back October 25, 2026, a week before most of the U.S. changes on November 1. See how the gap affects London, Paris, New York, and recurring calendar meetings.
Windows 11 24H2 Home and Pro support ends October 13, 2026. Learn how to back up files, check 25H2 availability, avoid data-loss traps, and upgrade safely.
