How to stop double-booking yourself across time zones

A double-booking across time zones rarely feels like a mistake at the time. You picked a slot that looked free, the call invite went out, and only later did two events land on the same hour. The cause is almost never carelessness. It is the small, predictable ways that time-zone maths goes wrong.

Why do double-bookings happen across zones?

The problem is widespread and growing: Microsoft's Work Trend Index found that nearly a third of meetings now span multiple time zones, up 35% since 2021, so cross-zone clashes are increasingly common. There are three repeat offenders behind cross-zone clashes. Each one is easy to trigger and easy to miss until the clash appears.

• Mental conversion errors. You convert a time in your head, land one hour off, and the slot you thought was free is already taken. Half-hour offsets like India's UTC+5:30 make this worse, because the gap is not a round number of hours.
• Daylight saving drift. Countries change clocks on different dates, so the gap between two cities is not fixed. A recurring call set when London and New York were five hours apart quietly moves an hour after one of them changes over.
• Events made in the wrong zone. Create an event while travelling, with your laptop or phone still set to another zone, and the time is stored against the wrong offset. It looks right on your screen and lands an hour or more out for everyone else.

How does daylight saving cause clashes?

The trap is assuming the gap between two cities is constant. It is not. Most of the year London is five hours ahead of New York, but the United States and the United Kingdom change clocks on different weekends, so for roughly two weeks each spring and autumn the gap is four or six hours instead.

A recurring meeting locked in during the five-hour window does not move with the change. After a clock change it sits an hour off, and that hour is often where your next call already lives. This is the same mechanism that quietly puts events at the wrong time in your calendar; we cover it in detail in why your calendar shows the wrong time zone.

How do I stop double-booking myself?

Four habits remove nearly every cross-zone clash. None of them require more effort than the guessing they replace.

1. Keep one source of truth. Pick a single place that shows everyone's current local time, and trust it instead of doing arithmetic in two different apps.
2. See local times before booking. Look at what the clock actually reads for each person, and check the slot sits inside their working hours before you send anything.
3. Confirm on the real date. Daylight saving means the gap on the day of the meeting can differ from today. Always check the offset for the actual date, not for now.
4. Block buffers. Leave a short gap either side of cross-zone calls. A ten-minute buffer absorbs the odd off-by-one and keeps a near-miss from becoming a clash.

Let the tool hold the truth

The reliable version of all four habits is to stop converting entirely and read the answer instead. Atlas pins your teammates and cities on a world map, shows each person's current local time, and shades their working hours, so you can see at a glance whether a slot is reasonable. It finds the best overlapping time for the group, then adds the meeting to your calendar in everyone's correct local time, with daylight saving handled.

Because Atlas knows every zone and offset, the off-by-one error that causes most double-bookings simply cannot happen: you are reading real local times, not guessing them. A Quick Check shortcut lets you confirm a time or add a meeting from anywhere without leaving what you are doing, so checking before you book costs a second rather than a context switch. For more on the underlying calendar pitfalls, browse the Atlas blog.