Enter elapsed minutes
Choose a whole-number duration from 15 to 240 minutes. The duration describes elapsed time. A clock change can make the local start and end labels look unusual, but it does not change a ninety-minute meeting into a different elapsed length.
Read the full interval
A shared window is bounded by the latest available start and earliest available end across all participants. The meeting must stay inside both boundaries. A start inside the window is insufficient when the duration carries the end beyond someone’s availability.
Use the latest-start result
Subtract the meeting length from the window’s end to find the latest permissible start. For a shared interval from 13:00 to 16:00 UTC, a 90-minute meeting can start no later than 14:30 UTC. Starting exactly at that value fits; starting fifteen minutes later overruns by fifteen minutes.
Distinguish short overlap from no overlap
If the shared interval lasts sixty minutes and the meeting lasts ninety, the result is a short window. Reducing the duration to sixty minutes can make it fit. If the interval has zero duration, reducing to fifteen minutes cannot create a meeting slot. Adjust a real availability constraint or choose another date.
Keep half-hour offsets precise
A ninety-minute London–Mumbai call at 10:00 London on 27 October 2026 is 15:30–17:00 Mumbai. The half-hour offset remains in the result. Whole-hour labels on a timeline do not justify rounding the start or end to a different time.
Recheck after changing the plan
Editing duration, date, availability, or anchor interpretation can make a previously selected instant unsuitable. Read the updated availability text and each city’s end time. For a weekly plan, inspect every occurrence; the same anchor start may leave less usable time after a clock change.
Sources
Follow the original references for the rules and formats used in this guide.