Meeting Planner
Plan meetings across any number of attendees in any timezones. Each attendee carries their own IANA timezone and business hours; the 48 x 30-minute Gantt grid finds the maximal-overlap slot automatically. DST and half-hour offsets (India, Iran, Newfoundland) handled correctly.
Quick Conversion
Formula: ist_hour = (utc_idx / 2 + 5.5) mod 24
Attendees
Selected: UTC 13:00
Top 10 candidate slots
| Rank | UTC | In core | Adjacent | Outside |
|---|---|---|---|---|
| 1 | 08:00 | 3/4 | 0 | 1 |
| 2 | 08:30 | 3/4 | 0 | 1 |
| 3 | 09:00 | 3/4 | 0 | 1 |
| 4 | 09:30 | 3/4 | 0 | 1 |
| 5 | 07:00 | 2/4 | 1 | 1 |
| 6 | 07:30 | 2/4 | 1 | 1 |
| 7 | 10:00 | 2/4 | 1 | 1 |
| 8 | 10:30 | 2/4 | 1 | 1 |
| 9 | 12:00 | 2/4 | 1 | 0 |
| 10 | 13:00 | 2/4 | 1 | 0 |
score(slot) = count(attendees where local_hour(slot, tz) in [bizStart, bizEnd))optimal_slot = argmax_score(slot) tie-break: minimise distance from local 11 AMWorked: 4 attendees (Mumbai, NYC, London, Singapore), business windows 10-18 / 9-17 / 9-17 / 9-18. At 13:00 UTC -> Mumbai 18:30 (edge), NYC 09:00 (core), London 14:00 (core), Singapore 21:00 (outside). Score = 2 in core. The algorithm scans all 48 half-hour slots and picks the maximum.
How to plan a multi-timezone meeting
- 1Click Add attendee and pick the IANA timezone for each person on the meeting.
- 2Adjust business hours per attendee if their local norm differs from 9-17 (Indian IT often runs 10-18 or 11-19).
- 3Read the optimal slot auto-picked above the grid - the half-hour with the most attendees in business core.
- 4Click any column to lock the marker and see each attendee's local time.
- 5Save to history and copy the formatted strings into a calendar invite.
Why multi-timezone scheduling is hard
In 2026, a Toronto product manager running a 7-person sprint review across Bengaluru, London, Tokyo, Berlin, San Francisco, and Sydney needs a meeting time that doesn't require anyone to wake up at 3 AM. This planner exists to make that pick reliable, repeatable, and DST-aware.
Scheduling a meeting across many people in many timezones is one of the unsung hard problems of modern remote work. The naive approach - everyone votes on a Doodle poll - falls apart with more than 4 timezones because most candidate slots land outside someone's business hours. Tools like When2Meet help, but require everyone to manually click their availability. This page is the structural opposite: each attendee declares only their timezone and business hours; the algorithm then computes the overlap automatically.
The optimal-meeting problem is a constrained search. Each attendee defines a per-day business window (typically 9 AM to 5 PM in their local timezone). The job is to find UTC hours where every attendee's local hour falls inside their window. With N attendees and 48 half-hour candidate slots per day, the brute-force search is 48 * N - trivial for any modern device. The clever part is presenting the result so the meeting organiser sees not just ‘yes/no’ for each slot but the per-attendee local time and any compromises required.
Indian Standard Time (UTC+5:30) is the trickiest single timezone for global meeting scheduling because of its half-hour offset, which breaks the every-hour grid that most calendar UIs assume. The Madras (now Chennai) Observatory chose 82.5 degrees east in 1906, giving UTC+5:30 - a single zone for a country 2,933 km wide. India considered DST during the 1962 Sino-Indian war and the 1971 Bangladesh war and rejected it both times. This page handles the half-hour correctly via the IANA TZDB.
Nepal (UTC+5:45) and the Chatham Islands of New Zealand (UTC+12:45 / +13:45) push the half-hour problem to a 45-minute problem. Iran (UTC+3:30 / +4:30), Afghanistan (UTC+4:30), Myanmar (UTC+6:30), the Cocos Islands (UTC+6:30), and Newfoundland (UTC-3:30 / -2:30) all use 30-minute offsets. The IANA TZDB encodes every such offset; the Intl.DateTimeFormat API used on this page reads it correctly. The grid render below is in 30-minute resolution.
Daylight Saving Time complicates multi-timezone scheduling because different countries shift on different dates. The US shifts on the second Sunday of March and the first Sunday of November. The EU shifts on the last Sunday of March and the last Sunday of October. Australia shifts in the opposite direction in October and April. New Zealand and the Chatham Islands shift in September and April. For most of the year, two-thirds of the world is in the ‘wrong’ DST state relative to North America - which is why this page evaluates DST at the specific candidate meeting date, not just ‘now’.
The IT services industry has produced a vocabulary for these compromises. The ‘Eastern shift’ (5 PM - 2 AM IST) overlaps with the US East Coast workday. The ‘Central shift’ (6 PM - 3 AM IST) overlaps with the US Central workday. The ‘UK shift’ (12 PM - 9 PM IST) overlaps with London business hours. The ‘Aus shift’ (5 AM - 2 PM IST) overlaps with Sydney. This page's overlap algorithm naturally finds these regimes once you add the attendees.
The IANA Time Zone Database (TZDB) was founded by Arthur David Olson at the National Institutes of Health in 1986 and is now maintained collaboratively at iana.org/time-zones. It encodes every DST rule change in every region since 1880 - the 1918 Standard Time Act, the 1942-1945 War Time period in the US, the 1986 amendments, the 2007 Energy Policy Act, the EU's repeated DST rule changes - and updates within weeks of any government change. Every modern browser ships a copy via the Intl API.
Used by globally-distributed delivery teams
“8 attendees, 8 timezones, one weekly steering committee. This page collapsed three weeks of email negotiation into one click. The optimal-slot suggestion is exactly the slot we ended up booking.”
“I needed a tool that handles the IST half-hour correctly. Every other meeting planner rounds it to 5:00 PM IST which loses a critical 30 minutes. This one is exact.”
“Three continents, three DST regimes (EU, India, Australia). The auto-DST handling means I stop calculating dates by hand. Attendees self-load their TZ from the dropdown. Saves an hour per month.”
“We rotate PagerDuty across 11 engineers in 9 cities. The 12-attendee grid is exactly the right size for our roster. The optimal-slot suggestion settles every quarterly handoff debate.”
Love using our calculator?
Related tools
Related Articles
Dive deeper with our expert guides and tutorials related to Meeting Planner