Time Zones
Meeting Planner
Find a meeting time that works across multiple time zones at once.
Meeting Planner
Overlapping working-hours window
- UTC: 09:00 – 17:00
- Europe/London: 10:00 – 18:00
A single time-zone conversion answers one question; scheduling a meeting across several time zones at once is a genuinely harder problem, since a slot that's convenient for one participant can be the middle of the night for another.
Distributed teams spanning three or more time zones are the clearest real use case for this tool, since manually cross-checking several people's local working hours by hand — especially when some of those zones observe Daylight Saving Time and others don't — is exactly the kind of error-prone task this tool is built to remove.
How the Meeting Planner works
You propose a meeting time in one "home" time zone and list every participant's zone; the tool converts that same instant into each zone using the same IANA-based method as the Time Zone Converter, then flags which participants would fall outside a normal working-hours window you can configure — solving for a workable slot across the whole group at once, rather than one conversion at a time.
This tool builds directly on the Time Zone Converter's underlying conversion method but adds the specific multi-participant, working-hours-window logic that a single pairwise conversion doesn't need — the two tools solve genuinely different-shaped problems even though they share the same underlying time zone data.
Worked example
A proposed 09:00 US Eastern time meeting converts to 14:00 in London, 15:00 in Paris and Berlin, and 22:00 in Singapore the same day — a reasonable time for the first three participants but very late evening for the one in Singapore, which the tool flags rather than presenting the slot as equally convenient for everyone.
Edge cases this tool handles correctly
- No fully convenient overlap sometimes exists
- A group spanning enough time zones — for example, the US West Coast and East Asia together — can genuinely have no overlapping conventional working-hours window at all; in that case the tool shows the least-bad available option rather than falsely presenting a perfect match.
- Participants in non-DST zones
- A participant whose zone doesn't observe Daylight Saving Time needs their offset re-checked independently near a transition week elsewhere in the group, the same caveat that applies to the Time Zone Converter.
- Public holidays aren't included
- The planner computes local clock time only — it doesn't know about any participant's local public holidays; check the per-country Holidays pages separately if that matters for scheduling.
- All participants in the same zone
- If every participant happens to share the same time zone, the planner effectively reduces to a single-zone scheduling check — there's no meaningful cross-zone conversion needed, though the tool still handles that case correctly rather than requiring at least two distinct zones.
- Very large groups
- There's no meaningful upper limit to how many participants' zones can be checked at once, though beyond a certain group size, finding any single mutually convenient slot becomes increasingly unlikely regardless of how the calculation is done.
- Rotating an unfair time slot fairly
- For a recurring meeting where no single slot is convenient for every zone, some distributed teams deliberately rotate which region bears the inconvenient early or late slot from one occurrence to the next — a scheduling policy choice the tool can help evaluate by checking a few different candidate times, though the rotation decision itself is made by the team, not computed automatically.
Frequently asked questions
What if there's no time that works for everyone?
The tool shows the option with the fewest participants outside their working hours rather than claiming a perfect match exists — some globally spread groups genuinely have no fully convenient overlap.
Can it suggest rotating an inconvenient slot fairly across a recurring meeting?
Not automatically — the tool evaluates individual proposed times; deciding to rotate which region takes the inconvenient slot on a recurring meeting is a team scheduling policy the tool can help you check candidate times for, not something it computes on its own.
How many time zones can I compare at once?
There's no fixed limit in the underlying calculation; the interface is designed around typical small-to-mid-size meeting groups.
Does it know about public holidays in each region?
No — it computes local clock time only; check the per-country Holidays pages separately.
Is the underlying time zone data the same as the Time Zone Converter?
Yes, the same IANA-based conversion method.
Does it still work if everyone is in the same time zone?
Yes — it simply reduces to checking everyone's shared local working hours, with no conversion needed.
Can I save a meeting plan to reuse later?
Each plan is generated from the inputs given at that moment; reusing the same group of zones for a future meeting just means re-entering (or bookmarking a link with) the same participant list.