How to Schedule Meetings Across Multiple Time Zones: A Practical Guide

Published 12 July 2026 · 7 min read

Scheduling a meeting with a team spread across three continents sounds straightforward until you actually try to do it. You pick what feels like a reasonable time, send the calendar invite, and then someone in Singapore replies to let you know it's 11pm for them. Again.

Time zone scheduling is a skill, and like most skills, it gets much easier once you understand the underlying mechanics. This guide walks through exactly how to approach it — from identifying your overlap window through to running a fair rotation when no good window exists.

Why it's harder than it looks

The obvious problem is the offset: if London is 5 hours ahead of New York, a 9am meeting in New York is 2pm in London. Fine. But most teams aren't just two cities. Add Singapore (8 hours ahead of London), and you're looking for a time that works across 13 hours of spread. That's before you account for daylight saving, which shifts offsets by an hour at different points in the year — and transitions happen on different dates in different countries.

On top of that, "working hours" aren't universal. Some cultures work a compressed week. Some offices observe different public holidays. Some teams expect you to be available at 8am; others start at 10. None of this is insurmountable, but it does mean you can't just look at a clock and eyeball it.

Step 1: Map your locations and their offsets

Before you can find a good time, you need to know where everyone actually is — specifically, their UTC offset on the date of your meeting. UTC is the universal reference point that doesn't change with DST, which makes it the most reliable anchor.

A good time zone planner will handle this automatically. You add your cities, set your date, and it calculates the correct offsets including any DST adjustments. If you're working from memory or a static table, be careful: offsets are accurate only for the specific date, not year-round.

Step 2: Identify your working hour windows

The standard assumption is 9am to 6pm local time, though you can adjust this based on what you know about each team's actual norms. Once you've mapped every city to UTC, you can see the full picture: which hours are simultaneously within business hours for all locations.

There are three scenarios you'll encounter:

• Good overlap (teams within 4–5 hours of each other). You'll typically have a 3–5 hour mutual window. This is comfortable — pick a time near the middle so neither side is at the edge of their day.
• Marginal overlap (teams 5–9 hours apart). You might have 1–2 hours, often at the very start or end of someone's workday. This is workable but requires commitment from at least one side to meet at an inconvenient time.
• No practical overlap (teams 9+ hours apart). A genuinely zero-overlap situation. Someone will be outside business hours no matter what you do. The question becomes who, and how to make it fair.

Step 3: Work from the overlap bar, not the clock

When you're trying to find a workable slot, think visually rather than arithmetically. A visual timeline that shows all your cities side by side makes it immediately obvious where the green windows are — the periods when everyone's within business hours — versus where it drops into evenings or early mornings.

The best slot is usually not the one that's most convenient for the majority. It's the one that distributes inconvenience most fairly. If you have a team of eight in London and one person in Tokyo, you might decide it's reasonable for the Tokyo person to take a late call occasionally. But if you have equal representation in both cities, rotating who bears the early morning is the right call.

When there's no good overlap: the rotation model

For teams with no practical overlap — common for NZ-to-US calls or Europe-to-Asia-Pacific calls — the fairest approach is a rotation. Instead of the same person always taking the 7am or the 10pm, you alternate which team absorbs the inconvenience each week or each fortnight.

To run this well, be explicit about it. Put the rotation schedule in writing. Acknowledge in your meeting invites which time zone is making the sacrifice this week. A bit of visible recognition goes a long way. Nobody minds an early call if they know it'll be someone else's turn next time and the team acknowledges the effort.

Practical tips that make a real difference

A few things that are easy to miss when you're still building this habit:

• Always include the time zone in your invite. "3pm" is meaningless without context. "3pm London (GMT+1)" is not. Even better, list the local time for every city on the call in the invite description.
• Check your dates near DST transitions. Many scheduling mistakes happen in the two weeks after a transition, when one country has changed clocks and another hasn't yet. Always verify for dates near the end of March, October and November.
• Send a shareable link, not just a time. A URL that encodes the cities and selected time means anyone can open it and see their local equivalent. No manual conversion required.
• Set a regular cadence and protect it. Ad hoc scheduling is where time zone confusion causes the most friction. Once you've found a slot that works for your team, lock it in as a recurring meeting rather than renegotiating every week.

Handling DST transitions mid-schedule

If you have a recurring weekly meeting, you'll hit DST transitions at some point. The meeting that was at 9am London / 4pm Singapore might suddenly be 8am London / 4pm Singapore after the UK clocks change, or the gap might shift in the other direction. Set a reminder to review your recurring meeting times whenever a relevant country transitions, which is typically in late March and late October for northern hemisphere countries.

Time zone rules and daylight saving dates are set by individual governments and can change with little notice. Always verify offsets for specific upcoming dates, particularly near known transition periods.