Time Zone Math: Why Your Meeting Keeps Landing at 3 A.M.

The arithmetic is easy. The calendar isn't.

Ask a room of adults to convert a meeting time and most will manage it — add eight, subtract five, done. So why do smart teams keep booking each other at 3 a.m.? Because the number you memorised was only true for part of the year. Offsets move. A cheerful 2 p.m. in New York is 3 a.m. in Singapore during the winter months, and 2 a.m. once daylight saving starts — the meeting didn't change, but the gap underneath it did.

Singapore sits at UTC+8 all year and never observes daylight saving. New York swings between UTC−5 and UTC−4. London swings between UTC+0 and UTC+1. Two cities that both "do" daylight saving still don't switch on the same dates, so twice a year there's a stretch of a few weeks where one has moved and the other hasn't, and every recurring meeting between them quietly shifts by an hour. Nobody did the maths wrong. The maths expired.

Convert through UTC, never from your own clock

The reliable method has one extra step, and that step is the whole trick: don't convert directly from your city to theirs. Convert both cities to UTC, the world's shared reference clock, and compare there. UTC never observes daylight saving, so it doesn't move under you. Your local offset to UTC is a single number your calendar app already knows; theirs is too. Two small, checkable steps beat one big leap you did in your head.

This is exactly how overlap works. Take each person's working hours in local time, convert that window to UTC, and lay the windows on top of each other. Where all of them stack is the only time a live meeting fits inside everyone's workday.

Read the table the way the planner below does. London (09:00–17:00 UTC) and New York (14:00–22:00 UTC) share 14:00–17:00 — a comfortable three hours. Add Singapore (01:00–09:00 UTC) and the three-way overlap vanishes: Singapore's window ends just as London's begins. That team doesn't have a scheduling problem to solve harder. It has no shared workday, and it needs pairwise calls plus async habits instead.

The three traps that do the damage

Daylight saving, in both directions. Northern-hemisphere zones spring forward in March and fall back around October and November — but not on the same dates, which creates those few mismatched weeks. Southern-hemisphere zones do the opposite: Sydney is at +11 during its summer, which is the northern winter, and +10 the rest of the year. So a Sydney gap can grow from one end while a London gap shrinks from the other. Any recurring cross-border meeting deserves a fresh check after every clock change, on either side.

Zones that aren't whole hours. Not every offset ends in :00. India runs at UTC+5:30, Nepal at UTC+5:45, and parts of Australia at +9:30. Do the sum assuming round hours and you'll land half an hour early to an empty room — or, worse, half an hour into a meeting that started without you. The :30 and :45 aren't trivia; they're where confident mental arithmetic goes to die.

The date line. Convert far enough east or west and the answer isn't just a different hour, it's a different day. Singapore's 9 a.m. Monday is still Sunday afternoon in San Francisco. Invitations that show only a time, with no date and no city, are how someone ends up waiting alone on the wrong morning. Always name the day in each place, not just the hour.

Rescuing a meeting that keeps landing badly

1. Write the time three ways before you send anything: in UTC, and in each participant's city, with the date in each place. If one of those reads 03:00, you'll see it now, not at 03:00.
2. Aim for the overlap, and protect at least an hour of it. Two to three shared hours is healthy; one hour carries a standup and not much more, so keep the deep discussions for days when someone flexes.
3. If there's no overlap, don't hand the pain to the same person every week. Rotate who takes the early or late slot, or split the meeting into two shorter ones, each kind to a different half of the team.
4. Move everything outside the overlap to async by default: written updates, recorded walkthroughs, documents with comments. Save the precious shared hour for the arguments only a live call can settle.
5. Put a note on the calendar to re-check the series after each daylight-saving change — yours and theirs. Ten seconds in March saves a 3 a.m. surprise in April.

None of this needs brilliance. It needs one shared ruler (UTC), the honesty to admit when no overlap exists, and a tool that reads a live timezone database instead of last year's offsets. Do the conversion that way and the 3 a.m. meetings quietly stop happening.