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
A three-hour gap still needs a full-duration check
New York is three hours ahead of Los Angeles on all four sampled dates. At 09:00 New York, Los Angeles is only at 06:00. For two illustrative 09:00–17:00 days, wait until 12:00 New York before treating the western workday as available.
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 Los Angeles relative to New York.
New York
Los Angeles
Time difference
2026-01-15 · 09:00
Thu, 15 Jan 2026 · 06:00
3 hours behind
2026-07-15 · 09:00
Wed, 15 Jul 2026 · 06:00
3 hours behind
2026-10-27 · 09:00
Tue, 27 Oct 2026 · 06:00
3 hours behind
2026-11-03 · 09:00
Tue, 3 Nov 2026 · 06:00
3 hours behind
Find a window for the whole meeting
The shared interval then runs from 12:00 to 17:00 New York, or 09:00 to 14:00 Los Angeles. A four-hour meeting fits only if it starts early enough in that window. Overnight calls near a clock-change boundary still need explicit repeated or missing-time handling, even though these daytime examples keep the same gap.
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.