Scheduling Across Time Zones Without the Off-By-One-Day Mistake

A meeting invite that says “Tuesday 3pm” is meaningless without a zone attached. When teams span California, London, and Singapore, that omission is how one person shows up at 3am and another a full day early. The underlying math is simple arithmetic, but a few real traps cause most scheduling failures. Here is how to run the conversion and where it breaks.

The Core Arithmetic: UTC as the Anchor

Every time zone is defined as an offset from Coordinated Universal Time (UTC). Converting between two zones is two steps:

1. Convert the local time to UTC by adding or subtracting the source offset.
2. Convert UTC to the target local time using the target offset.

Example: it is 9:00 AM in Los Angeles (UTC−8 in winter). UTC = 17:00. London is UTC+0 in winter, so it is 17:00 there. Singapore is UTC+8, so it is 01:00 the next day.

The Trap That Causes Most Errors

The classic mistake is adding the offset difference wrongly across midnight. Singapore is 16 hours ahead of Los Angeles. Adding 16 hours to 9:00 AM gives 25:00, which is 01:00 the next day. People either forget the day rollover or apply it in the wrong direction.

Any pair differing by more than 12 hours will almost always cross a date line. That is the tell to watch for.

Daylight Saving Ruins the Fixed Offset

Offsets are not constants. Daylight saving time (DST) shifts them by an hour for part of the year, and — critically — DST start and end dates differ between countries:

• The US switches in March and November.
• The EU switches in late March and late October.
• Australia switches in October and April, opposite the Northern Hemisphere.
• China, Japan, India, and Singapore do not observe DST at all.

The result: for roughly 2-4 weeks each spring and autumn, the offset between New York and London is 4 hours instead of the usual 5. A recurring meeting booked at a fixed UTC time is safe. One booked at “9am New York” drifts by an hour for those weeks.

Half-Hour and Quarter-Hour Zones

Not every zone sits on a whole hour. India is UTC+5:30, Nepal is UTC+5:45, and parts of Australia use UTC+9:30. If you convert assuming whole hours, these are off by 30 or 45 minutes — enough to miss the start of a call.

How to Pick a Meeting Time That Works

1. List each participant’s UTC offset for the exact date, not the generic one.
2. Find the overlap window where all local times fall between 8:00 and 18:00.
3. Check whether the date changes for anyone — if it does, note the day shift explicitly in the invite.
4. Send the invite in UTC with each local time listed, and let the calendar app handle DST automatically.

For a US-EU-Asia team the honest answer is often that no window suits everyone, and the fair solution is rotating the inconvenient slot rather than pinning it on the same people every week.

FAQ

Why is the offset different in summer? DST shifts one or both zones by an hour at different dates.

What does “UTC” stand for? Coordinated Universal Time — a compromise abbreviation between the English and French word orders.

Can I just use the city instead of the offset? No. City names hide DST rules; an explicit offset plus a DST check is unambiguous.

How do I avoid the off-by-one-day error? Convert to UTC first, then to the target zone, and check whether the resulting hour is less than zero or 24 or more — that tells you the date shifted.

Time arithmetic involving midnight rollovers, DST, and date changes is the same problem as calculating a duration between two timestamps. The free tools at TodayCalculator’s time duration calculator handle hours, minutes, and day crossings so you are not hand-tallying past midnight. If you also need the calendar days between two dates, use the date difference calculator.