Find a time everyone can actually attend
Each participant has a separate city label, IANA time-zone identity, workweek and editable preferred and acceptable local windows. The planner converts every local interval to UTC and intersects all participants. A green suggestion fits everyone's preferred time for the entire meeting. An amber suggestion fits everyone's acceptable time but not all preferred time. No result is invented when there is no shared window.
For New York and London on 15 January 2026, local 09:00–17:00 workdays overlap 14:00–17:00 UTC. Adding Kolkata with the same local hours removes the common interval. The planner does not confuse a pairwise overlap with a group match.
Overnight shifts and daylight saving
A window ending earlier than it starts continues into the next local day and belongs to the start day's workweek. A weekly recurrence keeps the chosen host-local wall time, then resolves each date separately. New York 09:00 maps to London 13:00 on 9 March 2026 but London 14:00 on 30 March after the UK's transition. A nonexistent wall time is rejected; a repeated time needs an earlier/later choice.
Calendar export and privacy
Download an RFC 5545 calendar file of only the selected one-off meeting or the explicitly previewed weekly occurrences. UTC event times avoid ambiguous TZID recurrence rules. Sharing uses a URL fragment that contains zones, dates and hours; it is not encryption. Participant labels are omitted by default.
Frequently asked questions
Does the tool use fixed EST or IST offsets?
No. It uses IANA location identifiers and date-aware rules. Abbreviations alone can be ambiguous.
Does a 45-minute meeting fit a 30-minute overlap?
No. The full meeting must fit within one continuous shared interval.
Can two people share one zone but have different hours?
Yes. Every participant's schedule is intersected separately.