Find an hour that works everywhere ZONES
Scheduling across time zones is how someone ends up on a 6am call. Add the cities, set the hours people keep, and see the day laid out, with the window everyone is awake for marked.
The meeting
How it works
Reading the grid
Each row is a city and each column an hour of the day, read in the top city's local time. The number in a cell is that city's own clock hour for that column, so one column can be late evening in New York and next morning in Tokyo, which is the whole difficulty. The tinted cells are working hours; a column outlined in full is an hour every city is awake for. The offsets, daylight saving and the half-hour zones come from your browser's time-zone data, exact for the day shown.
Questions people ask about ZONES
Why are some time zones half an hour or 45 minutes off?
Because a zone’s offset is a government’s choice, not a rule of geography. India is UTC+05:30, Tehran +03:30, Kathmandu +05:45, Adelaide +09:30 (+10:30 in its summer) and the Chatham Islands +12:45 (+13:45 in summer). The exact offset for the day shown is written beside each city.
In such a zone each cell shows its minutes under the hour, so 14:30 reads as 14 over :30. Working hours are judged by the hour: 8:30 counts as before a 9 o’clock start.
Does it handle daylight saving?
Yes. The offsets come from your browser’s own time-zone database, and every hour in the grid is worked out for that instant, so a day on which the clocks change is drawn as it happens. Use Prev day and Next day to look at the date of the meeting rather than today. It matters most across hemispheres: Europe and south-eastern Australia change on different dates in opposite directions, so the gap between London and Sydney changes more than once a year.
What do the colours in the grid mean?
Tinted cells are working hours: from the start hour up to, but not including, the end hour, so 9 to 17 means 9:00 to 16:59. The hour before the start and the hour beginning at the end are marked early or late, but doable. The rest is asleep. A column outlined top to bottom is an hour in which every city is within working hours. The same hours apply to every city. A start later than the end, such as 22 to 6, is a night shift and runs past midnight.
What if no hour suits everyone?
The line under the grid says so, gives the most cities that are at work in the same hour (for example 3 of 4), and names when that overlap starts in the top city’s time. When there is an hour for everyone, it gives the longest unbroken run and its start and end instead. The early-or-late cells show where a meeting costs someone an hour of their evening or morning rather than their sleep.
Which city is the grid read in?
The first in the list. Its day runs from midnight to 23:00 across the columns, and every other row shows its own clock at each of those hours. It opens on your own zone if it is in the list (otherwise UTC), with New York, London and Kolkata beside it. A city you add goes to the bottom, so to read the grid in another city’s time, remove the ones above it. The cities and the working hours are remembered in this browser.
Does it know about weekends or public holidays?
No. Every day of the week is treated alike, so a Friday afternoon in Los Angeles is marked as working hours in Sydney, where it is already Saturday morning. Public holidays are not known either. Check the day in each city before you send the invitation.
Can I add a city that is not in the list?
Not by name. The list holds 51 cities and UTC, one for each common zone. A place not listed shares its zone with one that is: Manchester keeps London’s clock, Lyon keeps Paris’s and Osaka keeps Tokyo’s, so choose that city.
Doing this often? OBSCURA Pro saves the result of every tool outside the Workspace and includes the paid applications. This planner has nothing to save: its cities and hours stay in this browser. Everything is US$5 a month or US$48 a year.