How to Schedule a Meeting Across Time Zones (2026)

Scheduling a single call between New York, London, and Singapore sounds simple until someone joins at 6 a.m. in pajamas while another person waits an hour for a host who got the hour wrong. Cross-time-zone scheduling is where good intentions quietly fall apart. This guide walks through a repeatable method you can use every time, plus the traps that catch even experienced remote teams.

Start From One Reference Time, Not Many

The single biggest mistake is doing the math in your head, twice, in opposite directions. Instead, anchor every meeting to one reference: UTC. Decide the meeting happens at, say, 15:00 UTC, then convert that single number outward to each participant. When you start from one anchor, you never accidentally add an offset where you should have subtracted it. A time zone planner does this conversion for you, but the discipline matters even when the tool does the arithmetic: think in one canonical time and translate outward.

The Five-Step Workflow

1. List every participant and their city. City beats country, because countries like the United States, Australia, and Brazil span several zones.
2. Convert each city to its current UTC offset. New York is UTC-4 in summer, UTC-5 in winter. London is UTC+1 in summer, UTC+0 in winter. Singapore is a steady UTC+8 all year.
3. Find the overlap window where everyone is inside a humane working block, ideally 9 a.m. to 5 p.m. local.
4. Pick a slot inside the overlap and rotate the pain if the overlap forces someone into an early or late hour.
5. Send the invite in UTC plus each local time so nobody has to convert.

Finding the Overlap Window

Picture three people: New York (UTC-4), London (UTC+1), and Mumbai (UTC+5:30) in June. Lay their working days on a single UTC ruler. New York 9 a.m. to 5 p.m. is 13:00 to 21:00 UTC. London 9 to 5 is 08:00 to 16:00 UTC. Mumbai 9 to 5 is 03:30 to 11:30 UTC. The only slice where all three overlap is roughly 13:00 to 11:30 UTC, which is empty. There is no time when all three are simultaneously inside normal hours.

That is the honest answer, and it is common. When the overlap is empty or razor thin, you have three options: shorten the meeting and place it at the least-bad slot, split into two regional calls, or move the content to async. Pretending a perfect slot exists just guarantees someone resents the calendar.

When Overlap Exists But Is Tight

If the overlap is only 30 to 60 minutes, protect it ruthlessly. Start on time, use a tight agenda, and record for anyone who genuinely cannot attend. Do not fill a precious shared hour with status updates that could have been a message.

The DST Trap That Breaks Recurring Meetings

Daylight Saving Time is the silent killer of recurring invites. The catch is that countries switch on different dates, and some do not switch at all. In 2026 the United States springs forward in March and falls back in November. The European Union shifts on the last Sunday of March and October. Australia, being in the southern hemisphere, moves the opposite direction. India, Japan, China, and most of Africa never change.

So a recurring 3 p.m. London to 10 a.m. New York call holds steady most of the year, but for the two or three weeks when one region has switched and the other has not, the gap shifts by an hour. Your 3 p.m. London call suddenly lands at 9 a.m. or 11 a.m. in New York. The fix: pin recurring meetings to a city, not a fixed offset, and warn the team in advance of the changeover weeks. Calendar apps usually handle this if you set the event in a named zone like America/New_York rather than a raw UTC offset.

Rotating the Pain Fairly

When no humane slot exists for everyone, fairness means sharing the inconvenience. If your weekly sync always lands at 6 a.m. for the Sydney teammate, they will burn out and quietly disengage. Rotate the meeting time across a cycle: one week favors Asia-Pacific, the next favors the Americas. Document the rotation so nobody feels singled out. A visible, agreed rotation turns an unfair fixed slot into a shared, predictable sacrifice.

Write Invites People Cannot Misread

Always include the UTC time, every participant's local time, and the named zone. A line like Tuesday 15:00 UTC = 11:00 New York (EDT) = 16:00 London (BST) = 23:00 Singapore removes all ambiguity. Avoid bare abbreviations alone, since CST means both Central US time and China Standard Time. Pair any abbreviation with a city or an offset.

Async-Friendly Scheduling

The best cross-zone teams treat meetings as expensive and rare. Before booking a call, ask whether a written thread, a recorded video, or a shared document would do the job. Reserve live time for decisions, brainstorming, and relationship-building, the things that genuinely need everyone present at once. Everything else can move asynchronously, which removes the time-zone problem entirely.

A Quick Checklist

• Anchor the meeting to a single UTC time.
• Convert outward to each city, not between cities.
• Find the real overlap window before proposing slots.
• Account for DST changeover weeks on recurring events.
• Rotate unavoidable bad slots fairly.
• Write invites with UTC plus every local time.
• Ask whether the meeting needs to be live at all.

Run every cross-zone meeting through this method and you will stop the 6 a.m. surprises, the missed calls, and the quiet resentment that builds when scheduling feels rigged. Use a time zone planner to do the math instantly and visualize the overlap before you send a single invite.

Frequently Asked Questions