Scheduling a meeting across time zones is one of those tasks that looks simple and consistently causes problems. Someone always shows up an hour late, or a day late, or not at all, and it's usually not their fault. The system is genuinely confusing, and most people don't realize how many ways it can go wrong until it already has.
What UTC Is and Why It Matters
UTC, Coordinated Universal Time, is the universal reference point for all time zones. Unlike a local time zone, UTC never changes. It doesn't observe daylight saving time. It doesn't shift seasonally. When precision matters, UTC is the anchor.
Every time zone in the world is defined as an offset from UTC. New York in winter is UTC-5 (Eastern Standard Time). London in summer is UTC+1 (British Summer Time). Tokyo is always UTC+9, because Japan doesn't observe daylight saving time at all. If you know the UTC offset for two locations, you always know the time difference between them, no guessing required.
This is why developers, pilots, broadcasters, and anyone coordinating across multiple countries defaults to UTC. For day-to-day scheduling, you don't need to think in UTC, but understanding it helps you catch errors before they become missed meetings.
How Daylight Saving Time Creates Real Confusion
Daylight saving time (DST) is the single biggest source of time zone errors in scheduling. The problem isn't that it exists, it's that different countries observe it on different dates, and some don't observe it at all.
The United States and Canada switch clocks on the second Sunday in March and the first Sunday in November. Most of Europe switches on the last Sunday in March and the last Sunday in October. That's a three-week window each spring and each fall where the US and Europe are one hour closer together than usual, or one hour further apart than you might expect, depending on the direction.
During those transition weeks, a standing meeting that worked perfectly for months can suddenly land at the wrong time. The recurring calendar invite still shows 3:00 PM EST. But your London colleague's calendar shows it at a different time than last week because the UK changed clocks and the US hasn't yet, or vice versa. Neither of you changed anything; the relationship between your time zones changed underneath you.
The only reliable fix is to either always express meeting times in UTC, or to use a time zone converter that accounts for DST when scheduling future meetings.
Best Overlap Windows for Global Teams
If you're managing a remote team spread across multiple continents, there are a limited number of hours where reasonable working hours overlap.
US (East Coast) and Western Europe share roughly a four-to-five hour window in the morning Eastern time, generally 9 AM to 1 PM EST maps to 2 PM to 6 PM GMT/CET. This is workable for most teams and is why many transatlantic meetings are scheduled in the late morning US time.
US (West Coast) and East Asia is harder. San Francisco and Tokyo are 17 hours apart in winter (16 in summer). There is no business-hours overlap. Meetings happen at the extreme edges of someone's workday, either very early morning in San Francisco or late evening in Tokyo. Acknowledging this explicitly and rotating who takes the difficult slot is a sign of good team management.
Europe and Asia generally have better overlap. London and Mumbai share roughly a four-hour window across standard business hours. London and Singapore overlap for about two hours in the early afternoon UK time.
Knowing these windows before you schedule a recurring meeting saves significant back-and-forth. A time zone converter lets you check instantly rather than doing the math manually.
Tips for Remote Teams
The most effective remote teams treat time zone management as infrastructure, not improvisation. A few practices that consistently reduce scheduling friction:
Always include the UTC offset when sharing a meeting time with new contacts. "3 PM EST" is ambiguous twice a year during DST transitions. "3 PM EST (UTC-5)" is not. Better still, share both the local time and UTC: "3 PM New York / 8 PM UTC."
Establish a team reference zone. Many distributed teams pick UTC as their canonical reference for any time-sensitive coordination, deployments, deadlines, async standup windows. When everyone converts to the same anchor, errors decrease.
Use calendar apps that handle time zone conversions automatically, but verify manually when precision matters. Calendar apps are reliable most of the time, but DST transitions and region-specific holidays have caused enough misfires that a quick manual check before a high-stakes meeting is worth thirty seconds.
Common Time Zone Mistakes
Confusing EST and EDT is one of the most frequent errors. EST (Eastern Standard Time) is UTC-5 and applies from November to March. EDT (Eastern Daylight Time) is UTC-4 and applies from March to November. "EST" is often used informally year-round, which means it's technically wrong for half the year and can be off by one hour.
Assuming all of a country uses the same time zone is another. The United States spans six time zones. China, despite its size, uses only one, but that's the exception, not the rule. Australia has three main time zones plus several regional variations, including half-hour offsets.
Forgetting that some places use half-hour or quarter-hour offsets. India is UTC+5:30. Nepal is UTC+5:45. Iran is UTC+3:30. If you're scheduling with contacts in these regions and you're rounding to the nearest hour, you'll be off.
A good time zone converter handles all of these edge cases for you. The goal isn't to memorize UTC offsets, it's to have a reliable tool you reach for before confirming a time, not after someone misses a call.