How to Plan a Meeting Across Time Zones

Ever agreed to a “9 a.m. call,” then got a message at 2 a.m. asking where you were? Small time zone mix-ups like that happen to remote teams every single week, and they are almost always avoidable. Planning a meeting across time zones is not guesswork once you learn one simple method: convert every local time through a single shared reference point, UTC, before you compare clocks. Master that one habit and scheduling across three, four, or five cities takes minutes instead of a headache.

Why UTC Is the Common Reference Point

UTC stands for Coordinated Universal Time. It is a single, fixed time standard that never shifts for daylight saving and never changes by location. Think of it as the one clock every other clock in the world is measured against.

Every local time zone is really just an offset from UTC, written like UTC-5 or UTC+5:30. New York runs a set number of hours behind UTC, and Tokyo runs a set number of hours ahead. When you convert every attendee’s local time into UTC first, you get one trustworthy number that all the local times can be checked against.

This is why airlines, ships, weather stations, and the internet’s own background clocks all quietly run on UTC. It removes the confusion of daylight saving and local politics from the math, at least for that one middle step.

How to Convert a Local Time to UTC and Back

The whole method comes down to two simple moves. First, turn your own local meeting time into UTC. Second, turn that UTC time into each attendee’s local time.

To go from local time to UTC, you use this rule: UTC equals local time minus the local offset. If your offset is negative, like UTC-5, subtracting a negative number means you actually add 5 hours. If your offset is positive, like UTC+5:30, you subtract that amount instead.

To go the other way, from UTC to any city’s local time, you flip the rule: local time equals UTC plus that city’s offset. Once your meeting time sits in UTC, you can push it out to as many cities as you need with simple addition.

• Step 1: Find your own current UTC offset (check it for the meeting date, not just your city).
• Step 2: Subtract your offset from your local time to get UTC.
• Step 3: Add each attendee’s offset to that UTC time to get their local time.

Why Some Time Zone Offsets Are Not Whole Hours

Most people assume every offset is a clean whole number of hours, but several regions use 30 or even 45 minute offsets instead. This trips up a lot of otherwise careful meeting planners.

India runs on UTC+5:30. Parts of Australia, including Adelaide, use UTC+9:30. Newfoundland, in Canada, uses UTC-3:30. Nepal uses UTC+5:45, one of the few 45 minute offsets in the world. These choices usually come from a country picking a single offset for the whole territory, often splitting the difference between two neighboring whole hour zones, rather than a strict geographic rule.

The lesson is simple: never assume a country’s offset rounds to a full hour. Always look up the exact offset, including minutes, before you convert a meeting time for that city.

How Daylight Saving Time Shifts the Offset

Many countries move their clocks forward by an hour in spring and back again in fall. This is daylight saving time, and it changes a city’s effective UTC offset for part of the year.

New York runs at UTC-5 in winter, called Eastern Standard Time, but shifts to UTC-4 in summer, called Eastern Daylight Time. London runs at UTC+0 in winter and UTC+1 in summer. Not every country observes this change at all. Japan, India, and most of China keep the same offset all year round.

Northern and southern hemisphere countries also flip their daylight saving seasons. Australia and New Zealand move their clocks forward around September or October, while the United States and Europe do it in spring. Because of this, the gap between two cities can quietly grow or shrink by an hour depending on the time of year.

Always check a city’s current offset for your actual meeting date, not just its name or its offset from memory. A zone that was five hours behind you last month might only be four hours behind this month.

The Date Line Trap: Same Meeting, Different Calendar Day

When two cities are far enough apart, converting a meeting time can push the clock past midnight. The result is that the meeting lands on a different calendar date for one side, even though everyone is joining the exact same call.

Say a meeting is set for 9:00 PM on a Monday in Los Angeles. Los Angeles is UTC-7 in summer, so the meeting is 4:00 AM UTC on Tuesday. Auckland, New Zealand runs at UTC+12, so add 12 hours to that UTC time and you land on 4:00 PM Tuesday in Auckland.

For the Los Angeles attendee, this is still “Monday night.” For the Auckland attendee, it is already Tuesday afternoon, a full calendar day ahead. Nobody’s math is wrong. The date line trap is just a side effect of large time gaps.

The fix is simple: always write the full date and day of the week next to the time, for every zone, on the invite. Never rely on a single date label and assume it matches everywhere.

Worked Example: One Meeting, Three Cities

Here is the full method run start to finish. Say a team wants to meet at 9:00 AM Eastern Time in New York, in September, when New York is on Eastern Daylight Time at UTC-4.

Step 1: Convert to UTC. Local time minus the offset means 9:00 AM minus (-4 hours), which is the same as adding 4 hours. That gives 1:00 PM UTC on the same day.

Step 2: Convert to London. London is on British Summer Time in September, at UTC+1. Add 1 hour to 1:00 PM UTC, giving 2:00 PM in London, same day.

Step 3: Convert to Tokyo. Tokyo has no daylight saving and sits at UTC+9. Add 9 hours to 1:00 PM UTC, giving 10:00 PM in Tokyo, still the same day.

• New York: 9:00 AM EDT (UTC-4)
• London: 2:00 PM BST (UTC+1)
• Tokyo: 10:00 PM JST (UTC+9)

All three land on the same calendar date here, because the total spread is under 24 hours from the earliest to the latest local morning. That will not always be true, so always double check the date for each city, not just the time.

A Simple Checklist for Planning Your Next Global Meeting

You do not need to memorize every offset in the world. A short checklist keeps the process fast and accurate every time you schedule across zones.

1. Pick the meeting time in one anchor city first, then convert it to UTC.
2. Look up each attendee’s current offset for the actual meeting date, including any daylight saving change.
3. Add each offset to the UTC time to get every attendee’s local time.
4. Check whether the date shifts forward or back for anyone, using the date line trap logic above.
5. Write the full date, day of week, time, and zone abbreviation on the invite for every city.

There is no dedicated time zone meeting planner in our tool lineup yet, so for the date-shifting part of this process, a general Date Calculator is a handy fallback. It will not convert time zones for you, but it makes it easy to confirm which exact calendar date a meeting lands on once you have worked out the day shift by hand.

Frequently Asked Questions About Planning a Meeting Across Time Zones

Sources

This article is for general education only. Date and time calculations use standard calendar conventions, so always double-check dates for anything important like legal deadlines or payroll. Reviewed for accuracy by Prof. Dr. Khalil Mudassar, PhD. Last updated September 14, 2026.