How clock changes alter shared working hours in 2026

Original analysis by SYNCDATE. Calculations and primary sources checked on 30 October 2026.

Eleven of twelve Europe–US city pairs gain one modeled shared office hour per weekday during 26–30 October 2026. This assumes both offices work 09:00–17:00 local time. Every pair returns to its earlier overlap on 2 November.

For London and New York, the shared window grows from three hours to four, then returns to three. London and San Francisco gain a one-hour window during the gap week. That window disappears the following Monday.

SYNCDATE conducted this original model using public time-zone rules. We calculated 180 city-pair weekdays across three weeks. These results describe modeled shared office hours. They do not measure free calendar slots, meetings or productivity.

Main findings from the clock-change model

The temporary gain affects eleven pairs; Berlin–San Francisco remains at zero throughout the model.

• London–New York: 3 → 4 → 3 shared hours per weekday. Lisbon–New York follows the same pattern.
• London–San Francisco: 0 → 1 → 0 shared hours per weekday. Lisbon–San Francisco follows the same pattern.
• Berlin–Denver: 0 → 1 → 0 shared hours per weekday. The gap week creates a window within the assumed office hours.
• Four pairs have zero overlap before the gap week. Only Berlin–San Francisco still has zero during that week.

These are exact outputs under the stated assumptions. They are not estimates from a sample of workers. The complete results CSV includes every calculated weekday, including rows with zero overlap.

Why Europe and the US have a gap week in 2026

The selected European cities move clocks back on 25 October 2026. The four selected US cities move clocks back on 1 November.

GOV.UK lists 25 October for the UK change. The UK rule uses the last Sunday in October. The European Commission schedule, published by Spain’s official gazette, gives the same date for EU summer time.

Portugal’s IPMA explains the mainland transition. Germany’s Hamburg city portal confirms its 2026 change. Both support the Lisbon and Berlin dates used here.

NIST says US daylight saving time “ends at 2:00 a.m. on the first Sunday of November.” Its 2026 guidance gives 1 November.

For 26–30 October, London is four hours ahead of New York instead of five. Berlin is five hours ahead instead of six. The smaller difference increases the overlap where the two office windows reach each other.

The repeated hour on Sunday does not become an extra office hour on Monday. The result comes from different UTC offsets during the five weekdays between the changes.

Shared working hours for all twelve city pairs

Eleven pairs gain one hour per weekday during the gap week. The table gives the full result, including the pair with no gain.

Modeled shared office hours per weekday, 2026. Both cities work Monday–Friday, 09:00–17:00 local time. Each row names a city pair. Values apply to every weekday in each column’s date range.

Source: SYNCDATE model, checked 30 October 2026. Download the twelve-pair summary or the full 180-row dataset.

An overlap of zero means no positive-length interval falls inside both office windows. It does not mean colleagues cannot meet. A different workday, an agreed exception or an asynchronous handoff changes the scheduling options.

Berlin–San Francisco illustrates the boundary. During the gap week, 09:00 in San Francisco is 17:00 in Berlin. One office opens exactly when the other closes, so shared office time remains zero.

What the extra hour looks like in a calendar

London–New York’s shared window begins one hour earlier in London during the gap week. It ends one hour later by New York’s clock. The New York office still opens at 09:00 local time.

On 23 October, London’s office hours are 08:00–16:00 UTC. New York’s are 13:00–21:00 UTC. Their intersection is 13:00–16:00 UTC: 14:00–17:00 in London and 09:00–12:00 in New York.

On 30 October, London’s office hours become 09:00–17:00 UTC. New York’s remain 13:00–21:00 UTC. Their intersection grows to 13:00–17:00 UTC: 13:00–17:00 in London and 09:00–13:00 in New York.

On 2 November, New York’s office hours become 14:00–22:00 UTC. The intersection returns to three hours: 14:00–17:00 in London and 09:00–12:00 in New York.

A one-hour call starting at 12:00 New York time fits both modeled workdays on 30 October. The same local start on 2 November is 17:00 in London. The call would start when the London office closes.

For London–San Francisco, the temporary window is 16:00–17:00 in London and 09:00–10:00 in San Francisco. It exists on every modeled weekday from 26 through 30 October. On 2 November, 09:00 in San Francisco is 17:00 in London, so that window closes.

How to schedule across the clock changes

Check the actual dates on both sides of each change before you confirm a recurring meeting. A window that fits the gap week can fall outside office hours the following week.

1. Compare three dates. For this period, use 23 October, 30 October and 2 November 2026. Check each attendee’s local start and end time.
2. Choose the meeting’s anchor city. Decide whose local time the series should follow. Use a named time zone, such as Europe/London or America/New_York, where your calendar supports it.
3. Inspect the actual occurrences. Open the series before, between and after the changes. Confirm that the calendar’s recurrence settings give the intended local times.
4. Use real working hours. Add lunch, local holidays, part-time schedules and booked events before you treat any modeled window as bookable.
5. Give temporary arrangements an end date. A London–San Francisco call in the gap-week window needs a fresh check for 2 November.
6. Agree on an alternative when overlap is zero. Consider written updates or a time outside office hours that all attendees accept.

A calendar’s second time-zone display or world clock can be enough for this check. Calendar synchronization cannot increase the shared office hours created by time-zone rules.

If your week spans several calendar accounts, our guide to viewing calendars in one place covers the separate visibility task. If you use SYNCDATE’s Working hours filter, read which time zone the filter uses. That filter uses each event’s own time zone; it does not calculate shared office hours between people.

Method and reproducible data

We calculated the UTC intersection of two local office windows for each city pair and weekday. The model covers 19 October through 6 November 2026, inclusive.

We selected Lisbon, London and Berlin in Europe, and New York, Chicago, Denver and San Francisco in the US. This gives twelve pairs across fifteen weekdays: 180 rows.

For each row, we:

1. Created a 09:00 start and 17:00 end in each city’s local time zone.
2. Converted both office windows to UTC using Python’s zoneinfo module.
3. Took the later start and the earlier end.
4. Recorded the positive difference in hours, or zero when the windows did not overlap.

In compact form: shared hours = max(0, earlier UTC end − later UTC start).

The calculation used Python 3.14.6 and the system IANA-derived time-zone database, version 2026e. We saved the seven zone identifiers and file hashes in the model metadata. Python’s documentation explains its time-zone data sources.

We reproduced all 180 rows of the pilot model. We also checked every UTC interval against separate arithmetic using the published transition dates and fixed UTC offsets. We checked all five weekdays in each table column before summarizing them.

The calculation script uses Python’s standard library. The research README and data dictionary gives the commands and data definitions. For one download, get the complete reproducible package (.zip). Extract it before running the script; it includes the pilot inputs and method notes.

The raw CSV includes the date, both city names, their zone identifiers, overlap duration and UTC boundaries. Zero-overlap rows have empty boundary fields.

Limits and disclosure

This analysis models a fixed workday under public clock-change rules. SYNCDATE, a calendar synchronization service, conducted the analysis for this article.

We used no customer calendars or personal event data. We did not survey workers or observe meetings. The results do not establish attendance, free slots, missed meetings, productivity or commercial outcomes.

The model excludes holidays, lunch breaks and part-time schedules. It also excludes booked events. A weekday in this dataset can be a local holiday, so the table is not a staffing forecast.

The cities are a selected set, not a representative sample of Europe or the US. The findings do not apply to every location or work pattern. Some US locations do not observe daylight saving time, as NIST’s guidance explains.

As of the analysis date, 2–6 November is a future period calculated from the published rules. Recheck the dates and time-zone data before using this model for another year.