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
Do not borrow Chicago’s seasonal offset
Mexico City stays at UTC−06:00 across the four 2026 samples shown here. Chicago shares that offset in January and November but uses UTC−05:00 in July and on 27 October. If a schedule says only “Central time,” ask which city controls it before converting the time.
A dated view of the local clock
Four examples at 13:00 UTC, calculated with IANA 2026f. These are selected dates, not a live clock.
UTC date
UTC offset
Abbreviation
Local date and time
2026-01-15
UTC−06:00
CST
Thu, 15 Jan 2026 · 07:00
2026-07-15
UTC−06:00
CST
Wed, 15 Jul 2026 · 07:00
2026-10-27
UTC−06:00
CST
Tue, 27 Oct 2026 · 07:00
2026-11-03
UTC−06:00
CST
Tue, 3 Nov 2026 · 07:00
A three-city example makes the difference visible
At 09:00 Mexico City on 27 October 2026, Chicago reads 10:00 and New York reads 11:00. On 3 November those clocks read 09:00 and 10:00. Keep Mexico City as its own row even when another row happens to match on the selected date.
Build a plan for this city
Select Mexico City, add the other participants, and enter the actual meeting date. The planner uses America/Mexico_City; 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.