Travel Routine
Time Zones Break The Calendar Before They Break You
Recurring appointments, alarms and shared calendars behave unpredictably across a time-zone change, because different systems anchor events to different reference points.

A traveler crossing time zones usually plans for sleep and forgets the calendar. Scheduling software handles the change in inconsistent ways, and the failures are silent.
Events are stored against a zone, not a clock
A calendar entry is stored with a time and a reference zone, and the display converts that to whatever zone the device believes it is in.
When both the event and the device are correct, this works invisibly. Problems begin when an event was created without a zone, or with the wrong one.
An all-day event has no time at all, which is why it can appear to shift by a day when a device crosses a boundary near midnight.
Recurring events are the fragile case
A weekly meeting is stored as a rule rather than a list, and the rule is evaluated in the zone of whoever created it, not the person viewing it.
When either side changes zone, or when daylight saving shifts on different dates in different countries, the meeting appears to move for one party and not the other.
The gap between the northern and southern hemispheres, and between countries that change on different weekends, produces several weeks each year where this is routine.
Alarms and calendars disagree
Phone alarms are typically set as wall-clock times and fire at that local time after the device updates its zone, which is usually what a traveler wants.
Calendar reminders behave in the opposite way, tracking the event's absolute time, so an alarm and a calendar entry set for the same purpose can diverge after landing.
This is the mechanism behind the common experience of an alarm going off correctly while a reminder for the same thing arrives hours earlier or later.
Automatic zone updates are not instant
A device changes zone from the network or from location, and either can lag, particularly in airplane mode or with a newly installed local data plan.
During the lag, every displayed time is wrong by the offset, and anything scheduled in that window is scheduled against the old zone.
Checking the clock deliberately after landing, before setting anything, is the small step that catches this before it produces a missed appointment.
Booking times belong to the place
Flight, train and hotel times are always expressed in the local time of the location concerned, which is unambiguous but easy to misread when connecting through zones.
An overnight flight crossing a boundary can arrive on the same calendar day it departed, or two days later, and neither is an error.
Reading itineraries as a sequence of local times, rather than converting them into a home-zone timeline, avoids nearly all of the confusion.
Questions readers ask
What do people lose most often when travelling?
Phones, chargers, passports and glasses, overwhelmingly at security, in seat pockets and in accommodation. All are transition points rather than random events.
Is a checklist worth it for regular travellers?
More so, not less. Frequent travellers pack on autopilot, which is exactly the mode in which a single item is quietly omitted.
Also by Nadia Halloran
- Jet lag has a direction, and that changes what worksTravel Routine
- Rail passes are usually the wrong answer, and sometimes the right oneTrains & Ground
- Hostels, guesthouses and the middle nobody booksWhere You Sleep
- Doing laundry on the road is a planning decisionTravel Routine





