How daylight saving changes international meetings

The offset is a moving relationship

Daylight saving is set locally, not globally. Two places can both observe it yet move their clocks on different weekends. One place can observe it while the other never does. Cities in opposite hemispheres often move in opposite seasons. In each case, the difference between their clocks can change even though neither team changed the calendar invite.

The practical consequence is simple: a meeting anchored at 09:00 in one city is not always anchored at the same local hour elsewhere. Treat the local time in the meeting organiser's zone as the source of truth, then check every attendee's local time around transitions.

A five-minute pre-flight check

1. Choose the city whose local time defines the recurring meeting.
2. Add every attendee's city to the meeting planner.
3. Check the proposed hour now, then inspect the next six to twelve months.
4. Note every date on which a participant's local meeting time changes.
5. Put those dates in the calendar description or send a short reminder beforehand.

Choose a policy, not a one-off compromise

For a two-person call, the least painful answer is often obvious. For a recurring team meeting, agree on a policy instead: keep the host city's hour fixed, rotate the burden every quarter, or pause when the overlap becomes unreasonable. A stated policy avoids treating an unpleasant time as an accident that only one person has to absorb.

Use the date, not a remembered rule

“They change at the end of March” is not enough for planning. Rules can differ by country and governments can alter them. Use a converter that accepts the actual meeting date, and re-check important series after any calendar-system warning. Hours Apart's time-difference pagesshow the dates on which each listed pair changes.