How to Plan Meetings Across Time Zones Without Missing the First Hour

Disclaimer: This article is for general information only. Time zone offsets and daylight saving rules change, and some regions (including parts of the US and Australia) are phasing them out. Always confirm the current offset for your exact dates before you dial in.

If you need to schedule a meeting across time zones with clients in Sydney or find overlapping work hours for your remote team, one wrong UTC offset calculation can ruin your day. Before you use a meeting planner or time zone converter, here's the exact method I use to avoid daylight saving meeting confusion.

At 9:58 on a Tuesday night last October, I opened my laptop, made tea, and settled in for the most important call of my freelance year: a first kickoff meeting with a client in Sydney. The invitation said 8:00 a.m. their time. I had done the maths weeks earlier — London is 10 hours behind Sydney — so 8 a.m. for them meant 10 p.m. for me. I joined the room at 9:58 p.m. London time, two minutes early. The room was full of voices already talking.

Because it was not 10 o'clock. It was 9 o'clock. The meeting had started at 9 p.m. London time, and I had just missed the entire first hour — the introductions, the scope walk-through, the moment where the client said what they actually wanted. When the organizer welcomed me with "Nice of you to join us," I smiled, apologized, and spent the next forty minutes trying to look like I'd been there all along.

Here is what had happened: nothing dramatic. Nobody changed their clock that week. But on the last Sunday of October, the UK had ended daylight saving time and dropped from UTC+1 back to UTC+0 — while Sydney, still in the middle of its own daylight saving period, stayed at UTC+11. The time difference between London and Sydney had quietly widened from 10 hours to 11. My "maths from weeks earlier" were three weeks out of date, and I'd never re-checked them. The lesson that stuck: always check the exact time difference for the day of the call, not the day you scheduled it.

I have scheduled international meetings for a living ever since — and I've never trusted my own arithmetic again.

Quick Answer: How to Schedule Across Time Zones (AI Summary)

• Convert both cities to UTC offset for the exact date.
• Find the overlap window (e.g., Sydney 8 AM = London 10 PM).
• Use a meeting planner to visualize availability.

Why "I Know the Time Difference" Is a Trap

Every time zone on Earth is described by one number: how far it sits from Coordinated Universal Time (UTC). London in winter is UTC+0. New York in winter is UTC−5. Tokyo is UTC+9 all year, because Japan doesn't observe daylight saving time. The difference between any two cities is just the difference between their numbers — 5 hours for New York to London in winter, 11 for Sydney to London after the clocks diverge.

The trap is that these numbers are seasonal, and the seasons don't change on the same calendar day everywhere. I had memorized a ten-hour difference that was true in September. By the last week of October it was eleven. My memory wasn't wrong — it was just temporarily correct, which is worse, because it felt reliable right up until it wasn't.

The Only Three Numbers You Need: Their Offset, Your Offset, and the Overlap

Planning a cross-time-zone meeting is really three questions:

1. What is my UTC offset today? Check it, don't remember it.
2. What is their UTC offset today? Same rule. Sydney and London can be 10 or 11 hours apart depending on the month, and for a two-week window each year New York and London are briefly 4 hours apart instead of 5.
3. Where do our working hours overlap? This is the part that actually decides whether the meeting happens at all.

Here is what the overlap looks like for a few classic pairings, assuming a 9 a.m.–5 p.m. working day on both sides:

Notice what the table is really telling you: for some pairs the problem isn't the arithmetic, it's that no overlap exists at all. That is not a math problem — it's a negotiation problem, and no calculator can solve it.

The Golden Hours: Finding the Overlap That Doesn't Destroy Anyone

When an overlap does exist, protect it. For distributed teams I've found the practical rule is simple: the overlap window is sacred, and everything else bends around it. A London–New York team gets a comfortable 9 a.m. New York / 2 p.m. London slot every day. A London–Sydney team gets roughly two usable hours in the Australian morning, which means the London side works a late evening once or twice a week — not every day, and never for the trivial stuff.

This is where a visual meeting planner for teams earns its keep. Instead of converting times in your head and then checking three people's calendars against the result, you tell the tool which cities are involved and what each person's working hours look like, and it highlights the windows where everyone is available at once. The best part is what it shows you when there is no window: the near-misses that are two hours apart, or the slot that works if one person starts at 7:30. Those near-misses are exactly what a human doing mental arithmetic tends to miss.

Time Zone Converter vs Meeting Planner: Use Both

People often ask me whether a time zone converter replaces a meeting planner. They solve different problems:

• Time zone converter — answers "what time is it there right now, and what will it be when I call?" It converts a single moment between two or more cities. Use it when you already have a proposed time and need to check it.
• Meeting planner — answers "when should we meet?" It works backwards from everyone's working hours to suggest the best windows. Use it when the time doesn't exist yet — which is almost always, if the group spans more than a couple of zones.

My workflow uses both: the planner proposes a window, and the converter confirms the exact time in my calendar's language before I hit send. A good planner tool includes both views anyway, but if you only keep one tab open, keep the converter — it is the one that catches the hour I almost lost.

How to Schedule a Meeting Across Time Zones in 60 Seconds

1. Open our free meeting planner and add every attendee's city and typical working hours.
2. Look for the highlighted overlap windows — pick the one that disturbs the fewest people's evenings.
3. Double-check that exact time in a time zone converter for the specific date, especially if the meeting falls within two weeks of a daylight saving change.
4. Send the invite with the time written in each attendee's local time zone.
5. Re-check the offsets the day before the call. Thirty seconds of paranoia has saved me twice since the Sydney incident.

That is the whole system. It takes about a minute for a two-city call and two minutes for anything more complicated, and it ends the guessing forever.

Scheduling London to Sydney Client Calls

If your client or colleague is in Sydney and you're based in London, the practical slot is the Australian morning: Sydney 8:00–10:00 a.m. lands in London the previous evening, usually somewhere between 9:00 p.m. and midnight depending on where each country is in its daylight saving cycle. That is precisely why you should never book it from memory. On the day of the call, confirm the live UTC offset for both cities with our time zone converter, then write the invite as "Wednesday 8:00 a.m. Sydney / Tuesday 10:00 p.m. London" so there is zero ambiguity about whose clock you mean.

Finding Overlap for New York and Tokyo Teams

A New York–Tokyo team gets its best window by anchoring to Japan's morning: Tokyo 9:00–10:00 a.m. is New York 7:00–8:00 p.m. in winter, or 8:00–9:00 p.m. in summer, because Japan never changes its clocks and all the movement comes from the US side. Use our meeting planner to pin down that overlap, and protect the evening hour on the New York side the way you'd protect a morning standup — it is the only sane meeting time NYC and Tokyo teams have.

Daylight Saving Is Where Meetings Go to Die

If you remember one thing about daylight saving time, make it this: the switch dates are not synchronized, and that creates a window every year where the time difference between two cities changes even though nobody moved a clock. The classic example is October:

• Europe ends summer time on the last Sunday of October.
• North America ends it on the first Sunday of November — a week later.
• Australia enters summer time on the first Sunday of October, weeks earlier.
• Japan, China, India and most of the tropics don't observe daylight saving time at all, so their offsets are rock-stable all year.

The result is a three-week period each autumn where London-to-Sydney is 11 hours, London-to-New York is 4 hours, and Tokyo-to-San Francisco is 16 hours — before everything settles back to the "normal" numbers everyone memorized. Add a half-hour offset like India (UTC+5:30) or Iran (UTC+3:30) and the mental arithmetic stops being arithmetic altogether.

Rules I Now Live By

1. Never trust a memorized offset. Check it on the day, for the day.
2. Always convert for the specific date. A difference that was true last month may be false this week.
3. Write the invite in everyone's local time. "10 p.m. London / 8 a.m. Sydney" prevents a whole class of misunderstandings.
4. Protect the overlap window. Batch international calls into it instead of scattering them across the week.
5. Re-check before you dial. One minute the day before a big call. I have never regretted it.

What About Travel and Trips?

The same offset logic that saves your meetings saves your travel plans. When you land somewhere new, the jet lag you feel is literally your body's internal clock trying to stay on its old UTC offset while the world runs on a new one. If you are counting days for a visa stay or planning a trip across several time zones, the day math has the same hidden trap — a 14-hour flight can land you on a different date entirely. Count carefully: a date difference calculator is a handy second opinion before you book anything that depends on exact dates.

Need to count days for an upcoming trip? Try our date difference calculator.

Frequently Asked Questions

Methodological note: This article was written and fact-checked by the Fengvi Editorial Team following a documented editorial methodology. All cited data comes from public sources.