Multi-Participant Time Zone Meeting Planner
Plan a meeting across many time zones with per-participant work hours, 30-minute resolution, and DST-aware offsets for any chosen date.
| UTC | You | London | Mumbai | Fairness |
|---|---|---|---|---|
| 13:00 | 09:00 | 14:00 | 18:30 | 32.3 |
Lower fairness score = closer to each person’s midday. Offsets computed for 2026-08-04 via Intl.DateTimeFormat, so DST is applied per zone for that specific date. Runs entirely in your browser.
About this tool
When a distributed team grows past a few people, the simple version of a meeting planner stops being enough: one person works 7-15, another 10-19, and a third only has Thursday afternoons free. This planner extends the basic time-zone overlap tool with three things the simpler version cannot do. First, each participant has their own work-hours window, not a single shared one — so an early-riser engineer in Chicago and a late-start designer in Berlin both get respected. Second, the day is scanned at 30-minute resolution rather than whole hours, which matters when zones like India (UTC+05:30), Nepal (UTC+05:45), Newfoundland (UTC-03:30), or the Marquesas (UTC-09:30) participate; their local clocks do not line up with full UTC hours, so a whole-hour search would either miss valid slots or place them awkwardly. Third, you choose the meeting date, and the tool uses the IANA database to compute each region's offset for that specific date — so a meeting two weeks out that straddles a DST transition in one country but not another is handled correctly. The output is a ranked list of overlapping slots, with each participant's local clock-time and a fairness score that prefers times near each person's working-day midpoint, so a slot that is mid-morning for everyone ranks above one that sits at the edge of everyone's window. Add up to twelve participants; toggle weekend availability per person; and copy the resulting slot list as a one-line summary you can paste into a thread. Everything runs in your browser using built-in time-zone data, so there is nothing to upload and no account to create.
How to use it
- Set the meeting date (defaults to today).
- Add each participant: name, time zone, their own work-hours window, and whether weekends count.
- Read the ranked list of 30-minute slots where every participant is inside their personal work hours.
- If nothing overlaps, widen one or two windows, mark weekend availability, or accept an early/late call for the most-flexible region.
- Copy the slot summary and share it with the group.
Frequently asked questions
- How is this different from the basic time-zone meeting planner?
- Per-participant work hours (not one shared window), 30-minute granularity (so half- and quarter-hour offsets line up cleanly), per-person weekend toggle, a chosen meeting date (so DST is correct for the actual day), and a fairness ranking that favors slots near each person's midday.
- How are overlapping slots ranked?
- Each candidate slot gets a score: for each participant, we measure how far their local time at that slot sits from the middle of their own working day, then sum the squared deviations. Lower is more fair. Slots that are mid-morning or early-afternoon for everyone rise to the top.
- Why 30 minutes instead of full hours?
- Several zones use half- or quarter-hour offsets — India (+05:30), Nepal (+05:45), Newfoundland (-03:30), parts of Australia (+09:30), Marquesas (-09:30). At whole-hour resolution their local times never align cleanly with UTC, so valid slots get missed or rounded.
- Does it handle daylight saving time?
- Yes, and for the date you pick. The tool calls Intl.DateTimeFormat with the chosen meeting date as the reference instant, so each region's offset reflects whether DST is in effect on that specific day in that specific zone — not just today.
- What does the weekend toggle do?
- If a participant has weekends unchecked, slots that fall on Saturday or Sunday in that participant's local zone are excluded — useful when one region's Friday-night is another region's Saturday-morning.
- How many participants can I add?
- Up to twelve. Beyond that the overlapping window usually collapses to zero and the planner stops being useful — at which point the practical answer is to record async or split into smaller meetings.
- Is any data sent anywhere?
- No. All computation happens in your browser. Names, zones, and the date never leave the page.