Skip to content
N-attendee scheduler|Up to 12 timezones

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.

Attendees
4
Max
12
Grid
48 x 30min
DST
Auto

Quick Conversion

Formula: ist_hour = (utc_idx / 2 + 5.5) mod 24

Attendees

Optimal slot
08:00 UTC - 3/4 in core
0 adjacent | 0 edge | 1 outside
Multi-attendee Gantt grid (4 attendees, 48 x 30-min cells)
Multi-attendee meeting Gantt gridHorizontal grid with one row per attendee and 48 columns for each UTC half-hour. Cells color-coded by whether the corresponding local hour falls inside that attendee's business window.UTC01234567891011121314151617181920212223Mumbai engineeKolkata053006000630070007300800083009000930100010301100113012001230130013301400143015001530160016301700173018001830190019302000203021002130220022302300233000000030010001300200023003000330040004300500New York leadNew_York200020302100213022002230230023300000003001000130020002300300033004000430050005300600063007000730080008300900093010001030110011301200123013001330140014301500153016001630170017301800183019001930London partnerLondon010001300200023003000330040004300500053006000630070007300800083009000930100010301100113012001230130013301400143015001530160016301700173018001830190019302000203021002130220022302300233000000030Singapore SMESingapore080008300900093010001030110011301200123013001330140014301500153016001630170017301800183019001930200020302100213022002230230023300000003001000130020002300300033004000430050005300600063007000730Business coreAdjacentEdgeOutside

Selected: UTC 13:00

2/4 in business core
Mumbai engineer
18:30
Sat GMT+5:30
Adjacent
New York lead
09:00
Sat EDT
Business core
London partner
14:00
Sat GMT+1
Business core
Singapore SME
21:00
Sat GMT+8
Edge

Top 10 candidate slots

RankUTCIn coreAdjacentOutside
108:003/401
208:303/401
309:003/401
409:303/401
507:002/411
607:302/411
710:002/411
810:302/411
912:002/410
1013:002/410
Algorithm
score(slot) = count(attendees where local_hour(slot, tz) in [bizStart, bizEnd))optimal_slot = argmax_score(slot) tie-break: minimise distance from local 11 AM

Worked: 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

  1. 1
    Click Add attendee and pick the IANA timezone for each person on the meeting.
  2. 2
    Adjust business hours per attendee if their local norm differs from 9-17 (Indian IT often runs 10-18 or 11-19).
  3. 3
    Read the optimal slot auto-picked above the grid - the half-hour with the most attendees in business core.
  4. 4
    Click any column to lock the marker and see each attendee's local time.
  5. 5
    Save 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.

Meeting Planner: Frequently Asked Questions

Have more questions? Contact us

Used by globally-distributed delivery teams

4.9
Based on 5,970 reviews

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.

N
Naomi Ferreira
Remote-team lead at a Sao Paulo SaaS coordinating 8 timezones
May 19, 2026

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.

D
Devansh Rangarajan
Outsourcing manager at a Chennai BPO with NYC + London + Singapore clients
April 27, 2026

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.

H
Henrik Larsen
Consulting partner running Stockholm-Mumbai-Sydney engagements
March 30, 2026

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.

L
Lisha Vaidyanath
DevOps engineer running global on-call across 11 zones
March 2, 2026

Love using our calculator?

Related tools

Learn More

Related Articles

Dive deeper with our expert guides and tutorials related to Meeting Planner

Loading articles...