Home › All Tools ›

Meeting Time Planner

Use Meeting Time Planner online for free at FreeToolZones — no sign-up, no watermark.

Loading tool...

Finding a meeting time that suits people in different time zones is a puzzle with many moving parts. Each person has working hours, each working day falls in a different window of universal time, daylight saving shifts the windows during the year, and the overlap that suits everyone may be only an hour or two, or may not exist at all. Guessing the overlap by adding and subtracting offsets is slow and error-prone. The Meeting Time Planner on FreeToolZones solves the puzzle directly. You pick a date, choose two to four time zones, set the working hours, and it shows the overlapping window in UTC, its length in hours, and an hour-by-hour table giving the same moment in every zone.

This article explains how the Meeting Time Planner works, including how it handles the case where no overlap exists, walks through realistic examples for distributed teams, and covers tips, honest limitations, and frequently asked questions. The tool has a date field, four zone selectors with checkboxes for the third and fourth zones, two working-hour fields, a Find Meeting Times button, and a Copy Result button.

What Is the Meeting Time Planner?

The Meeting Time Planner is a free online tool that finds the hours when the working days of people in different time zones overlap on a chosen date. The date field begins with today, and the hint under it explains that the date is read in each zone’s local calendar, which means the working window is applied to that calendar date in each zone separately. The zone selectors begin with New York, London, and Kolkata for the first three zones, and Tokyo for the fourth. The third zone is included by default, through a ticked checkbox labeled “Include a third time zone,” and the fourth zone is excluded by default, through an unticked checkbox labeled “Include a fourth time zone.” The first two zones are always included.

The working hours are set with two number fields: “Working day starts (hour, 0-23),” beginning at 9, and “Working day ends (hour, 1-24),” beginning at 17. The end hour must be after the start hour, and the tool validates this, showing an error message if the window is invalid. The end hour of 24 means midnight at the end of the date, which the tool handles by treating it as midnight at the start of the next day in the relevant zone. The same working window is applied to every zone, which is a simplification to be aware of: the tool assumes everyone keeps the same working hours in their own local time.

When an overlap exists, the result shows two figures: the overlap window length in hours, to one decimal place, and the overlap range in UTC, as start and end times. Below the figures, a paragraph explains that everyone is within working hours during the window and that each table row shows the same moment in every zone. The table that follows has a UTC column and one column per included zone, with one row per whole hour within the overlap, plus a row for the overlap start when the overlap is shorter than an hour or does not align with whole hours. Each row shows the UTC time and the local time in every zone, so a meeting time can be read across the row.

When no overlap exists, the tool says so plainly, in a paragraph explaining that there are no overlapping working hours on the date with the chosen zones and window, and suggesting widening the working hours or dropping a zone. It then shows a reference table giving 12:00 UTC in each zone, so you can see the local times at a shared reference moment and judge how far apart the working windows are. The Copy Result button copies a summary of the overlap, or a statement that no overlap exists, depending on the result.

How to Use the Meeting Time Planner

Follow these steps to find meeting times across zones.

  1. Pick the meeting date in the date field. The date is read in each zone’s local calendar, so the working window applies to that date in every zone. The field begins with today.
  2. Choose the first two time zones in the Time zone 1 and Time zone 2 selectors. These zones are always included. They begin with New York and London.
  3. Decide whether to include the third zone. The “Include a third time zone” checkbox is ticked by default, and the Time zone 3 selector begins with Kolkata. Untick the box to plan for two zones only.
  4. Decide whether to include the fourth zone. The “Include a fourth time zone” checkbox is unticked by default, and the Time zone 4 selector begins with Tokyo. Tick the box to add the fourth zone.
  5. Set the working hours. Enter the start hour, from 0 to 23, and the end hour, from 1 to 24, with the end after the start. The defaults of 9 and 17 represent a 9 AM to 5 PM working day in each zone’s local time.
  6. Click the Find Meeting Times button. Read the overlap figures and the table, or the no-overlap message and reference table if there is no overlap.
  7. Pick a meeting time from a table row. Each row is a candidate start time, showing the UTC time and the local time in every zone. Click Copy Result to copy the overlap summary for sharing.

Here is a worked example. A team in New York, London, and Kolkata wants to meet on a given date, with working hours of 9 to 17 in each place. Leave the third-zone box ticked, leave the fourth-zone box unticked, and click Find Meeting Times. The result shows an overlap of a few hours in the UTC late morning, with a table whose rows give the UTC time and the local times in all three zones. A row reading 14:00 UTC, 10:00 New York, 15:00 London, and 19:30 Kolkata would be outside the working window for Kolkata, so the actual overlap rows will all fall within 9 to 17 in every zone; the table only includes hours inside the overlap, so any row you pick is safe.

Now add Tokyo as a fourth zone and calculate again. The overlap may shrink or disappear, because Tokyo’s working day overlaps less with New York’s. If the result reports no overlap, widen the working hours, for example to 8 to 18, or drop a zone, and calculate again. The reference table at 12:00 UTC helps you judge the adjustment: it shows how far each zone’s local time is from the shared moment. If you see an error message about a valid working window, check that the start hour is before the end hour and that both are in range.

Key Features of the Meeting Time Planner

The planner’s features are built around the overlap calculation, the readable table, and honest handling of the no-overlap case.

Two to four time zones

The planner handles two zones always, with optional third and fourth zones controlled by checkboxes. The zone selectors offer the same twenty-five zones as the Time Zone Converter, so the same world coverage applies. The checkbox design makes it easy to test whether dropping a zone creates an overlap, without losing the zone choice: untick, calculate, and retick to restore it.

Configurable working window

The working start and end hours are fully configurable, from a narrow window such as 10 to 15 to a wide window such as 8 to 20, with 24 allowed as an end hour for a window running to midnight. Widening the window is the main lever when no overlap exists, and narrowing it is useful when the overlap is large and you want only the core hours. The same window applies to all zones, which keeps the comparison fair and simple.

Overlap length and UTC range

The result gives the overlap length in hours to one decimal place and the overlap range in UTC. The UTC range is the unambiguous statement of the window, suitable for sharing with a group, because UTC has no daylight saving changes. The length figure tells you at a glance whether the overlap suits a 30-minute call, a one-hour meeting, or a longer workshop.

Hour-by-hour table in every zone

The table lists the whole hours within the overlap, with the UTC time and each zone’s local time on every row. This is the practical output: pick a row, and you have the meeting time in every participant’s local time, ready to paste into an invitation. When the overlap is shorter than an hour or does not align with whole hours, the table includes a row for the overlap start, so a short overlap is still represented.

Honest no-overlap result with a reference table

When no overlap exists, the tool does not invent one. It states the fact, suggests widening the hours or dropping a zone, and shows a reference table of 12:00 UTC in each zone. That reference helps you see the shape of the problem: which zones are far apart, and how much the window would need to widen to bridge the gap.

Practical Use Cases With Concrete Examples

Cross-zone meeting planning is a daily task for distributed teams, global clients, and international collaboration. The examples below show the main patterns.

Distributed team standups

A daily standup needs a time inside everyone’s working hours, every day. A team spanning New York, London, and Kolkata has a comfortable overlap in the late morning UTC, while adding Sydney or Auckland tightens it sharply. Use the planner to find the overlap for the current date, pick a row in the middle of the overlap for resilience, and set the standup there. Recheck the overlap after daylight saving transitions, because the offsets change and the overlap shifts by an hour, sometimes moving a standup outside someone’s working hours.

Client meetings and sales calls

Client meetings often involve two zones and a need to be accommodating. A seller in London and a client in Los Angeles have an overlap in the London afternoon and the Los Angeles morning. The planner’s table shows the candidate times in both zones, so the seller can offer two or three options with both local times stated, rather than asking the client to convert. For a three-way call with a colleague in Singapore, the overlap narrows, and the table shows exactly which hours remain.

Interviews, webinars, and training

Interviews and training sessions need longer overlaps than standups, often 60 to 90 minutes. The overlap length figure tells you immediately whether a 90-minute session fits: an overlap of 1.5 hours or more is needed, and the table shows the start times that leave enough room. For webinars with a global audience, the planner helps in choosing a time that is inside working hours for the largest number of regions, even if it cannot suit everyone, and the no-overlap case signals that two sessions, at different times, may be needed.

Shift handover and support coverage

Support teams handing over between regions need an overlap for the handover conversation. A handover between London and Sydney, for example, has a narrow window, and the planner shows whether the standard working hours overlap at all, and if so, for how long. Widening the window to include early or late hours can create a handover slot, and the planner quantifies the widening needed. The reference table in the no-overlap case helps in negotiating the adjusted hours.

Personal and family coordination

Family calls across zones benefit from the same planning, with the working window reinterpreted as waking hours. Set the window to waking hours, such as 8 to 22, choose the family members’ zones, and the overlap shows the hours when everyone is awake. The table then gives the call time in every zone, so the invitation can state each person’s local time. The wider window reflects that family calls are not limited to working hours.

Tips and Best Practices

  • Start with the standard window and widen only if needed. The default 9 to 17 window represents core working hours. If it gives no overlap, widen gradually, such as 8 to 18, so the compromise is as small as possible.
  • Pick a row in the middle of the overlap, not at its edge. A meeting at the very start or end of the overlap leaves no room for overrun and may feel early or late to one participant. A middle row is the most comfortable for everyone.
  • Recheck after daylight saving transitions. Offsets change on different dates in different regions, so an overlap that worked last month may have shifted by an hour. Run the planner for the new date rather than reusing an old table.
  • Test dropping a zone when there is no overlap. Untick the third or fourth zone and calculate again to see the overlap for the remaining zones. That tells you whether a smaller meeting is possible, or whether the time must move outside someone’s working hours.
  • State every participant’s local time in the invitation. Copy the row’s times into the invitation, with the UTC time as a shared reference, so nobody has to convert and nobody can misread the time.
  • Remember that the same window applies to all zones. If participants keep different working hours, set the window to the intersection of their patterns, or run the planner with the narrowest common window and adjust by conversation.
  • Use the date field for the actual meeting date. Daylight saving rules depend on the date, so a plan for a future date must be calculated for that date, not for today.

Limitations to Know Before You Rely on the Result

The Meeting Time Planner applies the same working window to every zone, on the same calendar date in each zone’s local calendar. It does not support different working hours per zone, does not know about lunch breaks, part-time patterns, or individual availability, and does not check calendars. It finds the overlap of the stated windows, not the overlap of real availability, so a time inside the overlap may still clash with an individual’s commitments. The planner also treats the working window as applying to the chosen date in each zone, which is the natural reading for a single-day plan, but it does not handle multi-day or recurring meeting series, where the overlap may vary by date.

The table lists whole hours within the overlap, plus a start row for short or misaligned overlaps, so start times at half hours or quarter hours within the overlap are not listed individually, although any time inside the UTC range is valid. The zone list is fixed at twenty-five zones, and the planner relies on your browser’s time zone data for daylight saving rules. It does not save results, create calendar invitations, or send notifications; use Copy Result to keep the summary and create the invitation in your own calendar.

Frequently Asked Questions

What does the overlap window mean?

It is the period, on the chosen date, when every included zone is inside the stated working window at the same moment. Any meeting time inside the window falls within working hours for every participant, in their own local time. The window is stated in UTC, with a table giving the local times.

What should I do if there is no overlap?

Widen the working hours, drop a zone, or both, and calculate again. The no-overlap message suggests exactly this, and the reference table at 12:00 UTC helps you judge the adjustment. If no reasonable widening creates an overlap, consider two meetings, asynchronous updates, or a meeting outside one participant’s working hours by agreement.

Why is the same working window used for all zones?

For simplicity and fairness: the planner compares the same local working pattern in each zone. If participants keep different hours, set the window to the hours they share, or run the planner with the narrowest pattern and refine the result by conversation with the participants.

Does the planner account for daylight saving time?

Yes, through your browser’s time zone data, applied for the chosen date. The overlap is calculated for that specific date, so daylight saving rules in force on that date are used. Always enter the actual meeting date, especially near clock-change dates.

Can I plan for more than four zones?

Not in one calculation. The planner handles up to four zones. For more zones, run the planner for groups of four and compare the UTC ranges, or find the overlap for the most distant zones first, because they constrain the window most, and then check the remaining zones against that window with the Time Zone Converter.

Why does the table show whole hours only?

The table lists the whole hours that fall inside the overlap, which covers the usual meeting start times. Any time inside the UTC overlap range is valid, including half-hour starts, so a 30-minute meeting can start at a half hour within the range even if that row is not listed. A start row is added when the overlap is short or misaligned.

Related Tools

These related tools on FreeToolZones cover neighboring time zone questions:

Browse More Tools