US–UK daylight saving mismatch weeks in 2027

The dates to check

New York and London change their clocks on different Sundays. Under the rules checked on 28 October 2026, New York moves forward on 14 March 2027 and back on 7 November. The UK moves forward on 28 March and back on 31 October. Other US locations can follow different rules, so choose a city rather than applying this table to the whole country.

For ordinary Monday–Friday meetings, the spring mismatch covers two workweeks, 15–26 March. The autumn mismatch covers 1–5 November. Sunday transition days need a specific time as well as a date: the two places do not move their clocks at the same UTC instant. The converter handles that detail for the chosen moment.

What happens to working-hour overlap?

Assume both participants work 09:00–17:00 on weekdays. With a five-hour difference, their common window is 09:00–12:00 in New York and 14:00–17:00 in London: three elapsed hours. During the four-hour mismatch, it becomes 09:00–13:00 in New York and 13:00–17:00 in London: four hours. These are example availability settings; holidays, lunch breaks and calendar bookings are not included.

A 90-minute meeting must fit completely inside that window. With the five-hour difference, 10:30 New York is the latest possible start before the London participant finishes at 17:00. During the mismatch, the latest start is 11:30 New York. A start time inside green working hours is not enough if the meeting ends outside them.

Compare your actual working days, hours and meeting length →

Choose which city keeps its local time

For a New York-anchored Tuesday meeting, 09:00 New York maps to 14:00 London on 9 March, 13:00 on 16 and 23 March, then 14:00 on 30 March. For a London-anchored meeting at 14:00, the New York hour changes instead. Agree which local clock is the commitment before creating calendar events.

1. Open the recurring planner and select the anchor city whose local time must stay fixed.
2. Start the twelve-meeting preview before a transition, for example Tuesday 9 March 2027. Set the agreed time and each participant’s working hours.
3. Inspect every dated row, including 16 March and 30 March. Review the autumn dates separately if they fall outside this twelve-occurrence preview.
4. Resolve any missing or repeated local time explicitly, then export the reviewed occurrences and check them in the destination calendar.

A download is a dated snapshot

HourBraid exports the resolved weekly occurrences as individual UTC events. It does not send invitations, sync later edits or create an unlimited repeating series. If a time-zone rule or your plan changes after download, review the new plan and manage old imports in your calendar application. Keep the project JSON as the editable backup.

Understand calendar exports and check an imported event →

Scope and rule changes

This guide concerns New York and London under the bundled 2026f rules, with planning supported for 2026–2035. Civil-time rules can change after publication. Check the data-sources page and official notices before relying on a future schedule. The static examples use weekday availability, not public-holiday or personal-calendar information.