Enter the start and next-day end
Set the start later than the end, such as 22:00–06:00. The app treats the end as occurring on the following local date. Select the weekdays on which that interval begins. A Monday selection therefore creates a Monday-night interval extending into Tuesday morning.
The morning tail follows the starting day
Turning off Tuesday as a starting weekday does not delete the Tuesday morning portion of Monday’s interval. It prevents a new Tuesday-night interval from beginning. This distinction matters when an overnight participant meets a colleague whose availability begins early the next day.
Work through the New York–London example
For New York on Monday, 26 October 2026, 22:00–06:00 becomes 02:00–10:00 UTC on Tuesday. London’s Tuesday 09:00–17:00 availability overlaps it from 09:00 to 10:00 UTC. The local shared interval is 05:00–06:00 New York and 09:00–10:00 London.
A 45-minute meeting at 05:00 New York fits and ends at 09:45 London. The latest start is 05:15 New York. A 90-minute meeting is too long for the available hour. The morning tail does not extend merely because another participant is still working.
Keep clock changes attached to the interval
The app maps the local availability interval onto the real UTC segments in the named zone. A skipped portion of the wall-clock day contributes no elapsed time; a repeated portion can contribute both occurrences. The actual duration of an overnight shift may therefore differ on a transition night.
Resolve the selected meeting start separately
If you enter a meeting start that repeats, choose the earlier or later instance. If that start does not exist, select a valid time or use an explicit recurrence skip. Having an overnight availability interval does not remove the need to identify a real meeting instant.
Sources
Follow the original references for the rules and formats used in this guide.