Guide · daylight saving
Daylight saving and the four traps it sets for meetings
Twice a year, a large share of the world's recurring international meetings silently move by an hour. Nobody changes the invitation. The clocks change around it.
Daylight saving time (DST) is a political decision, not a physical law. Each country sets its own dates, some have abolished it, a few have abolished and then restored it, and a handful keep a permanent offset change. That is why “the meeting is at 9 a.m. my time” is a promise the calendar can break on its own.
Trap 1 — the offset changes between booking and meeting
Most calendar tools store a recurring event in the organiser's local time and repeat it weekly. When one region springs forward and another does not, the shared instant moves by an hour for everyone else. The classic version: a London–New York call booked at 14:00 London is 09:00 New York all winter, then becomes 10:00 New York for the two weeks between the US change in March and the UK change later that month.
Because the two countries change on different Sundays, there is a period every year when the gap is four hours instead of five, and again in autumn when it is five, then four. Teams that meet weekly will hit that window at least once and usually blame each other for the no-show.
What works: store the event in UTC. A calendar file with DTSTART and DTEND in UTC describes an absolute instant; each attendee's calendar renders it in their local zone, including whatever offset applies that week. CrossClock's .ics export is written this way for exactly this reason, and the description repeats every participant's local time so the human reading it can verify.
Trap 2 — the southern hemisphere moves in the other month
Europe and North America change in March and late October/November. Australia, New Zealand and most of South America change in April and September/October. For a few weeks each spring and autumn, the northern and southern zones are out of phase: Sydney is 11 hours ahead of London in January, but only 9 or 10 hours ahead during the transition weeks.
If your team spans both hemispheres, this is the period when your carefully chosen “works for everyone” slot falls apart — and it is easy to miss, because the shift happens in the middle of the night for most of the team. Schedule a review of recurring calls in late March, late September and late October, and check them against the actual dates rather than last quarter's notes.
Trap 3 — offsets that are not whole hours
Not every zone differs from UTC by an hour. India is UTC+5:30, Nepal UTC+5:45, parts of Australia UTC+8:45 and +9:30, the Chatham Islands UTC+12:45, and Lord Howe Island uses a 30-minute DST shift. Add those to a chain of whole-hour zones and the arithmetic produces half-hours that people round — usually in the wrong direction.
The failure is quiet: a 15:30 IST call announced as “10:00 London” is right, but the same call written as “10 a.m. UK, 3 p.m. India” invites someone to assume 3 p.m. means 15:00 local when the organiser meant 15:30. Write the minutes. A tool that computes from a time zone database will produce 15:30 and keep it consistent everywhere.
Trap 4 — governments change the rules with little notice
DST is not stable. In the last decade several countries abolished it, others restored it, and at least one shifted its whole national offset. Every change ripples through every meeting that touches that country. Two practical consequences:
- Any offset table hard-coded into a spreadsheet, a wiki page or an app becomes wrong on the day of the change. Prefer a source that reads the IANA time zone database at the moment you ask — your operating system, your browser, or a planner that does.
- Treat an unexpected one-hour difference as a data question before treating it as a person's mistake. “Did your country change its clocks this week?” resolves most of these in one message.
Making an invite immune
A robust invitation has four properties:
- An absolute instant. UTC start and end, so no offset arithmetic is needed to interpret it.
- Every local time, written out. Including the minutes, and including the date if it differs — a 22:00 call in Singapore on Tuesday is Wednesday 01:00 in Sydney.
- Zone names, not just cities. “Europe/Berlin” survives a rename; “Berlin time” invites a guess between CET and CEST.
- A note about the transition. If a clock change falls within a week of the meeting, say so in the description: “US clocks go back on 1 November; this event is stored in UTC and does not move.”
That last note is what CrossClock adds for you: when any participant's zone changes within about a week of the selected date, the planner shows the exact transition and the old and new offsets next to the proposed time.
A two-minute pre-call check
- Does anyone on the invite live in a country that changed clocks in the last ten days? Compare the offset in the invite with the offset now.
- Is the meeting recurring? If yes, check whether it is stored in a local time or in UTC.
- Does the invite show a date for every participant, not only a time?
- For anyone in India, Nepal, Adelaide, Darwin or the Chatham Islands, are the minutes written explicitly?
Run the same check on the invitation you are about to send with the CrossClock planner: it recomputes offsets from your browser's time zone data on every change of date, so the timeline you are looking at is the one that applies on that day, not last month's.
Next: the three-question test for whether the call should be a written handoff.
Read the async guide