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
Keep the earlier Central start visible
New York is one hour ahead of Chicago on the displayed 2026 dates. A 09:00 New York meeting asks Chicago to join at 08:00. Moving the start to 10:00 New York puts both participants within an illustrative 09:00–17:00 workday.
Compare the same local start on four dates
09:00 in New York, resolved separately on each date with IANA 2026f. The final column describes Chicago relative to New York.
New York
Chicago
Time difference
2026-01-15 · 09:00
Thu, 15 Jan 2026 · 08:00
1 hour behind
2026-07-15 · 09:00
Wed, 15 Jul 2026 · 08:00
1 hour behind
2026-10-27 · 09:00
Tue, 27 Oct 2026 · 08:00
1 hour behind
2026-11-03 · 09:00
Tue, 3 Nov 2026 · 08:00
1 hour behind
Find a window for the whole meeting
The seven-hour shared interval runs from 10:00 to 17:00 New York. If Los Angeles joins, its later opening becomes the new limiting start. Recompute the full intersection instead of assuming that two individually comfortable city pairs guarantee a comfortable three-city meeting.
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.