AI Meeting Planner

Best-Slot Recommender

Common Team Shapes

One-click rosters for the time-zone spreads remote teams hit most often.

Every Hour, Scored

Prefer a draggable timeline? Try the Drag & Drop Meeting Planner.

The Scoring Formula

Standard Time-Zone Offsets (IANA tz)

No saved recommendations yet. Tap "Save Best Slot to History" to remember up to six.

How to Use the AI Meeting Planner

1. Add each attendee by name and pick their IANA time zone from the dropdown (the same Area/Location identifiers your calendar app uses).
2. The recommender instantly scores all 24 UTC hours and surfaces the top three slots, ranked, with a confidence bar at the top of the widget.
3. Read each slot's rationale to see who is comfortably at their desk, who is awake but stretched, and who would be asleep — then choose the fairest option.
4. Scan the 24-hour coverage lane and the full scored table to compare alternatives or spot a second workable window for a follow-up.
5. Save the best slot to history, then re-run after each daylight-saving change and confirm against every attendee's live calendar before booking.

Why an AI Meeting Planner Beats a Green Band

In 2026, a remote engineering lead trying to book one weekly sync for teammates in Bengaluru, London, New York, and Tokyo faces a problem no single wall clock can solve: there is rarely an hour when all four are inside polite working time. The AI Meeting Planner exists to rank that trade-off rather than just display it. Instead of showing a green band and leaving the human to squint, it scores all 24 UTC hours for how many attendees are awake and working, weights working hours above merely-awake hours, and surfaces the top three slots with a confidence bar and a plain-English rationale for each.

The arithmetic underneath rests on Coordinated Universal Time (UTC), the global reference that replaced Greenwich Mean Time (GMT) as the world standard in 1972 when the International Telecommunication Union and the Bureau International de l'Heure adopted atomic timekeeping with periodic leap seconds. Every modern operating system stores wall-clock time as an offset from UTC, and this planner does the same: each city's standard offset (London at UTC+0, New York at UTC-5, Bengaluru at UTC+5:30, Tokyo at UTC+9) is added to a candidate UTC hour to produce each attendee's local clock, which is then classified as working, awake, or asleep.

The named regions and their daylight-saving rules come from the IANA Time Zone Database, also called the tz database, zoneinfo, or the Olson database after its founder Arthur David Olson, who began maintaining it in the 1980s. It is the canonical source used by Linux, macOS, Java, Python, and effectively every calendar app, and it uses an Area/Location naming convention such as America/New_York, Europe/London, and Asia/Kolkata. The browser's own Intl.DateTimeFormat API reads the same database, which is why the local times shown here line up with what your operating system reports.

India Standard Time is the classic stress test for any scoring engine because it sits at UTC+5:30, one of only a few half-hour offsets alongside Iran at UTC+3:30 and parts of Australia at UTC+9:30. IST was standardised in 1906 around the 82.5 degrees east meridian near Mirzapur. When the planner evaluates a 13:00 UTC slot it computes 6:30 PM in Bengaluru (late but awake), 1:00 PM in London (prime working time), 8:00 AM in New York (early working), and 10:00 PM in Tokyo (awake but winding down) — then rolls those four classifications into one comparable score.

The ranking logic is deliberately transparent so it can be trusted: each attendee inside the 9 AM to 6 PM working window contributes a full point, each attendee merely awake between 7 AM and 10 PM contributes a partial point, and anyone asleep contributes nothing. The hour with the highest weighted sum wins, ties break toward the slot whose worst-off attendee is least inconvenienced, and the confidence bar simply expresses the winning score as a percentage of the theoretical maximum. This mirrors how Google Calendar's Find a Time, Microsoft Outlook's Scheduling Assistant, World Time Buddy, and Doodle's heat-map reason — but with the reasoning written out instead of hidden.

Fairness is the quiet feature most schedulers ignore. A recurring 6:00 AM call landing on the same teammate every single week is a documented driver of distributed-team burnout, called out in GitLab's Remote Work Report and Buffer's State of Remote Work surveys. Because the planner lists each attendee's local time and comfort band for the recommended slots, a manager can rotate the burden — taking the early call themselves one week, asking Tokyo to stay late the next — rather than silently taxing whoever sits furthest east. The roster persists in your browser via localStorage, so the same team can be re-scored after each daylight-saving shift.

Asynchronous-first companies — Automattic, GitLab, Zapier, Doist — use a planner like this not to book more meetings but to book fewer, sharper ones, reserving synchronous time only for the narrow window the engine flags and pushing everything else to written docs and recorded video. Daylight Saving Time remains the model's honest caveat: the offsets here are standard-time values, so during DST a city may shift an hour. The United States moves on the second Sunday of March and first Sunday of November under the Energy Policy Act of 2005; the European Union moves on the last Sundays of March and October under EU Directive 2000/84/EC; India, Japan, and most of the equatorial world observe no DST at all. The score is a planning aid — always confirm the booked slot against each attendee's live calendar.