Meeting Planner

What This Tool Does

A meeting planner helps you find a single time that works for participants in multiple time zones by showing each location's hours across a day timeline, aligned so the same instant appears in the same column for every city. You add the cities involved, and the tool visualizes the overlapping windows of reasonable working hours, highlighting the slots where everyone is within an acceptable local time range. Unlike a timezone converter, which translates one specific time into other zones, the meeting planner shows the full day for all participants so you can find the best available slot rather than just check whether a proposed time works. Where no acceptable overlap exists, the tool makes that absence visible, which is itself valuable information that prompts a different approach.

Why It Matters

Scheduling a meeting across time zones is a genuine optimization problem, not a simple lookup. You need a time that falls within acceptable hours for every participant, and the right answer is rarely obvious when zones span eight or more hours and the working-day overlap is thin or nonexistent. Solving this by converting times for each person and reasoning about each clock separately is slow and error-prone, and it tends to bias the result toward the scheduler's own convenience rather than toward fairness. A meeting planner surfaces the overlap visually, turning a multi-variable problem into a quick visual check, and it reveals when no good overlap exists — which is the signal to consider an async alternative rather than forcing someone onto a call at 11 PM. The result is fewer reschedules, fewer "that is an unreasonable hour for me" replies, and a more considerate, equitable scheduling culture. For teams where one region historically bears the burden of off-hours calls, a planner makes that burden visible and makes it easier to rotate it fairly.

How to Use the Meeting Planner

1. 1Open the meeting-planner tool and start by adding the cities or time zones of all meeting participants, building the panel of locations the meeting must accommodate.
2. 2Add each participant's location in turn. The tool displays a timeline of hours for each city, all aligned so that the same instant appears in the same column across every row.
3. 3Define acceptable working hours for participants — for example, 8 AM to 6 PM local — if the tool allows you to customize the window. Default working-hour assumptions are a starting point, not a rule.
4. 4Review the highlighted overlap region, which is the set of hours where every participant falls within their acceptable local window simultaneously.
5. 5Pick a time within the overlap that also suits the meeting's purpose — a morning slot for a kickoff that needs energy, an avoidance of Friday afternoons for anything requiring follow-up action.
6. 6Note the chosen time in each participant's local zone so the meeting invitation is immediately clear to everyone without requiring them to convert anything themselves.
7. 7If no overlap exists, identify the participant whose hours can flex and adjust their window with their agreement, or seriously consider an async alternative such as a recorded update or a shared document.
8. 8Send the invitation with each person's local time stated explicitly, or publish the time in UTC alongside a converter reference for maximum clarity.

Benefits

• Visual overlap detection turns a multi-variable scheduling problem into a quick visual check, saving the time and errors of manual conversion for each participant.
• Respects each participant's local working hours, leading to better-attended, less resentful meetings and fewer last-minute declines or no-shows.
• Customizable hour windows let you account for early risers, flexible schedules, or shift workers rather than forcing everyone into a rigid 9-to-5 assumption.
• Reveals when no acceptable overlap exists, prompting an async approach instead of a doomed meeting that one person will silently suffer through or skip.
• Reduces the back-and-forth email chains that plague cross-zone scheduling, where each reply proposes a new time that someone else finds unworkable.
• Each participant sees their own local time in the result, eliminating the conversion errors that creep into invitations when the scheduler converts for everyone by hand.
• Encourages equitable scheduling by making the burden of off-hours calls visible, so it can be distributed across regions over time rather than always falling on the same one.

Common Use Cases

• •A distributed team in San Francisco, London, and Mumbai needs a weekly sync. The planner shows the only viable overlap is San Francisco early morning, London early afternoon, and Mumbai late evening — a real constraint that shapes how they structure the meeting.
• •A sales representative schedules a product demo across three customer time zones and uses the planner to find a single slot that is daytime for all three prospects, maximizing the chance everyone attends.
• •A hiring committee with interviewers in four countries uses the planner to find a panel time when every interviewer can attend live, rather than conducting a sequence of one-on-ones that lack the dynamic of a group discussion.
• •An open-source maintainer team scattered globally uses the planner for their monthly community call, deliberately rotating the inconvenient slot so no single region always takes the late or early hour.
• •A consultant running a workshop for clients in Asia and North America finds the one narrow overlap window and books it well in advance, since the slot is scarce and likely to fill.
• •A family coordinating a birthday video call across five time zones uses the planner to find a weekend slot that works for everyone, rather than defaulting to the organizer's convenience and inconveniencing the rest.
• •An event organizer planning a global product launch livestream uses the planner to choose a time that maximizes the live audience across major regions, accepting that some smaller markets will receive a recording instead.

Best Practices

• Default to everyone's standard working hours — 9 to 5 or 8 to 6 local — and only flex a window with that participant's explicit agreement, so no one is silently expected to take an inconvenient call.
• Rotate inconvenient meeting times for recurring calls so the same region is not always the one taking the early-morning or late-evening slot. Rotation is the simplest way to keep scheduling equitable over time.
• When overlap is thin or nonexistent, seriously consider async communication. A recorded video update or a shared document with comments often beats a bad-hour meeting that one person will resent or skip.
• State the chosen time in each participant's local zone plus UTC in the invitation, so there is no conversion required to accept and no ambiguity about when to show up.
• Avoid scheduling recurring meetings near a participant's lunch hour or at their end of day, which are productivity low points and times when people are mentally checked out.
• Re-run the planner around daylight saving transition dates in any participant's zone, since an offset shift can eliminate a previously good overlap or create a new one that was not available before.
• For large or important meetings, confirm the chosen time with each participant individually before sending a broad invitation, so you catch any objection before it becomes a public scheduling failure.

Practical Examples