Scheduling a meeting across a distributed team usually means someone mentally converting three or four timezones at once, and getting it wrong is easy, especially around daylight saving changes, when the “usual” offset between two cities briefly shifts. This planner lays every selected timezone’s working hours out on one grid, so the overlap (or lack of one) is visible at a glance rather than reconstructed by hand.
How it works
Add the timezones your team spans using the dropdown, and the grid fills in the local hour for each one across a full day, aligned to a shared UTC column so every zone reads off the same reference.
Each cell is colored by how workable that hour typically is locally: green for core working hours (9am-6pm), yellow for early or late edge hours, and plain for hours most people would consider off the clock. The column (or columns) where the most timezones land in core hours simultaneously is highlighted as the best overlap.
Conversions are computed using each timezone’s real rules for today’s date, not a fixed offset, so daylight saving time is handled automatically and correctly, in every zone, without a manual adjustment.
A worked example
A team split across New York, London, and Mumbai never gets all three into core working hours at the same time. The best available overlap covers two of the three zones at once, and that maximum is tied across a fairly wide band of hours (roughly UTC 8 through 16), not one narrow peak. The grid highlights every tied hour, and hovering a cell shows exactly which zone is at the edge of its day at that point, so you can pick the specific slot that’s least disruptive for whoever draws the short straw.
Questions people ask
Why show UTC hours across the top instead of one person's local time?
UTC is the one reference that doesn't shift depending on whose timezone you'd otherwise anchor to. Every zone's local hour is read off the same UTC column, so adding or removing a timezone never requires re-reading the whole grid.
How is daylight saving time handled?
The planner reads each timezone's actual rules for today's date directly from your browser's timezone database, rather than a fixed offset, so it's automatically correct whether or not a given zone is currently observing daylight saving time, and stays correct as clocks change throughout the year.
What counts as "core hours"?
9am-6pm local time is treated as core working hours, 7-9am and 6-9pm as edge hours usable for early or late calls, and everything else as off-hours. These are reasonable defaults, not a rule. Use the grid's actual local-time labels (hover any cell) to judge what's workable for a specific team.
Can I plan for a specific future date, like next Tuesday?
The grid always reflects today's date. Since most timezones' UTC offsets stay stable for weeks or months at a time, today's overlap window is normally accurate for a meeting in the near future too. The exception is the small number of days right around a daylight-saving transition in one of your selected zones.