Daylight saving is not a vibe. It is four clusters of weekends in 2026 that turn repeating calendar invites into fiction. Teams that book New York against London on folklore (“always five hours”) will have two bad weeks in March and another in late October. Teams that book Sydney against California will have *four* bad weekends, because the southern hemisphere moves in the opposite season.
Open the pair page when a clock change is within fourteen days. The New York–London heatmap will disagree with last month’s memory. That disagreement is the story.
The 2026 dates worth tattooing
United States (most zones): DST begins 8 March 2026 (second Sunday) and ends 1 November 2026 (first Sunday).
European Union and the UK: DST begins 29 March 2026 (last Sunday) and ends 25 October 2026 (last Sunday).
Australia (NSW, VIC, SA, TAS, ACT): DST *ends* 5 April 2026 and *begins* 4 October 2026.
New Zealand: similar southern pattern; do not copy Sydney’s dates blindly — check `Pacific/Auckland`.
Shoulder periods:
- 8–29 March: US already summer, Europe still winter. - 25 October–1 November: Europe already winter, US still summer. - March–April and October–November for any US–Australia pair: both sides may move on different weekends, in different directions.
Berlin follows the EU dates. London follows the UK dates, which currently still match the EU last-Sunday rule. Do not assume this political fact remains true forever; in 2026 it still holds.
What repeating invites actually do
Calendar software stores a timezone, not a feeling. If the event is `America/New_York` 09:00 weekly, New Yorkers keep 09:00 local through the spring-forward (they lose an hour of sleep; the meeting stays at 09:00 local). Londoners watching that same event in `Europe/London` will see the *civil* time jump when the offset between the zones jumps.
People then “fix” it by dragging the hold, which breaks the next DST weekend. The adult move is: the week of a clock change, delete the series from the transition onward and recreate it with both IANA zones named in the title. Fifteen minutes of calendar hygiene beats a quarter of missed standups.
No-DST cities are not simpler; they are one-sided
Tokyo does not move. When the US springs forward, the US–Japan offset changes by an hour and Japan did nothing. Arizona (`America/Phoenix`) matches Mountain Time in winter and Pacific in summer. Queensland matches Sydney in winter and not in summer. If your “APAC call” mixes Tokyo, Sydney, and Brisbane, you have a small orchestra of offsets. Conduct it with IANA names, not country names.
Meeting-design for DST season
Keep overlap meetings short in March, April, October, and November. Write both local times in the title every week, not just when you created the series. Add a note in the agenda: “If this is the Monday after a clock change, check the pair page before you join.” Do not mock the person who shows up an hour off; the software and the folklore did that together.
If you run a program of launches, freeze no-meeting weeks around the US spring-forward and the EU spring-forward rather than shipping through both. Humans are already sleep-deprived. Your slide deck is not the emergency.
DST is a known schedule. Treat it like a planned outage. Check London, check Sydney, rebuild the invite, and stop saying “it’s always five hours.”
How to brief a team the Friday before
Send one paragraph, not a lecture: "Clocks move in the US this weekend (8 March). UK/EU do not move until 29 March. For three weeks, New York to London is four hours, not five. I rebuilt the Tuesday standup to keep 09:30 ET / 13:30 GMT. If your local time looks wrong, trust the city page, not last month's muscle memory."
Attach the pair link. Ask one person in each zone to screenshot the event as they see it and drop it in the thread. The screenshots will disagree. That disagreement is the bug report.
Do the same on 24 October, 4 April (Australia), and 3 October (Australia start). Put those four Fridays on a calendar named `DST hygiene` with a 20-minute hold. Treat it like certificate rotation.
If you run customer meetings, freeze new series creation on DST weekends. Humans are tired. Your renewal call can wait until Wednesday.
Sydney plus London plus New York is three regimes. Do not put them in one recurring hold without a named owner for invite repair.
Field notes from the city desk
In New York, start from FiDi. Slack after 19:00 is usually parked until the morning subway ride. The local prior remains 09:00–18:00 (America/New_York). If this article's advice conflicts with that desk, the desk wins — ask once and write it down.
Treat London as a place, not a resource pool. the City / Shoreditch keeps 09:00–18:00 as the honest window. Sorry-culture is real: a 19:00 Slack gets a next-morning reply and a faint wince. A calendar title that omits Europe/London is how this city gets pinged in the dark.
In Berlin, start from Mitte / Kreuzberg offices. Punctuality is kindness. 18:01 is already Feierabend unless the calendar said otherwise. The local prior remains 09:00–18:00 (Europe/Berlin). If this article's advice conflicts with that desk, the desk wins — ask once and write it down.
In Sydney, start from the CBD / Barangaroo. AEDT in summer, AEST in winter. US calls eat breakfast or dinner — never lunch. After 18:00 a ping is tomorrow. The local prior remains 09:00–17:00 (Australia/Sydney). If this article's advice conflicts with that desk, the desk wins — ask once and write it down.
None of these notes replace the live verdict. Open the city page at send time. Clocks and holidays move; this paragraph does not.