Find a meeting hour that works everywhere

How Meeting Planner works

Dates are computed from your device's clock and timezone settings, both of which stay on the device. Nothing about when you opened the page is reported. Daylight-saving rules come from your browser's own database, so the conversion follows your region rather than a server's guess.

That is the whole architecture: static files, one script, no upload endpoint to leak or log. Close the tab and the work is gone.

Why the grid is anchored to UTC

Every other column shifts twice a year; UTC never does. Building the table on UTC means one row is one instant everywhere, and daylight saving is handled when each cell is converted — not by adding an hour by hand and hoping the other country changed on the same date.

That matters because countries switch on different weekends. The United States moves in March and November, the European Union in March and October, and the southern hemisphere in between. A meeting that works in July can be an hour out in December.

What counts as a workable hour

The shading uses 09:00 to 18:00 local, which is the usual definition of a polite call. The outlined rows are the ones where every selected city is inside that window at the same moment — often a two- or three-hour band, sometimes none at all.

When the overlap is empty the honest answer is asynchronous: a written update and a recording beats a 22:00 call for half the team. The grid makes that visible instead of leaving it to whoever is most senior to decide.

Good to know

• Works offline once loaded, including on flights and in locked-down networks.
• No file size limit beyond your device's own memory.
• Free to use, with no account and no usage counter.
• Results are produced locally, so they are not logged or shared with anyone.

Questions