Before you go: the ten-minute setup

  1. Add your destination cities to your world clock before the trip — plus home, plus any city you'll be calling into (your team's HQ, your biggest client). Three to five cities cover almost any trip.
  2. Audit next week's calendar in destination time. That recurring 16:00 standup is 07:00 in your destination — decide now whether you're attending, moving it, or skipping it, not at 06:45 in a hotel.
  3. Check what your calendar app will do. Most calendars shift events to local time when you land. That's correct for calls ("15:00 Berlin" is still 15:00 Berlin) and wrong-looking for local plans you typed as times. Enter local plans (dinners, pickups, tours) with the event's timezone set to the destination.

The booking-confirmation trap

Flights, trains, and hotels always print local times: departure in the origin's timezone, arrival in the destination's. A 22:10 arrival after a 14:30 departure is not a 7.7-hour flight if you crossed zones. The practical rule: never compute layovers or arrival-day plans from the printed times alone — check both cities' current offset (this is a two-second glance if both are in your menu bar).

During the trip: two clocks, one rule

You need exactly two mental anchors while traveling: local time (your phone and Mac handle this automatically) and home time (everyone you left behind). The rule: before calling or messaging anyone, glance at their clock, not yours. A menu bar world clock like GlobalTimeZones makes this passive — home, your team's cities, and your next destination sit one click away, each with an availability dot that answers "is it rude to call right now?" before you find out the hard way.

Schedule around jet lag, not just offsets

After a big eastward hop you are biologically hours behind the local clock for several days (rule of thumb: about a day of adjustment per timezone crossed, eastward being harder). So don't book your most important call for 9:00 the morning after landing from an 8-zone flight — your calendar says 9:00, your body says 1:00. Put the critical meetings on day two or three, afternoon local time, where your home rhythm and the local clock overlap best. The time slider is handy here: drag to a proposed slot and see it in home time — if it's the middle of your biological night, negotiate.

Working while traveling

If you're working from the road, the offset to your team changes with every leg of the trip. Re-run the same routine each move: where does the team's core window land in my new local day, and which recurring meetings survive? For longer stints abroad, the full playbook is in working remotely from a different time zone — and mind DST changeover dates, which can move your offset mid-trip even when you don't move.

The checklist

  1. Destination + home + team cities added before departure.
  2. Next week's calendar reviewed in destination time.
  3. Local plans saved with the destination's timezone.
  4. Layovers computed from offsets, not printed times.
  5. Critical meetings scheduled for day 2–3, not landing day.