Planning dates run from Thu, Jan 1, 2026 through Mon, Dec 31, 2035. Future rules can be revised; review the data version when a distant schedule matters.
More context and planning advice
The week between the autumn changes
London’s lead is four hours on 27 October 2026 and five hours on 3 November. A New York-anchored 09:00 meeting moves from 13:00 to 14:00 in London. Decide which city should retain its local start before exporting a weekly plan.
Compare the same local start on four dates
09:00 in London, resolved separately on each date with IANA 2026f. The final column describes New York relative to London.
London
New York
Time difference
2026-01-15 · 09:00
Thu, 15 Jan 2026 · 04:00
5 hours behind
2026-07-15 · 09:00
Wed, 15 Jul 2026 · 04:00
5 hours behind
2026-10-27 · 09:00
Tue, 27 Oct 2026 · 05:00
4 hours behind
2026-11-03 · 09:00
Tue, 3 Nov 2026 · 04:00
5 hours behind
Find a window for the whole meeting
For illustrative 09:00–17:00 hours, the shared window is 13:00–17:00 London on 27 October and 14:00–17:00 on 3 November. A 90-minute meeting fits both, but its latest permitted start changes. If Berlin joins, its earlier UTC finish further reduces the common window.
Make the plan specific
Enter each participant’s actual working days and hours. The 09:00–17:00 examples here are editable assumptions, not local business-hour facts.
Choose a duration from 15 to 240 minutes and check both local end times.
For a weekly meeting, choose one anchor city and review all twelve dates. Resolve repeated or missing local times explicitly.
Reversing the base city changes how you enter the meeting, not the pair’s information page. Share the configuration or export the resolved event after the participants agree on the time.