Meeting planner
Add the cities your team sits in and see, hour by hour, where the working days actually overlap. Everything runs in your browser using your own device's time zone data.
Three cities are loaded to start with. Remove any with the × next to its name.
How to read the grid
Green cells are normal working hours, amber is early or late but usually workable, and grey is the middle of the night. Look for a column that is green or amber for everyone.
The grid is anchored to today's date in the first city on the list, which is why the top row reads 00 through 23 in that city's local time. Adding a city with a fractional offset such as India (UTC+5:30) will show the hour it falls into rather than a half-hour label; hover any cell to see the exact local time.
Reading it in practice
- A column green for everyone is the ideal slot and rarely exists past six hours of spread.
- A column that mixes green and amber is usually the best available compromise.
- If every column contains grey for someone, alternate who takes the unsociable hour.
- Once you pick a slot, send a calendar invitation rather than a clock time in an email.
Questions
Each row renders the same 24 instants in that city's zone using your browser's time zone data. Green marks 9am to 5pm local, amber marks 7–9am and 5–8pm, and grey is overnight. A column that avoids grey for everyone is a workable slot.
Yes. The grid uses today's actual offsets, so a city currently on daylight saving is placed where it really is rather than where its standard offset would put it.
No. The grid is built in your browser and nothing about your selection reaches our servers.
Then the working days genuinely do not overlap, and someone has to take the call outside normal hours. Rotate who does it rather than fixing it on one region permanently.
Running a team across zones?
Our guide covers core hours, handovers and the failure modes that quietly cost you people.
Read the guide