Time Zones and Scheduling Across Them (Without the Headaches)

The basics: everything is an offset from UTC

There is one master clock the whole planet agrees on: Coordinated Universal Time, or UTC. Every local time zone is simply UTC plus or minus some number of hours. US Eastern Standard Time is UTC−5; Pacific Standard Time is UTC−8; India runs at UTC+5:30. Yes, some offsets include half-hours (and a few, like Nepal, even quarter-hours). In total the inhabited world stretches from UTC−12 in the far Pacific to UTC+14 in places like the Line Islands — a spread of 26 hours, which is why two real places can be on different calendar dates at the same instant.

Once you think in offsets, conversion becomes arithmetic. To turn a local time into UTC, subtract your offset; to go the other way, add it. Everything below is just that idea applied carefully.

Common zones at a glance

Here are the four mainland US zones plus three international anchors most people end up scheduling with. Note that each zone usually has two offsets — one for standard time and one for daylight time:

India never changes its clocks, so it has a single offset all year. Australia, in the southern hemisphere, runs daylight time during our winter — its seasons are flipped. A live world clock is the quickest way to see all of these side by side right now.

Daylight saving: the number one cause of errors

If a cross-zone meeting ever drifts by exactly one hour, daylight saving time (DST) is almost certainly the culprit. The trap is that DST is not universal and not synchronized. Many countries — most of Asia, including India, and large parts of Africa — never observe it at all. Those that do switch on different dates: the US and Europe spring forward and fall back roughly a week or two apart, and the southern hemisphere does it in the opposite half of the year.

The practical consequence is that the offset between two cities is not constant. New York and London are usually 5 hours apart, but for a couple of weeks each spring and autumn — when one has changed clocks and the other hasn't — they are only 4 hours apart. A recurring 10am call can silently become a 9am call until both sides realign. If your tool doesn't account for DST automatically, this is exactly where it will bite you.

24-hour vs 12-hour time

The 12-hour clock with AM and PM is common in the US, but it is a frequent source of scheduling confusion. The AM/PM marker is easy to drop in a hurry, and "12:00 PM" versus "12:00 AM" trips up even careful people. The 24-hour clock — where afternoon times just keep counting, so 2pm is 14:00 and midnight is 00:00 — removes that ambiguity entirely, which is why most of the world and nearly all software use it internally. For anything written down and shared across borders, a 24-hour time paired with an explicit zone (or expressed in UTC) is the format least likely to be misread.

Practical tips for scheduling across zones

• Find the overlap. Sketch each person's working hours and look for the block where they all coincide. That window is your only viable space — pick inside it.
• Anchor to one zone or to UTC. Decide on a single reference ("16:00 UTC" or "10am New York time") and convert everyone else from that, rather than each person guessing.
• Let calendar apps do the conversion. Modern calendars store events as a fixed instant and display them in each attendee's local time. Trust that machinery instead of typing converted times by hand.
• State the zone, every time. "3pm" alone is meaningless internationally. "3pm ET" or "15:00 CET" is not.
• Beware "tomorrow" near the date line. When a chunk of the day separates you, your colleague's Tuesday morning may be your Monday evening. Use a concrete date, not relative words like today or tomorrow.

A worked example: New York, London, India

Suppose three colleagues each work 9am to 5pm in their own city, and we want a slot that falls inside everyone's day. Convert each person's working day to UTC (using standard-time offsets):

The overlap is the slice where all three UTC ranges intersect. London covers 09:00–17:00 UTC, India ends at 11:30 UTC, and New York doesn't begin until 14:00 UTC — so there is no time that fits everyone's standard 9–5. The realistic compromise is the New York–London overlap of 14:00–17:00 UTC (that's 9–10am in New York, 2–5pm in London, and 7:30–10:30pm in India), where the India colleague stays a little late. This is exactly the kind of squeeze a time zone converter surfaces in seconds, and it shows why three-continent calls almost always ask someone to bend their day.

The takeaway

Time zones are just offsets from a single shared clock, and most scheduling pain comes from two things: forgetting that daylight saving makes those offsets wobble, and leaving the zone unstated. Pin every time to a clear reference, lean on tools to convert, and the headaches mostly disappear. If long flights across those zones are next on your list, the jet lag planner picks up where this guide leaves off.

Frequently asked questions

What is UTC and why does it matter for scheduling?

UTC (Coordinated Universal Time) is the global reference point that every time zone is measured against as a fixed offset, like UTC−5 or UTC+5:30. Because UTC never shifts for daylight saving, anchoring a meeting to a UTC time removes ambiguity — everyone converts the same single instant into their own local clock.

Why does the time difference between two cities change during the year?

Most of the change comes from daylight saving time. Countries and even hemispheres start and end it on different dates, so for a few weeks each spring and autumn one city has shifted its clocks and the other has not. During those windows the usual offset between them is an hour off until both have changed over.

Should I use 24-hour time for international meetings?

Yes, for written invites it is safer. 12-hour times rely on AM/PM, which is easy to drop or misread, and 12:00 is famously confusing. A 24-hour time such as 14:00, ideally paired with the zone or UTC offset, is unambiguous and is the standard most of the world already uses.

How do I find a meeting time that works across several time zones?

List each person's working hours, convert them to one common reference such as UTC, and look for the block where they all overlap. Pick a slot inside that overlap, state the zone explicitly in the invite, and let calendar apps convert it for each attendee so nobody has to do the math by hand.

This guide is general educational information. Time zone rules and daylight saving dates can change, so confirm current offsets with a live tool before booking critical meetings.