An endpoint is not an available interval
London is eight hours behind Singapore on 27 October 2026. London’s 09:00 is Singapore’s 17:00, so two illustrative 09:00–17:00 days only touch at one instant. Even a fifteen-minute meeting needs a changed availability window.
Compare the same local start on four dates
| London | Singapore | Time difference |
|---|---|---|
| 2026-01-15 · 09:00 | Thu, 15 Jan 2026 · 17:00 | 8 hours ahead |
| 2026-07-15 · 09:00 | Wed, 15 Jul 2026 · 16:00 | 7 hours ahead |
| 2026-10-27 · 09:00 | Tue, 27 Oct 2026 · 17:00 | 8 hours ahead |
| 2026-11-03 · 09:00 | Tue, 3 Nov 2026 · 17:00 | 8 hours ahead |
Find a window for the whole meeting
In the July sample, London’s UTC+01:00 offset makes the gap seven hours and creates an illustrative hour from 09:00 to 10:00 London. A weekly habit from summer can stop fitting after the autumn change. Review dates around the transition before sending an ongoing schedule.
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.