How to Schedule a Meeting Across Time Zones (Without Making Mistakes)

Scheduling a meeting with someone in another country sounds simple. You pick a time, send a calendar invite, and wait for them to accept. But anyone who has done it more than once knows the traps: the person joins an hour late because clocks shifted, or worse — nobody joins at all because the time was completely wrong for one side.

Time zone scheduling mistakes are more common than most people realise. And with remote work connecting people across more countries than ever, getting this right is a real skill worth developing. Here is a straightforward guide to doing it properly every time.

Understand the Difference Between a Time Zone and a UTC Offset

Before anything else, it helps to understand what you are actually working with. A time zone is a region that follows the same standard time — like Eastern Time or Japan Standard Time. A UTC offset is the number of hours that time zone sits ahead of or behind Coordinated Universal Time (UTC), the global reference point.

For example, New York in winter runs on UTC-5. Tokyo runs on UTC+9. The difference between them is 14 hours — but that number changes when the US observes daylight saving time and Japan does not.

This is where most mistakes happen. People use a fixed offset they looked up once and assume it is always correct. It is not. Offsets change with the seasons in countries that observe daylight saving time — and the change happens on different dates in different countries.

The safest approach: always use a time zone tool that calculates based on the specific date of your meeting, not a memorised offset.

Step 1 — Establish Working Hours for Both Sides

Before you even think about picking a time, find out the working hours of the person you are meeting. This sounds obvious, but it is often skipped. Standard business hours vary more than people expect:

• In many Middle Eastern countries, the working week runs Sunday to Thursday

• Some European countries have a strong lunch break culture, with reduced availability midday

• In parts of Asia, early morning start times are common, which can create more overlap with European afternoons

Ask or confirm rather than assume. A quick "what are your usual working hours?" before proposing a time saves a lot of back-and-forth.

Step 2 — Find the Overlap Window

Once you know both sets of working hours, find the window where they intersect. This is the only safe zone for scheduling a meeting that works for everyone without asking someone to join outside their normal day.

Use a meeting planner tool to do this automatically. Select both cities, enter the working hours for each, and the tool shows you the shared availability window. For some city pairs this window is generous — London and New York share around four hours of overlap on a standard weekday. For others, like Sydney and New York, the window can be just one or two hours, or require one party to meet early or late.

Knowing the overlap window upfront tells you what you are working with before you propose anything.

Step 3 — Convert the Time Correctly

Once you have identified a good time within the overlap window, use a time converter to express it in both local times before sending the invite.

Do not just write "3pm" and assume the other person will figure it out. Be explicit. Write the time in both cities — for example, "3:00 PM London time / 10:00 AM New York time" — and include the time zone abbreviation so there is no ambiguity.

If you are using a calendar tool like Google Calendar or Outlook, always set the event time zone explicitly rather than relying on the recipient's calendar to convert it. Most modern calendar apps handle this correctly, but specifying the zone removes any doubt.

Step 4 — Account for Daylight Saving Time

This is the step most people miss. Daylight saving time does not happen on the same date everywhere. The United States and Europe shift their clocks in spring and autumn, but on different weekends. Australia shifts its clocks at the opposite time of year from the Northern Hemisphere.

The result is that the time difference between many city pairs changes up to four times per year. A London–New York meeting scheduled correctly in January may be off by an hour in March if you used a fixed offset.

The fix is simple: always calculate based on the exact date of the meeting, not a general offset. A reliable time zone tool does this automatically. If you have a recurring meeting, revisit the time after any daylight saving change in either location to confirm it still falls within reasonable hours for both parties.

Step 5 — Confirm in the Invite

The final step is to make the time unambiguous in the calendar invite itself. Good practice includes:

• List both local times in the invite title or description — e.g. "Weekly sync — 9am Sydney / 11pm London"

• Specify the time zone the invite is set in, so the recipient knows which clock to reference if there is any confusion

• Add a note for recurring meetings reminding both parties to check the time after daylight saving changes

This takes thirty seconds and eliminates almost all scheduling confusion.

The Most Common Mistake — and How to Avoid It

The single most common time zone scheduling mistake is using a memorised offset without checking whether it is still correct for the date in question. Someone remembers that Tokyo is 14 hours ahead of New York, schedules based on that, and misses the fact that the US has shifted its clocks since they last checked.

The solution is to stop relying on memory and use a tool every time. It takes less time than the back-and-forth that follows a scheduling mistake.

Tools to Help You Get It Right

• Time Converter — convert a specific time from one city to another

• Meeting Planner — find the best meeting time across two time zones

• Time Overlap Tool — see shared working hours between two cities at a glance

• World Clock — check the current time in any city worldwide

Scheduling across time zones gets easier once you build a consistent process. Use the right tools, confirm the time explicitly in both locations, and revisit recurring meetings whenever clocks change. That is all it takes to stop making mistakes.