A large gap makes the local date essential
Auckland is UTC+13:00 on 27 October 2026. When London reaches 13:00 that Tuesday, Auckland is already at 02:00 on Wednesday. A date copied from the London header alone would put the Auckland participant on the wrong day. Export a table that includes both local dates.
A dated view of the local clock
| UTC date | UTC offset | Abbreviation | Local date and time |
|---|---|---|---|
| 2026-01-15 | UTC+13:00 | NZDT | Fri, 16 Jan 2026 · 02:00 |
| 2026-07-15 | UTC+12:00 | NZST | Thu, 16 Jul 2026 · 01:00 |
| 2026-10-27 | UTC+13:00 | NZDT | Wed, 28 Oct 2026 · 02:00 |
| 2026-11-03 | UTC+13:00 | NZDT | Wed, 4 Nov 2026 · 02:00 |
Compare opposite seasonal changes explicitly
The January sample gives Auckland a thirteen-hour lead over London; the July sample gives it an eleven-hour lead. Both places change their sampled offsets, and they do not share one seasonal calendar. A weekly call across this pair deserves a full preview and a discussion about early or late availability.
Build a plan for this city
Select Auckland, add the other participants, and enter the actual meeting date. The planner uses Pacific/Auckland; the abbreviation in the table is a display label. Adjust working days, hours, and meeting length before choosing a shared window. The supported planning range is 2026–2035.