About Meeting Time Overlap Planner
Meeting Time Overlap Planner lays a chosen date out as twenty-four UTC hours and shows what each of those hours looks like in every city you add. Up to five cities can sit on the grid at once, chosen from ten hubs that cover the usual spread of a remote team: Los Angeles, New York, São Paulo, London, Berlin, Dubai, Mumbai, Singapore, Tokyo and Sydney.
Each row is one hour of coordinated universal time. A row is green when it falls inside 09:00 to 17:59 in every city on the grid and does not put anyone before 06:00 or at 23:00 or later; it is amber when at least two cities are still in office hours under that same restriction, and plain otherwise. The panel above the table names the best window — the longest unbroken run among the green and amber rows, so an hour that lands somebody at one in the morning is never proposed — and spells out the local start and end for each city, which can be copied as one line for an invite or a message. When no hour qualifies, the panel says so instead of inventing a compromise.
The conversion uses the IANA time zone database through the browser rather than fixed UTC offsets, so the offset applied is the one actually in force on the date you picked. That matters in the week a country changes its clocks, and it also keeps the half-hour offset of Mumbai readable as :30 in the table.
Nothing is saved and no calendar account is involved: the grid is worked out in the page for the date on screen and rebuilt whenever the date or the cities change.
How to use Meeting Time Overlap Planner
- 1 Pick the date of the meeting you are trying to schedule.
- 2 Add up to five cities from the list; remove one by clicking its chip.
- 3 Read the table — green rows suit everyone, amber rows need a compromise.
- 4 Press Copy time to take the best window as UTC plus each city's local hours.
Frequently asked questions
How are working hours defined?
A day is treated as 09:00 to 17:59 local time for every city, and a row is only called comfortable if nobody lands before 06:00 or at 23:00 or later. The window is fixed — there is no field for a team that starts at seven or a client who works evenings.
Does it account for daylight saving?
Yes, as long as you choose the date of the meeting rather than today. The offset comes from the IANA database through the browser, so New York is four hours behind UTC in summer and five in winter, and Sydney follows the opposite pattern for the southern hemisphere.
Can I schedule a meeting for 09:30 local time?
Not directly. Every row is a whole UTC hour, so a city with a half-hour offset such as Mumbai shows :30 in its column and the true local minute is never hidden — but there is no column for a 09:30 start in that city.
What if two windows score the same?
The earliest of the longest runs is reported. Later windows that cover the same number of cities are still visible in the table, but the summary line only names one, so a second option has to be read off the rows.
Can I add a city that is not in the list?
No. The chooser offers ten fixed cities and the grid holds at most five of them. A smaller office in another region cannot be represented, so its local hours would have to be worked out with a separate converter.
Free, online, and private
Free to use
Meeting Time Overlap Planner is completely free. There is no account to create, no login, and no hidden charge or usage limit.
Runs online in your browser
It is a free online tool that runs entirely in your browser. Nothing to download or install — open the page and start using it right away.
Your data stays private
All processing happens locally on your device. Your input is never uploaded, stored, or tracked, so it never leaves your browser.
How Meeting Time Overlap Planner behaves in detail
These are the specifics of this implementation — the exact ranges, defaults and fixed settings you are working with.
| Parameter | Value |
|---|---|
| Cities | ten fixed IANA zones - Los Angeles, New York, Sao Paulo, London, Berlin, Dubai, Mumbai, Singapore, Tokyo and Sydney - with at most five on the grid and at least one kept |
| Defaults | New York, London and Singapore, on the current date from the system clock |
| Grid | twenty-four rows, one per UTC hour on the hour; each cell shows the local hour and minute from Intl.DateTimeFormat with hourCycle h23 |
| Working hours | a fixed 09:00 to 17:59 local window, and a row is only comfortable when nobody falls before 06:00 or at 23:00 or later |
| Row grades | green when every city on the grid is inside the window and none is extreme; amber when at least two are inside it under the same limit; plain otherwise |
| Best window | the longest unbroken run among the green and amber rows only, with ties going to the earliest run; the copy line gives the UTC range plus each city's local start and end |
| Time source | IANA zone identifiers resolved by the browser for the chosen date, so daylight saving and half-hour offsets such as Mumbai's :30 are applied automatically |
Compiled from the implementation of this tool and checked against it by itoolnet.
What Meeting Time Overlap Planner does not do
Knowing the edges of a tool saves more time than another list of its features. These are the cases where it will not do what you might expect.
- Every row is a whole UTC hour. A meeting that starts at 09:30 in Mumbai cannot be placed on the grid, and although the table shows :30 in that column the minute is never selectable - there is no half-hour or fifteen-minute step.
- The city list is closed and the working day is fixed. Ten hubs only, five of them at once, all assumed to work 09:00 to 17:59, with no per-person hours, no tolerance setting, no weekend or public-holiday awareness and no way to add a smaller office.
- It plans a single slot, not a calendar. There is no invite, no attendee list, no recurrent meeting, no saved planner state, and a daylight-saving changeover on the chosen date is applied silently rather than flagged, while two windows that score the same are reduced to the earliest one.
Tested and documented by itoolnet, the team that builds and maintains this site.