Meeting Time Planner

The Meeting Time Planner finds the hours that fall inside everyone’s workday when your team or client is spread across time zones. Pick two to four cities, set a working-hours window, and the tool converts every zone into a common frame, highlights where they all overlap, and lists the resulting slots in each participant’s local time. It turns the “let’s find a time that works” email thread into a two-minute lookup.

How to Use

1. Set the working-hours window that applies to everyone, such as 9:00 to 18:00. If one zone has different norms, the overlap simply reflects the constraint you choose.
2. Add time zones by typing city names into up to four fields and selecting from the suggestions.
3. Read the grid. Each row is one city’s 24-hour day; a highlighted column means that hour is inside working hours for every selected zone.
4. Use the best-times list, which converts each overlapping range into local time for each city so you can copy it directly into the invite.

Reading the Overlap Grid

The grid’s mental model is a single vertical slice equal to one moment in time. The rows are the cities, each shown in its own local clock; a column that is green in every row is a time everyone is at work. Reading down a column answers “who is available now?”, while reading across a row shows how one city’s morning lines up with another’s evening.

Two patterns show up repeatedly. If the zones are close — New York and Chicago — the overlap is wide and the meeting is easy. If they are far apart — New York and Tokyo — the overlap may be an early morning on one side and a late evening on the other, and the grid makes that asymmetry visible before you commit. Seeing “your 7:00, their 20:00” is much harder to argue with than a written time-zone conversion in a chat message.

Worked Examples

Example 1 — a three-city standup. A distributed team has members in New York (UTC−4), London (UTC+1), and Bangalore (UTC+5:30). The overlap between all three, within a 9–18 window, lands in the morning for New York and London and the mid-afternoon for Bangalore — the planner lists it as a concrete slot in each local time, ready to paste into a calendar invite.

Example 2 — a client call across two continents. A freelancer in Berlin wants a call with a client in California. The overlap inside 9–18 for both is narrow: the Berlin afternoon maps to the California early morning. Seeing the single viable hour discourages a late-afternoon booking that would land at 6 a.m. for the client.

Example 3 — a workshop with four locations. For a virtual workshop spanning Austin, Dublin, São Paulo, and Seoul, the grid shows whether any hour works within a normal day for all four — often none does. That result is valuable: it tells you to schedule two sessions rather than inconvenience one region permanently.

How the Overlap Is Computed

The planner converts each city’s working-hours window into UTC using the offset for the current date, then intersects the four windows. The intersection, if any, is converted back into each zone’s local time. This is why the answer is expressed as ranges rather than a single time: the overlap can be an hour wide or four hours wide, and knowing the width lets you pick a slot that is comfortable for the majority.

Two details matter for interpreting the result. First, offsets can include fractional hours — India is UTC+5:30, Nepal UTC+5:45, and a few zones have their own unusual offsets — so the grid aligns to real local hours, not whole-hour steps. Second, the calculation uses today’s offsets from the IANA database. That is correct for meetings this week and a good approximation beyond it, but a zone that changes its clocks next month is not yet reflected.

Daylight Saving Caveats

Daylight saving is where time-zone planning goes wrong in practice, because countries switch on different dates and some do not switch at all. The northern hemisphere changes in March and October, the southern hemisphere in March and April or September and October, and regions such as Arizona, Hawaii, and most of East Asia stay on standard time year-round. During the few weeks around a transition, a slot that overlaps today may not overlap next month.

The practical routine: plan with the tool using current offsets, then check the World Clock shortly before confirming a date that crosses a transition period, and prefer recurring meetings with a fixed UTC anchor plus a note about the local times, so participants can spot a change.

Common Mistakes

• Assuming the listed time is everyone’s time. Each row and each result line is labeled with its own city’s local time; the same slot is a different clock reading in each zone.
• Choosing a slot that only works for the organizer. The overlap list already excludes those; if there is no overlap, the honest answer is that the meeting needs to be split or rotated.
• Planning across a DST boundary without rechecking. The offsets shift, and the slot you booked may drift by an hour.
• Ignoring the width of the window. A one-hour overlap has no slack for a call that runs long; prefer a wider slot when one exists.
• Forgetting that “working hours” are a convention. Some colleagues start earlier or finish later, and widening the window often produces a slot that everyone actually prefers.

Features

• Compares two to four time zones from a searchable city list
• Configurable working-hours window applied to every zone
• Color-coded 24-hour grid with the shared overlap highlighted
• Best-times list in each participant’s local time
• Fractional offsets supported (UTC+5:30, UTC+5:45 and similar)
• Daylight-saving aware via the IANA database, and fully client-side

Use Cases

• Distributed teams: Choose a standup or sync slot that everyone can attend.
• Client calls: Check the overlap before proposing a time to a customer abroad.
• Event planning: Test whether a single session works across four regions or needs to be split.
• Recurring meetings: Identify the narrowest practical window and the risks around DST changes.
• Travel: See how your own day will line up with the office while away.

Related Tools

• World Clock
• Timestamp Converter
• Time Calculator
• Date Calculator