Flagship tool
Meeting Planner
Add each participant's city and working hours, pick a date and duration, and find the time that works best — with a timeline everyone can read and a summary you can paste into Slack or Teams.
How it works
Each participant has working hours in their own local time (9:00–17:00 by default; overnight shifts like 22:00–06:00 work too). Time converts every participant's working day into exact instants for the date you choose, so overlaps are computed precisely — including on days when someone's clocks change.
The timeline shows the chosen day in 30-minute slots for every participant: Working hours, Early or Late (within two hours of their hours, striped) and Outside hours. Slots where everyone is working are underlined.
Find best overlap lists every window where all participants are working for the full duration. If there's none, Time proposes the closest compromise: minutes just outside someone's hours count once; minutes deep in their night count three times.
Worked example
Chennai and London, 9–5 each, on 7 October 2026: working hours overlap from 1:30 PM to 5:00 PM in Chennai — 9:00 AM to 12:30 PM in London.
Add New York and there's no time when all three are inside 9–5. Time then suggests the closest option that keeps everyone out of the middle of their night: 4:30 PM Chennai, 12:00 PM London, 7:00 AM New York — 2 people slightly outside their hours.
Edge cases handled
- No overlap at all — explained plainly, with the closest compromise.
- DST changes mid-season: the London–New York overlap grows from 3 to 4 hours while only one side has changed clocks.
- 23- and 25-hour days on DST change dates (the timeline shows 46 or 50 slots).
- Overnight working hours that cross midnight.
- Participants whose meeting falls on a different calendar day are marked “+1 day”.
- Share links carry only places, working hours, date, duration and start time — never names.