World Time Meeting Planner: Practical Tips and Common Mistakes
Reviewed by the FreeOnline.fyi team · Updated 2026-09-16
Why the date field matters
A time-zone offset is not a fixed number. It is a rule that changes with the calendar, which is why the planner asks for a meeting date alongside the two cities: the tool applies the daylight-saving rules that are in force on that specific day instead of reusing a stale winter offset in July.
Take London and Los Angeles. For most of the year the gap is eight hours, so London's 08:00–18:00 workday lands on Los Angeles 00:00–10:00, and the only shared hour block is Los Angeles 08:00–10:00, which is London 16:00–18:00 — a two-hour window. But in the roughly three weeks each spring when the US has already sprung forward and the UK has not yet, the gap shrinks to seven hours and the same two cities suddenly share three hours. Same cities, same clocks, different answer.
Southern-hemisphere cities flip the other way. Sydney, Auckland and Santiago move their clocks in the opposite part of the year, so a June meeting and a January meeting are not mirror images in the way people expect. Pick the date first, then look at the hours — never the reverse.
Reading the overlap timeline
The centrepiece of the World Time Meeting Planner is a 24-cell horizontal strip, one pill-shaped chip per hour of the chosen date. Chips inside the shared working window are filled with the accent colour and sit over a soft daylight band, so you can see the answer before you read a single number.
Above the strip sits the headline, phrased in both clocks, for example: "Best overlap: 15:00–18:00 (your time) / 09:00–12:00 (their time) — 3 hours." Below it is a paired table with one row per hour: your city's time, their city's time, a +1 or −1 day marker, and both UTC offsets. That day marker matters more than it looks — it is the difference between scheduling someone for Monday morning and accidentally booking their Sunday night.
Everything recomputes live as you change a city or the date, so there is no submit button and nothing to reload. If you want a second opinion on a region's current rules, the IANA time zone database is the canonical source behind almost every calendar app you use.
What counts as a workable hour
The tool counts an hour only when both cities are inside 08:00–18:00 local time. An hour that starts at 09:00 in both places qualifies; an hour that runs 18:00–19:00 in either city does not. That definition is deliberately narrow, and it is worth knowing before you argue with the result.
Real teams often accept 07:00 or 19:00 for a short call, especially once a week. So treat the highlighted block as the honest default, not the only option. If nothing qualifies, the planner does not silently widen the window — it shows the closest two-hour block and labels it clearly as outside normal hours, which is a much better starting point for negotiation than an empty result.
One more detail: the chips snap to whole hours, but some zones are not on the hour. India is UTC+05:30, Nepal UTC+05:45 and the Chatham Islands UTC+12:45. Read the UTC offset column in the table if a :30 or :45 offset is involved, and remember a one-hour call needs a start time plus room to finish, not just a free slot.
Common offset-math mistakes
The most frequent error is direction. People know the offset but apply it the wrong way, turning a 15:00 London slot into 07:00 in New York instead of 10:00. The paired table removes that guesswork because both columns are printed, side by side, for the same row.
The second error is forgetting the day shift. A Tuesday 09:00 call in Sydney can be Monday afternoon in Los Angeles, and the planner marks that with a +1 or −1 flag on the row rather than leaving you to notice. The third is treating half-hour zones as a rounding detail; a 30-minute offset is enough to push a call past the end of someone's working day.
Finally, don't trust your memory of a DST rule you learned years ago. Rules do change, and official bodies publish the current definitions — the NIST time and frequency resources are a good starting point for US practice, and your calendar app will normally agree with the planner, but confirm anything unusual.
When no overlap exists
Some pairs genuinely share nothing. London and Sydney sit about eleven hours apart during the southern summer, so London 08:00–18:00 maps to Sydney 19:00–05:00 — no hour puts both cities inside a normal day. The planner will say so and offer the nearest two-hour window with a warning attached, rather than inventing a slot.
When that happens, the fix is structural, not arithmetic. Rotate the awkward slot so the same person is not always the one on a 05:00 call, split a long meeting into two shorter ones that each fit a friendlier window, or move the discussion to written updates and keep the live call for decisions only.
If you are juggling more than two locations, it helps to look at the whole day rather than a single pair. Our world time meeting planner handles two cities at a time; for three-way calls, run the pairs and pick the hour that appears in the most results.
Verify before you send the invite
The city list behind the tool is a bundled static set of roughly 60 major cities mapped to IANA zone IDs — there is no live lookup service. That keeps it fast and private, but it means a colleague in a smaller town may not appear by name. Choose the nearest major city that shares their zone, then confirm the offset in the table before you commit.
City lists and DST rules are also not the whole story: government decisions occasionally change a zone, and software updates lag behind. Treat the planner as a reliable first pass and a sanity check, not a guarantee, and let the attendee confirm their own local start time on the invitation.
One last habit that saves goodwill: keep the invite itself short. Write the meeting time in both zones, state the duration, and cut repeated phrasing — an online word frequency counter is a quick way to spot the same sentence appearing three times in an agenda. If you want other small utilities for distributed work, they are all collected on FreeOnline.fyi.