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
Choose whose afternoon or morning stays fixed
A 15:00 Paris meeting is 10:00 New York on 27 October 2026 and 09:00 New York on 3 November. A New York-anchored 10:00 meeting instead becomes 16:00 Paris in the second week. Those are different recurring intentions, even though the first meeting could be identical.
Compare the same local start on four dates
09:00 in Paris, resolved separately on each date with IANA 2026f. The final column describes New York relative to Paris.
Paris
New York
Time difference
2026-01-15 · 09:00
Thu, 15 Jan 2026 · 03:00
6 hours behind
2026-07-15 · 09:00
Wed, 15 Jul 2026 · 03:00
6 hours behind
2026-10-27 · 09:00
Tue, 27 Oct 2026 · 04:00
5 hours behind
2026-11-03 · 09:00
Tue, 3 Nov 2026 · 03:00
6 hours behind
Find a window for the whole meeting
The illustrative common workday narrows from three hours to two across those dates. If the Paris team must finish by 17:00, a New York-anchored 90-minute meeting at 10:00 will no longer fit after the change. Adjust the anchor time, duration, or agreed availability before export.
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.