Common Time Zone Scheduling Mistakes (and How to Avoid Them)
You told your vendor in Riyadh, "let's talk Friday." They didn't show. You weren't wrong about the date. You were wrong about the week: in Saudi Arabia, Friday is the first day of the weekend, not a normal workday. Nobody told you because nobody thought to.
That's the pattern behind almost every time zone scheduling mistake. It's rarely the arithmetic. It's an assumption nobody checked, because it never occurred to anyone that things might work differently on the other end. Here are the ones that cause the most missed calls, and the one-line fix for each.
An Abbreviation Instead of a Place
"Let's do 3 PM CST" sounds specific. It isn't. CST can mean three different time zones: US Central Time (UTC-6), China Standard Time (UTC+8) or Cuba Standard Time (UTC-5). Between Chicago in winter and Beijing that is a 14-hour difference. IST has the same problem between India, Israel and Ireland.
The fix: name the city or the offset. "3 PM CST (Chicago)" or "3 PM UTC-6" removes the doubt in a few extra characters. The time zone converter shows both for any city you add.
A Half Hour Treated as a Rounding Error
India runs on UTC+5:30 and Nepal on UTC+5:45, both all year. Darwin is UTC+9:30 all year, and Adelaide is UTC+9:30 in winter and UTC+10:30 in summer. The Chatham Islands of New Zealand are on UTC+12:45 in winter. These are in the time zone database, not curiosities.
Quick mental math that adds "five hours for India" is consistently 30 minutes off, which is exactly wrong enough to make someone late without knowing why. If it's a zone you don't work with every week, don't estimate. Check the exact offset.
Trusting What Your Calendar Shows After You Travel
A calendar stores each event as a moment in time and then shows it in whatever zone your calendar or device is set to. When you land in London, your 9 AM Eastern call correctly reads 2 PM. The trouble comes next. If the device now thinks it's in London, a new event typed as "9 AM" is 9 AM London time unless you choose the zone, and with some apps a recurring series is displayed in the zone you happen to be in rather than the one it was created in.
How an app behaves depends on its settings. The University of Michigan's IT help, for example, documents that Google Calendar shifts the times it displays to your current location unless you turn off the "Use device time zone" option, and explains how.
The fix: before a trip, look at how your calendar handles time zones. When you create an event while traveling, set its zone explicitly. After you land, open the next important call and check what time it shows for the other side.
Assuming the Weekend Is Saturday and Sunday
Saudi Arabia and Qatar run a Friday and Saturday weekend, and Friday is the first rest day in most of the Gulf states. If you assume a Gulf team's week looks like yours, you'll book a Friday call that won't happen, or treat their Sunday as a day off when it's a working day.
The assumption can also go out of date. The UAE moved to a Saturday and Sunday weekend on January 1, 2022, with a half working day on Friday for government offices, while private companies can still choose their own schedule. Someone who learned "the Gulf means Friday and Saturday" years ago will now get Dubai wrong in the opposite direction.
The fix: ask once, at the start of a working relationship, and don't assume the answer stays fixed. It takes five seconds.
"Tomorrow" Across a Big Offset
"Let's talk tomorrow" is precise for two people in the same zone. It gets ambiguous once the offset is large. At 4:00 PM on a Monday in Los Angeles it is already Tuesday morning in Sydney, and for the whole Los Angeles working day the two cities are on different dates.
The fix: use a date, not a day word, when the offset is 10 hours or more. "Wednesday, October 14, your time" can't be misread. The time difference pages show the gap for popular pairs.
The Weeks the Gap Changes
If you have a recurring call with Europe, there are weeks each year when the US and the UK or EU are on different clocks, and the usual gap is an hour off. For New York and London that is the two to three weeks from the second Sunday in March to the last Sunday in March, and the week from the last Sunday in October to the first Sunday in November (in 2026, March 8 to 28 and October 25 to 31). The call feels an hour off, and it is. The exact dates are on the 2026 daylight saving page and the DST rules by country guide.
The Habit Behind All of These
Every mistake above comes from doing the conversion in your head, once, and trusting it. A converter handles the half-hour offsets, the daylight saving rules in force on that date, and the date line for you. Reading its result back to the other person ("that's 9 AM Thursday your time, right?") catches most of what's left.
What to Do Next
Pick the next meeting you're about to send across time zones and check it three ways: the zone is a named city or an offset, the date is written out, and the result has been through the time zone converter with the date set. If you're coordinating more than two places, the meeting scheduler shows what a proposed time means in up to three locations and flags anyone outside working hours.
Related Articles
- DST Rules by Country: The Complete Guide: which countries observe daylight saving time, which have stopped, and the exceptions worth knowing.
- How to Schedule a Meeting Across Time Zones: step by step finding overlap for US, India, UK and EU teams.
- Best Meeting Time for US and India Teams: the overlap windows for East Coast, Central and West Coast teams calling India.
Related glossary terms: Timezone Abbreviation Ambiguity · What Is DST? · What Is a Time Zone?