Local rules, explicit.
Give each person a named zone, local weekdays and one work window. Overnight hours belong to their starting weekday.
A clearer hour for a scattered team
Different clocks.
One shared window.
Put working hours on the same timeline. See who can make the whole meeting, with local dates and overnight shifts kept in view.
Find your overlap ↗Free · No account · No calendar access · Browser-local
ILLUSTRATIVE TEAM / 14:00 UTC
London14:00Wed 11 Nov 2026
New York09:00Wed 11 Nov 2026
Kolkata19:30Wed 11 Nov 2026
Compare the whole duration—not just the first minute.
Duration included.
Every candidate is checked across its full elapsed duration. See complete overlap or inspect transparent partial-fit counts.
One instant to keep.
Inspect each person's local date, time and offset. Download a UTC event without sending an invitation or connecting an account.
Notes for crossing the clocks.
PLANNING NOTE 01
One instant can have several local dates ↗
Use UTC as the shared anchor, then read every local date.
PLANNING NOTE 02Make overnight windows belong to the right day ↗
A checked weekday identifies the day an overnight shift starts.
PLANNING NOTE 03Recheck the date, then carry the instant into a calendar ↗
Named zones and fixed UTC events solve different parts of the task.
Entered windows are not real calendar availability. No holidays, leave, split shifts or recurring-event predictions. Time-zone rules come from your browser; confirm the chosen date with your team.