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
Auckland’s morning can be London’s previous evening
At 09:00 Auckland on 27 October 2026, London reads 20:00 on 26 October. That is a different local day, not a conversion error. A Tuesday Auckland recurrence must therefore be reviewed against Monday availability in London.
Compare the same local start on four dates
09:00 in Auckland, resolved separately on each date with IANA 2026f. The final column describes London relative to Auckland.
Auckland
London
Time difference
2026-01-15 · 09:00
Wed, 14 Jan 2026 · 20:00
13 hours behind
2026-07-15 · 09:00
Tue, 14 Jul 2026 · 22:00
11 hours behind
2026-10-27 · 09:00
Mon, 26 Oct 2026 · 20:00
13 hours behind
2026-11-03 · 09:00
Mon, 2 Nov 2026 · 20:00
13 hours behind
Find a window for the whole meeting
The sampled gap is thirteen hours in January and late October, but eleven hours in July. Illustrative 09:00–17:00 days do not overlap in these examples. Discuss an early or late exception with both teams, then check weekday boundaries and all twelve recurring dates before exporting.
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.