How to schedule meetings across time zones

Coordinating a call between New York, London and Singapore is mostly arithmetic — but the mistakes are expensive. This guide covers the method we built Timezone Matcher around: find the real overlap, write times that can't be misread, and keep it fair when no slot is perfect.

Remote and distributed teams lose hours every week to scheduling friction: the 7am call someone forgot was their time, the invite that landed an hour off after the clocks changed, the recurring meeting that always lands at midnight for one teammate. None of it is hard to avoid once you follow a few rules.

1. Anchor everything to UTC, then translate

Pick one neutral reference — UTC — and express the candidate time in it first. "14:00 UTC" is unambiguous; "2pm" is not. From the UTC anchor, translate into each participant's local time using their IANA zone (e.g. America/New_York, Europe/London, Asia/Singapore), which carries the correct daylight-saving rules. This is exactly what a world clock or time-zone converter does for you, so you never reason about offsets by hand.

2. Find the working-hours overlap, not just a shared minute

A meeting that technically "works" at 11pm for one person isn't a working meeting. Map each participant's acceptable window (say 09:00–18:00 local) onto a shared timeline and look for where the bands overlap. With two or three nearby zones there's usually a comfortable block; across US–Europe–Asia the overlap can be 30–60 minutes or none — which tells you to rotate (see below). Timezone Matcher shades these overlapping hours automatically so the answer is visual, not mental.

3. Respect daylight-saving transitions

The single most common scheduling bug: a recurring meeting drifts by an hour because one region changed clocks and another didn't. The US, EU and Australia switch on different dates, and many countries (most of Asia, Africa) don't switch at all. Always schedule against named zones, not fixed offsets, so the conversion follows each region through its own transition. If you maintain a recurring invite, re-check it around late March and late October.

4. When no slot is fair, rotate

If the only overlap is painful for someone — early morning in California or late night in Sydney — don't make the same person absorb it every week. Rotate the burden: alternate between a slot that's early for the Americas and one that's late for Asia-Pacific, or record the session and let the off-hours region watch asynchronously. Fairness over weeks beats a single 'optimal' slot that quietly taxes one timezone.

5. Send invites that can't be misread

Put the time zone in writing and let the calendar do the conversion. A good invite states the time with its zone ("Thu 15:00 CET / 09:00 ET"), uses a calendar event so each attendee sees it in their own local time, and avoids bare "2pm" with no zone. For one-off coordination with people outside your calendar system, share a link that shows the time pre-converted for them rather than asking them to compute it.

Do it in one click

Timezone Matcher does steps 2–5 for you: add each participant's city, see the overlapping working hours shaded across the day, and generate a meeting invite that everyone reads in their own local time.

Open the meeting grid →

Frequently asked questions

What is the best time to schedule a meeting across time zones?

The best time is the widest overlap of everyone's working hours. For US East Coast and Western Europe that's typically 13:00–17:00 UTC (morning in New York, afternoon in London). When the Americas, Europe and Asia are all involved, the overlap is small or zero, so you either accept one short shared window (around 07:00–09:00 UTC) or rotate the inconvenient slot between regions.

How do I avoid daylight-saving time mistakes in recurring meetings?

Schedule against named IANA time zones (like Europe/Madrid), never against a fixed UTC offset. Calendar tools that store the zone will follow each region through its own DST transition automatically. The risk window is late March and late October, when different regions change on different dates — re-check recurring invites around then.

What time zone should I put in a meeting invite?

State the time in at least one explicit zone and let the calendar convert for each attendee — for example 'Thursday 15:00 CET (09:00 ET / 22:00 SGT)'. Never write a bare local time with no zone. A calendar event is best because every attendee sees it in their own local time automatically.

How can I find overlapping working hours quickly?

Use a tool that shades each participant's working window on a shared 24-hour timeline. Timezone Matcher does this: add each city and the overlapping hours are highlighted, so you can see at a glance whether a comfortable slot exists or whether you need to rotate.

Is it fair to always meet at the same time across regions?

Often not. A single fixed slot usually favours one region and pushes another to early-morning or late-night repeatedly. Rotating the meeting time, or recording sessions for the off-hours region to watch asynchronously, spreads the inconvenience and is generally fairer for distributed teams.

Tool

Meeting grid + working-hours overlap

Tool

Convert a specific time between zones

Guide

Best hours to work with remote teams