Hour-by-hour comparison
Hours shown in each city's own local time for the chosen date. The header row is the reference city's day, midnight to midnight.
How to use the planner
Pick the meeting date, then add up to five cities — your own first, so the header row reads in your day. Each row shows that city's local clock hour by hour, colored by how humane the hour is: green for core business hours (9:00–17:00), amber for the stretchable edges (early morning and evening), red for the hours when reasonable people are asleep. Scan for columns where every row is green — those are your best slots. No all-green column? The least-bad options are the ones trading green for amber, never for red.
The classic pairings — and the impossible one
US East Coast ↔ Europe is the easy one: New York mornings are London/Paris afternoons, so 9–11 AM Eastern works almost every day. US West Coast ↔ Europe is tighter — only 8–9 AM Pacific catches London before evening. US ↔ India favors early US mornings (8 AM Eastern is 5:30–6:30 PM in India, depending on DST). And the famous impossible triangle is San Francisco – London – Singapore: there is no hour that's green for all three; someone is always in the red. Teams that span it usually rotate the pain — alternating who takes the late call — or split into two overlapping meetings.
Habits that make global meetings kinder
State the time zone every time you name a time — "3 PM" with no zone causes more missed meetings than any calculation error. For recurring calls, remember the DST wobble: a meeting pinned to New York time shifts by an hour for Sydney twice a year, in opposite directions. Record anything important, because someone worth including was probably asleep. And when two slots tie, pick the one kindest to the person who's been taking the worst slot lately — fairness compounds.
Frequently asked questions
Why does the comparison change when I change the date?
Daylight saving. The planner applies each city's actual rules for the chosen date, so the alignment between cities genuinely differs between, say, March and April — that's the tool being right, not wrong.
Can I plan for someone working night shifts?
The colors assume standard business hours, but the local times shown are exact — just read the row against their real schedule and ignore the coloring for that city.
How do I share the result?
Once you've found the slot, send it with the converter: set the agreed time in your city and everyone can read their own local equivalent from the table — no screenshots needed.
Related: the world clock for a live view of all your cities, and daylight saving time explained for why the alignment shifts twice a year.