A one-hour gap leaves room for the whole discussion
Tokyo is one hour ahead of Singapore on the displayed 2026 dates. A 09:00 Singapore start is 10:00 Tokyo. For illustrative 09:00–17:00 availability, the common interval ends at 16:00 Singapore or 17:00 Tokyo, leaving seven hours.
Compare the same local start on four dates
| Singapore | Tokyo | Time difference |
|---|---|---|
| 2026-01-15 · 09:00 | Thu, 15 Jan 2026 · 10:00 | 1 hour ahead |
| 2026-07-15 · 09:00 | Wed, 15 Jul 2026 · 10:00 | 1 hour ahead |
| 2026-10-27 · 09:00 | Tue, 27 Oct 2026 · 10:00 | 1 hour ahead |
| 2026-11-03 · 09:00 | Tue, 3 Nov 2026 · 10:00 | 1 hour ahead |
Find a window for the whole meeting
This broad pairwise overlap can shrink sharply when a third city joins. London, for example, reaches 09:00 when Singapore reaches 17:00 on 27 October. Add every participant before choosing the window; pairwise suitability is not the same as a common interval for the entire group.
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.