Why your calendar shows the wrong time after you travel
You land in New York and your 9am dentist appointment back home now says 4am. Nothing is broken — but one setting decides whether that helps or confuses.
What is actually happening
A calendar entry stores an instant, not a clock reading. When your phone's zone changes, every entry is re-rendered in the new zone. The appointment did not move; your reference frame did.
That is correct behaviour and usually what you want — a flight at 18:00 local departure should show as 18:00 wherever you are standing. It is disorienting for everything else.
The two settings that matter
| Setting | Effect | Best for |
|---|---|---|
| Automatic time zone (on) | Everything re-renders on landing | Most travellers |
| Automatic time zone (off) | Calendar stays on home time | Short trips where you keep home hours |
| "Home time zone" in calendar app | Shows a second column in home time | Anyone booking across zones while away |
Google Calendar, Outlook and Apple Calendar all support a secondary time zone. Turning it on gives you both readings side by side, which removes almost all of the confusion.
All-day events are the exception
Birthdays, holidays and deadlines stored as all-day events have no time attached, so they do not shift. That is why a birthday reminder stays on the right date while a 9am meeting appears to move — the two are stored differently, deliberately.
Booking while you are away
This is where mistakes happen. Creating an appointment for "next Tuesday 10am" while sitting in a different zone books it in the zone your phone currently thinks it is in. Before creating anything, check which zone the entry field is using — most apps show it, and most people never look.
The practical routine
- Leave automatic time zone on.
- Enable a secondary home time zone in your calendar app.
- When creating events abroad, set the zone explicitly on the entry.
- Check your alarms separately — they follow device time, not calendar logic.
Alarms behave differently from calendar entries
This trips up more travellers than the calendar itself. A 07:00 alarm is stored as a wall-clock time on the device: change zone and it still fires at 07:00 local. A 07:00 calendar event is stored as an instant: change zone and it re-renders. Same number on screen, opposite behaviour.
| Item | Stored as | After you land |
|---|---|---|
| Alarm | Wall-clock time | Fires at the same local number |
| Timed calendar event | Instant + zone | Shows the equivalent local time |
| All-day event | A date only | Unchanged |
| Reminder with a due time | Varies by app | Check before relying on it |
Flights are the special case
Airlines publish departure in origin local time and arrival in destination local time, and good itinerary apps store both as instants with the correct zones. If you hand-enter a flight, enter departure in the origin zone and arrival in the destination zone explicitly — entering both in your home zone produces a flight that appears to take a strange length of time.
Booking on behalf of someone else
If you are arranging a call for a colleague in another region while you are travelling in a third, you are now three zones deep. Set the event zone explicitly to the colleague's zone, and confirm the rendered time back to them in their own city name. It takes one line and removes the entire class of error.
Before you fly
- Turn on a secondary time zone in your calendar view, set to home.
- Check anything scheduled for the travel day itself, especially connections.
- Confirm your work calendar and personal calendar agree on the zone setting.
- Leave automatic time zone on unless you are deliberately staying on home hours.
Filed under Travel · Tags: calendar, travel, phone settings, jet lag. Figures verified against the official definitions — see our editorial policy.
