How to set an alarm for a different timezone (and not miss your flight)

I landed in Taipei a bit after midnight, set an alarm for 7am so I could make a call back to Sydney, and woke up to sunlight already high in the window. The alarm had gone off. Just not when I thought it would. Somewhere between the wheels touching down and my phone catching the local network, the time had shifted under me and the alarm came along for the ride.

If you cross timezones often you have had a version of this. You go to set an alarm for a different timezone, the phone quietly does its own thing, and the alarm rings at a time you did not expect. Sometimes earlier, sometimes later, and almost always on the morning you needed it to be right. So here is what your phone is actually doing when you travel, how to work around it, and the approach I have landed on after a couple of years living out of a backpack across Asia.

What your phone actually does when you cross a timezone

Most modern phones set their clock automatically from the mobile network or GPS. The moment you land and connect, the phone notices it is somewhere new and updates the time. That part is genuinely useful. Nobody misses winding a watch forward five hours by hand.

The catch is what happens to an alarm you set before the clock moved. On a lot of Android phones an alarm set for 7am stays at 7am and simply rings at 7am local time in the new place. On iPhones it depends on a setting, and people get caught both ways: some find the alarm has quietly shifted, others find it stubbornly stuck on home time. The behaviour is not really wrong. The phone has guessed what you want, and it cannot read your mind.

Quick test before a trip: set an alarm, change your phone's timezone by hand in settings, and watch whether the alarm time moves. That tells you which way your particular phone leans, without finding out at 5am.

The two things you actually want from a travel alarm

When you pull the frustration apart, it is almost always one of two needs, and they pull in opposite directions.

• Ring at local time, wherever I am. You land in Tokyo and you want a 7am Tokyo alarm so you are up for the day. Most phones handle this one.
• Ring at a specific city's time, wherever I am. You are in Bangkok but the call is 9am Sydney, and you want the alarm on Sydney time. Phones are bad at this one.

The second is where the head-maths starts. Bangkok is three hours behind Sydney, so the call is at 6am where you are, except daylight saving in Sydney just shifted things by an hour and now you are not sure, so you set two alarms and a calendar reminder to be safe. I have done exactly that more times than I would like to admit.

How to set an alarm for a different timezone right now

There are a few ways to set an alarm for a different timezone with tools already on your phone, as long as you know where they stop. For the first need the built-in clock is fine. Land, let the phone update, set a 7am alarm, done.

For the second need there are two reliable manual routes. Open the world clock, add the city you care about, read the current offset and convert once by hand, then set an ordinary alarm at the converted time. Or lean on your calendar: Google Calendar lets you pin an event to a specific timezone, so a 9am Sydney meeting will notify you at the right moment wherever you happen to be. It is not an alarm in the loud, drag-yourself-out-of-bed sense, but for a call it usually does the job.

The weakness in both is the same. They depend on you doing the conversion correctly, once, while tired, and on remembering to redo it if daylight saving flips while you are away. That is a lot of small chances to get a single number wrong.

Anchoring an alarm to a city instead of a number

This is the gap I kept falling into, so I built a small app for it called Meridian Clock. The idea is simple. You anchor an alarm to a city rather than to a number on the clock. Pin an alarm to Sydney and it stays on Sydney time. Fly to Bangkok and it still rings at the right moment in Sydney, with no converting on your part. Fly home and it behaves like a normal alarm again. The aim was to make the whole thing frictionless: no arithmetic, no backup alarm set out of nerves.

Anchor an alarm to a city and it stays on that city's time, so you stop doing timezone maths in your head at midnight.

A few things sit around that, because an alarm screen at 6am is not the moment to go hunting for information. When a city alarm rings it shows the weather there and your next meeting, so you wake up already oriented. There is a gradual sunrise option that brightens the screen before the sound, which is far kinder than being jolted awake in a strange room. And the alarms survive a restart, which sounds dull until your phone reboots overnight and a normal alarm quietly fails to fire. No account, nothing to sign up for, it just runs on your phone.

The honest tradeoffs

Automatic is not always worse. The reason this is fiddly at all is that phones try to be clever, and most of the time their guess is right. If you only ever want to wake at local time you do not need any of this. The built-in clock already does that, and reaching for an app would just be friction for its own sake.

The anchored alarm earns its place when you are regularly holding two timezones at once. Remote workers with a team back home, people doing long stretches of slow travel, anyone whose calls do not move just because they did. If that is not you, the manual world-clock trick is honestly fine and free. I built Meridian because it was me most weeks, and I was tired of the 6am arithmetic.

I still double-check the important ones. Old habit, and a missed call with someone five timezones away is not a small thing. But the day-to-day maths is gone, which was most of what I wanted. If you travel across timezones a lot, try the world-clock trick first and see how often it bites you. If the answer is often, you will know what to do about it.

Benjamin

Founder & sole developer, Novaire Digital