Meeting Time Zone Planner

Scheduling Meetings Across Time Zones

The Challenge of Global Teams

Scheduling a meeting when your team spans multiple continents is one of the most persistent friction points in remote and distributed work. When it is 9 am in London, it is 10 am in Paris, 2 pm in Dubai, 4:30 pm in Mumbai, and 5 pm in Bangkok — and simultaneously 4 am in Los Angeles. There is rarely a time that is perfectly convenient for everyone, but there are almost always windows that are merely inconvenient for the fewest people.

The goal of a meeting planner is to surface those windows objectively, without relying on mental arithmetic or the person who always ends up sacrificing their lunch break because they happen to be in the middle timezone.

Understanding UTC and Time Zone Offsets

Coordinated Universal Time (UTC) is the primary time standard by which the world regulates clocks and time. It has no daylight saving time adjustments — it remains constant year-round. Every time zone is defined as an offset from UTC: New York is UTC-5 in winter (UTC-4 in summer), London is UTC+0 in winter (UTC+1 in summer), Tokyo is always UTC+9.

When thinking about scheduling, UTC is your neutral reference point. If you say "let's meet at 14:00 UTC," there is no ambiguity — everyone can convert that to their local time. Many international teams adopt the convention of scheduling in UTC to avoid errors, especially around daylight saving transitions when offsets shift and previously agreed times can suddenly conflict.

Daylight Saving Time: The Hidden Complicator

Daylight Saving Time (DST) is observed in roughly 70 countries, but not all of them — and crucially, those that do observe it change their clocks on different dates. The United States and Canada change in early November and mid-March. The European Union changes in late October and late March. Australia changes in early April and early October (and some states don't observe it at all). India, China, Japan, and most of Africa and Asia do not observe DST.

The practical consequence is that for several weeks each year, the time difference between, say, New York and London changes from 5 hours to 4 hours because one side has changed clocks and the other hasn't yet. This is the source of countless missed calls. Modern tools that use IANA time zone identifiers (like "America/New_York" rather than "EST") automatically handle these transitions, which is why this planner uses those identifiers.

Finding Overlap Windows

The heatmap produced by this tool works by taking a reference day (today) and checking, for each 30-minute slot in the 24-hour UTC clock, whether that slot falls within each participant's stated working hours in their local time zone. A slot where all participants are available is shown in solid green. Slots with partial availability are shown in lighter green. Slots where nobody is available are gray.

The "best time" recommendation factors in meeting duration — if your meeting is 1 hour, the tool looks for a block of two consecutive 30-minute slots where the overlap score is highest, not just a single slot.

Async-First Culture: When No Time Works

Sometimes there genuinely is no overlap window. A team with members in Auckland, London, and San Francisco faces a 12–13 hour span between the two extremes — it is practically impossible to find a time that falls within business hours for all three. In these cases, the recommended approach is to adopt an async-first culture:

• Record meetings so those who cannot attend can watch on their own schedule.
• Write detailed agendas before meetings and send them out at least 24 hours in advance, allowing async input.
• Use asynchronous tools (Loom for video updates, Notion or Confluence for documentation, Slack or Teams for threaded discussion) as the primary communication channel, with meetings reserved for decisions that genuinely require real-time discussion.
• Rotate meeting times so the same person is not always the one joining at midnight or 5 am.
• Acknowledge the burden — if someone regularly takes calls outside their working hours, compensate with flexible time off or adjusted core hours.

Best Practices for Cross-Timezone Meetings

• Send calendar invites with timezone context. Always include the UTC time in the meeting title or description: "Weekly Sync 14:00 UTC." Calendar applications will convert to local time, but a UTC reference prevents confusion if someone's calendar app has the wrong timezone set.
• Keep it short. Meetings are more tolerable at inconvenient hours when they are brief and focused. A 30-minute stand-up at 7 am is far less disruptive than a 90-minute workshop.
• Use a world clock widget. Browser extensions and apps like World Time Buddy, Clockwise, or simply pinning multiple clocks in your phone's Clock app help build an intuitive sense of where your colleagues are in their day.
• Start and end on time, always. When someone is attending from 6 am or 10 pm, running over is a serious inconvenience. Rigid time discipline is a sign of respect in distributed teams.
• Designate a clear facilitator. Remote meetings drift more than in-person ones. Assign someone to keep the agenda moving, draw out quieter participants, and ensure decisions are captured and actioned.

Frequently Asked Questions