Time Zone Calculation and DST Formula for Global Meetings

Contents
When a PM at a Seoul headquarters tries to set up a remote video call with a developer in the New York office and a designer in the London office, there's always that stressful moment. Get the math wrong, and someone has to join the Zoom call at 3 a.m. in their pajamas — or, on the flip side, gets forced to present late at night long after quitting time.
Here's a plain-language breakdown of the UTC offset math that connects countries, the Daylight Saving Time (DST) variable, and the mathematical algorithm for finding the optimal meeting slot by tracing the intersection of everyone's workable hours.
Summary ① Time difference offset formula: A city's local time follows the relationship
UTC ± offset, and the time difference between two cities comes from simply subtracting one offset from the other. ② The DST variable: Every year in March and again in October–November, the US, Europe, and others shift the clock forward and back by one hour, so you need a seasonal correction. To keep things simple, the tool below uses only each city's standard time (a fixed UTC offset), so you have to account separately for the 1-hour difference during DST. ③ Work and sleep classifications: Local time from09:00 ~ 18:00counts as working hours,06:00 ~ 09:00and18:00 ~ 22:00as flexible hours, and22:00 ~ 06:00as sleep hours. The goal is to find a slot where every participating city avoids sleep hours. ④ In the Global Meeting Timezone Coordinator, activate the participant city chips and drag the host city time slider. Each city's current local time and its work/flexible/sleep status appear as color badges, along with a suggested time button that keeps everyone out of sleep hours.
1. Multinational Time Offset and DST Correction Math
The mechanism for calculating the time difference between any two cities, A and B, comes down to simple addition and subtraction that uses standard UTC time as the shared constant.
Standard local time formula:
local time = UTC time + city offset + DST correction value(The offset here is the number of hours relative to Coordinated Universal Time — for example, Seoul +9, New York -5. The DST correction value is a seasonal flag: +1 when daylight saving is in effect, 0 when it isn't.)Final time difference formula between cities A and B:
time difference (A−B) = (A's offset + A's DST correction value) − (B's offset + B's DST correction value)
The Risk of DST Mismatches
The United States and the European Union move the clock forward one hour in spring (mid-March) and then set it back in fall (late October to early November).
- A case where this causes errors: Korea doesn't observe daylight saving time, so the actual time difference with New York is 13 hours in summer (while DST is in effect) and 14 hours in winter (when DST is off). Miss this seasonal variable, and your video call ends up an hour off. (The Global Meeting Timezone Coordinator below calculates each city with a fixed standard offset, so during DST you need to correct that 1-hour difference yourself.)
2. The Working Golden Window Overlap Formula
To pick the best meeting time without hurting anyone's quality of life, you need to check whether each participant's local time meets the following conditions.
- Working condition:
09:00 ≤ local time < 18:00(working hours, shown in green) - Flexible condition:
06:00 ≤ local time < 09:00or18:00 ≤ local time < 22:00(can negotiate before work or after work, shown in orange) - Never condition:
local time ≥ 22:00orlocal time < 06:00(late night and sleep hours, excluded and shown in red)
The Global Meeting Timezone Coordinator's suggested slots show only the host-city times from these three windows where every participating city avoids sleep hours (red).
How to Use the Global Meeting Timezone Coordinator
Instead of looking up each city's time difference and doing the mental math every time, a dedicated timezone tool gets you an answer in a few clicks.
Free · side-by-side local time and work status for each country · recommended meeting slots shown in real time

Here's how to use the tool.
- Choose participating cities: Of the six preset cities — Seoul/Tokyo, London, New York, Sydney, Frankfurt, and Los Angeles — tap the chips to activate the cities joining the meeting.
- Set the host city and time: Pick the city hosting the meeting from the dropdown, then use the 0–23 slider to set the meeting start time in that city.
- In the Multinational Local Meeting Time Analysis table at the bottom of the screen, check each active city's UTC offset, its calculated local time, and its work/flexible/sleep status badge.
- Daytime working hours (green), pre- and post-work flexible hours (orange), and late-night sleep hours (red) are separated by color badge, so you can hit the Suggested Shared Available Time Slot button to jump straight to a time that keeps every participating city out of sleep hours. This tool uses fixed standard offsets for each city, so during DST the actual time difference can be off by 1 hour — double-check before you lock anything in.
Wrap-Up
Scheduling multinational team meetings means weighing time offsets, the DST variable, and each participant's working and sleep hours together, so you can find a time that works for everyone. The Global Meeting Timezone Coordinator simplifies that process by comparing participants' local times and their work/flexible/sleep status on a single screen.
Free · side-by-side local time and work status for each country · recommended meeting slots shown in real time
FAQ
Why does the world divide time differences based on the Greenwich observatory in England (UTC+0) as the original constant?
Because of the historical agreement reached at the 1884 International Meridian Conference, which aimed to make ocean navigation maps safe and standardize railway timetables in the late 19th century.
- British shipping dominance: At the time, most of the world's trade navigation maps already used the London Greenwich observatory as the 0-degree Prime Meridian to plot latitude and longitude at sea.
- A single standard: Building on that, and driven by the US demand for synchronized railway time, an imaginary line running through the Greenwich observatory was established as the origin point for measuring global time — GMT (Greenwich Mean Time, later refined into UTC with atomic clock corrections). The global standard assigning plus offsets to the east and minus offsets to the west, one hour for every 15 degrees of longitude, was made permanent in law.
Are time differences between all countries always exact whole hours?
No. Some countries, including India, Nepal, and Iran, use half-hour offsets (30 or 45 minutes) to make up the difference in longitude from the standard meridian.
- Half timezone examples:
- India: Uses UTC+5:30, 5 hours 30 minutes ahead of Coordinated Universal Time, as its single national standard time (IST).
- Nepal: Uses the unusual UTC+5:45, a 15-minute increment offset.
- Business risk: When coordinating schedules with these countries, calculating only in whole hours can put your meeting 30 to 45 minutes off, so check separately. (The Global Meeting Timezone Coordinator currently supports only whole-hour offset cities like Seoul/Tokyo, London, New York, Sydney, Frankfurt, and Los Angeles, so cities with 30- or 45-minute offsets like India and Nepal need to be calculated separately.)
This article was adapted from our Korean original. Read the Korean original