Add every participant's city and find a meeting time that works for the whole team, without juggling multiple time zone conversions by hand.

Meeting Planner

Add participant cities and drag the time slider to find a time that works for everyone.

09:00

Add a few cities above to build your meeting time table.

Picking a Time That Doesn't Punish Anyone

Scheduling across two time zones is arithmetic. Across five it stops being arithmetic and becomes a negotiation, because past roughly eight hours of spread there is no hour that is convenient for everyone — someone is taking the call before breakfast or after dinner. The planner's job is to make that trade-off visible before the invitation goes out, rather than after someone declines it.

Two things are worth checking on the rows above. The first is whether any participant lands outside roughly 8am to 7pm, which is where goodwill starts to erode — particularly for a meeting that recurs weekly. The second is the date: once a group spans enough of the globe, the same moment falls on different calendar days for different people, and "Tuesday's call" can genuinely be Wednesday at one end.

For a recurring meeting, the fair answer is usually to rotate which region takes the awkward slot rather than fixing one time forever. And if the group spans a daylight saving boundary, the working time drifts by an hour twice a year for some participants but not others — each city page lists the exact dates its clocks change, which is the moment to revisit a standing invitation.

Comparing just two cities? The time zone converter goes deeper for a pair, with a full 24-hour table and a worked-out window when both cities are inside business hours. To watch a handful of cities live rather than plan a specific time, the homepage comparison keeps up to 8 clocks side by side.

Two Zones Rather Than a Whole Team?

The planner is built for groups. For a single pair, a converter page goes further: a full 24-hour table, the hours both sides are inside normal working time, and the date the gap between them next changes. These are the pairs distributed teams schedule across most.

All time zone converters →

Common Team Corridors

Named cities rather than zone abbreviations, which is usually how a team actually describes itself. Each page works out the overlap between the two ends and flags the dates their clocks stop moving in step.

Before You Send a Recurring Invitation

A standing meeting survives a clock change only if you know which participants are moving and which are not. Roughly half the world adjusts its clocks and half does not, and those that do pick different dates — the UK moves in late October, the US a week later, and India never. For those weeks the gap between two participants is not what it was the month before, and nobody gets a notification about it.

For US participants the answer differs by state — two states ignore the change entirely and fourteen more are split across two time zones. If your meeting also has to dodge public holidays, the US federal holiday list through 2036 is the other half of the problem.

Frequently Asked Questions

How does the meeting planner work?

Add each participant's city, then drag the hour slider. Every row updates to show what that moment is on each participant's own clock, so you can see at a glance which hours are civilised for everyone and which are not.

How many cities can I add?

As many as your meeting needs. The rows stay readable well past the point where a mental calculation would have given up, which is the whole reason to use a planner rather than converting each pair by hand.

Does it handle daylight saving time?

Yes. Each city is converted using its current daylight saving rules, so a city that has just changed its clocks shows its new offset immediately. If your meeting is weeks away and falls across a clock change, check the relevant city page for the exact changeover date before you send the invitation.

What is a reasonable meeting time across many time zones?

Once a group spans more than about eight hours, no hour suits everybody, and the practical question becomes who takes the inconvenience. Early morning for the westernmost participant against early evening for the easternmost is usually the fairest compromise — and worth rotating if the meeting recurs.

What if I only need to compare two cities?

Use the time zone converter instead. It gives a full 24-hour table for the pair and works out the window when both cities are inside business hours, which is more detail than the planner shows per city.

Planning a call across three or four time zones? Add each city and drag the slider to spot the overlap that works for everyone.