How to Avoid Time Zone Scheduling Mistakes
Business & Remote Work
A missed meeting across time zones is rarely caused by carelessness — it is almost always one of a handful of predictable traps. Someone drops the time zone, forgets a clock change, or mixes up two abbreviations that look the same. The good news is that these mistakes repeat, which means you can learn to spot them in advance. This guide walks through the errors that catch people out most often and the simple habits that prevent each one.
- Never write a time without its zone — “15:00 UTC”, not just “3 PM”.
- Account for Daylight Saving Time: regions change clocks on different dates, so offsets drift for a week or two.
- Beware ambiguous abbreviations — CST alone could mean three different zones.
- Include the date: a meeting can fall on a different calendar day for distant participants.
- Let your calendar convert the time for you instead of doing the maths by hand.
Mistake 1: Naming a Time but Not the Zone
By far the most common error is treating a clock time as if it meant the same thing everywhere. “Let us meet at 3 PM” is perfectly clear in one office and completely ambiguous the moment two people sit in different zones. Each reader assumes their own local clock, and someone joins an hour — or several hours — late.
How to avoid it: always attach a zone or offset to every time you write. Anchor it to a neutral reference such as Coordinated Universal Time (UTC), the global standard from which every zone is measured, and state it explicitly — “15:00 UTC” or “3:00 PM New York time”. A 24-hour clock removes any leftover AM/PM confusion.
Mistake 2: Forgetting Daylight Saving Time
Time-zone offsets are not fixed all year. Many countries shift their clocks by an hour for Daylight Saving Time — and, crucially, they do not all do it on the same date. For a couple of weeks each spring and autumn, the gap between two cities can be an hour different from what you expect, which is exactly when standing meetings quietly slide out of place.
For example, the gap between London and New York is usually 5 hours, but in late March and late October it briefly becomes 4 hours because the two regions change their clocks on different weekends:
| Period | London | New York | Gap |
|---|---|---|---|
| Most of the year | UTC+00:00 / +01:00 | UTC−05:00 / −04:00 | 5 hours |
| Late March (UK not yet switched) | UTC+00:00 | UTC−04:00 | 4 hours |
| Late October (UK switched back first) | UTC+00:00 | UTC−04:00 | 4 hours |
How to avoid it: around mid-March, late March, late October and early November, double-check the offset before an important call. Some regions, such as most of Asia, do not observe Daylight Saving Time at all, which makes them easier to plan around.
Mistake 3: Confusing Time-Zone Abbreviations
Three-letter abbreviations feel precise but are surprisingly ambiguous. The same letters are reused around the world, so an abbreviation on its own can point to more than one zone:
| Abbreviation | Could mean | Offset |
|---|---|---|
| CST | Central Standard Time (USA) | UTC−06:00 |
| China Standard Time | UTC+08:00 | |
| IST | India Standard Time | UTC+05:30 |
| Irish Standard Time | UTC+01:00 | |
| BST | British Summer Time | UTC+01:00 |
| Bangladesh Standard Time | UTC+06:00 |
How to avoid it: pair any abbreviation with a city or a UTC offset — “CST (Chicago, UTC−6)” leaves no room for doubt. Better still, communicate the underlying UTC time and let each person read it in their own zone.
Mistake 4: Getting the Date Wrong
Large time differences do not just shift the hour — they can shift the day. A 9 PM call on Monday in Los Angeles is already Tuesday afternoon in Sydney. When the two ends of a conversation are far enough apart, or near the International Date Line, people agree on a time but turn up on the wrong date.
How to avoid it: always include the date alongside the time, and confirm it for both sides when the difference is large. “Tuesday 02:00 UTC” tells everyone exactly which calendar day to be there, even if that lands on Monday evening for some and Tuesday morning for others.
Mistake 5: Assuming Every Offset Is a Whole Hour
It is easy to assume time zones differ in neat, one-hour steps, but several do not. India is at UTC+5:30, parts of Australia sit at UTC+9:30, and Nepal is famously at UTC+5:45. Round an offset to the nearest hour and you can land a meeting 30 or 45 minutes off.
How to avoid it: check the exact offset rather than estimating it. If you ever work with colleagues in India, central Australia or Nepal, treat the half-hour and quarter-hour offsets as the rule for that conversation, not an oddity. Our guide on how time zones work around the world explains why these fractional offsets exist.
Mistake 6: Converting Times by Hand
Manual arithmetic across zones is where small slips creep in: adding when you should subtract, losing track of AM and PM, or forgetting a date rollover. Each conversion is one more chance to make an error, and the more people involved, the more likely one calculation is wrong.
How to avoid it: let software do the conversion. Tools such as Google Calendar, Outlook and Apple Calendar store an event as a single fixed instant and display it in each attendee’s own local time automatically — this is the safest way to share a time, because no one has to do the maths.
To sanity-check a conversion, open the city page for any location on this site — the live local time and current UTC offset are shown together, so you can confirm a slot at a glance.
Mistake 7: Pinning Recurring Meetings the Wrong Way
Recurring meetings are where time-zone mistakes compound. Fix a weekly call to a rigid UTC time and it will drift relative to everyone’s working day as soon as a region changes its clocks — what was a comfortable 4 PM can suddenly become 3 PM or 5 PM for half the team. Pin it to the wrong city and the same thing happens from the other direction.
How to avoid it: anchor a recurring event to one location’s local time — usually whichever is most central to the group — and let everyone else’s clock follow it through clock changes. Then verify the offset for the others during the weeks when regions switch, since they rarely switch on the same day.
Mistake 8: Ignoring Local Days Off and Working Hours
A slot can be technically valid and still be a poor choice. A date that is an ordinary workday in one country is a national holiday in another, and a “reasonable” hour in your zone might be the middle of someone else’s evening. Booking across a public holiday, or always landing the awkward hour on the same region, quietly erodes goodwill on a distributed team.
How to avoid it: keep a shared calendar of each region’s public holidays, respect local working hours, and rotate any unavoidable early or late slot so the same people are not always inconvenienced. See Working with Remote Teams Across Time Zones for more on keeping the burden fair.
A Quick Pre-Send Checklist
Before you send the next invite, run through these to catch the common traps:
- Have I stated the time with a zone or UTC offset, not just a bare clock time?
- Have I included the date, and confirmed it for participants far away?
- Does a Daylight Saving Time change fall near this date for anyone?
- Did I use a full city name rather than an ambiguous abbreviation?
- Is the offset exact, including any half-hour zones?
- Did I let the calendar convert and display the time, rather than doing it by hand?
- Does the slot avoid local holidays and unsocial hours — or rotate them fairly?
For the full step-by-step routine behind these checks, see How to Schedule Meetings Across Time Zones.
Frequently Asked Questions
What is the single most common time-zone scheduling mistake?
Writing a time without naming its zone. “3 PM” means something different to everyone who reads it from a different region. Always attach a zone or a UTC offset.
How do I stop Daylight Saving Time from breaking my meetings?
Anchor recurring events to one location’s local time rather than a fixed UTC time, and double-check offsets in the weeks when regions change their clocks, since they do not all switch on the same date. See What Is Daylight Saving Time? for the background.
Why are time-zone abbreviations risky?
The same letters are reused around the world — CST, IST and BST each map to more than one zone, so an abbreviation alone is ambiguous. Pair it with a city or a UTC offset to be safe.
Is it better to schedule in UTC or in local time?
Use UTC as the reference for working out a slot because it never changes, but send the invite through a calendar app so each attendee sees it in their own local time. That combination avoids both ambiguity and manual conversion errors.