A Pacific afternoon can align with tomorrow’s Japanese morning
At 09:00 Los Angeles on 27 October 2026, Tokyo is at 01:00 on 28 October. A later Los Angeles start at 17:00 reaches 09:00 Tokyo on the next date, but that is only the endpoint of an illustrative Pacific workday.
Compare the same local start on four dates
| Los Angeles | Tokyo | Time difference |
|---|---|---|
| 2026-01-15 · 09:00 | Fri, 16 Jan 2026 · 02:00 | 17 hours ahead |
| 2026-07-15 · 09:00 | Thu, 16 Jul 2026 · 01:00 | 16 hours ahead |
| 2026-10-27 · 09:00 | Wed, 28 Oct 2026 · 01:00 | 16 hours ahead |
| 2026-11-03 · 09:00 | Wed, 4 Nov 2026 · 02:00 | 17 hours ahead |
Find a window for the whole meeting
The July and October samples have no positive-length overlap for two 09:00–17:00 schedules. In the November sample, the changed Los Angeles offset creates a one-hour edge window from 16:00 to 17:00 Los Angeles, corresponding to 09:00–10:00 Tokyo the next day. Check weekday availability on both local dates.
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.