How to schedule recurring meetings that survive daylight saving

You set up a recurring call months ago. It has been fine every week. Then one Monday half the room joins an hour early, or an hour late, and nobody is quite sure who is wrong. The culprit is almost always daylight saving, and the fix is simpler than the confusion suggests.

Why does a fixed meeting suddenly move?

Daylight saving does not arrive everywhere at once. Different regions shift on different dates, so for a short window the usual gap between two cities is off by an hour. A meeting pinned to one person's local time will look like it has jumped for everyone else, even though that person's clock never changed. The meeting did not move; the gap did.

For a fuller explanation of the mechanics, see does daylight saving affect meetings.

When exactly does the drift happen in 2026?

The danger is never a single day; it is the gap between two transition dates. In 2026 there are two such windows in each half of the year. Inside each window, one region has already changed and its neighbour has not.

So a London-to-New York call is briefly four hours apart instead of five between 8 and 29 March, and again between 25 October and 1 November. Any recurring meeting that lands inside one of these windows deserves a second look.

What are the three reliable fixes?

There is no way to repeal daylight saving, so the goal is to make your meeting predictable in spite of it. Three approaches work, in roughly increasing order of how little thought they cost you.

• Anchor to one zone. Pick the person whose schedule matters most, fix the meeting to their local time, and accept that everyone else flexes by an hour during the changeover windows. Simple, but it quietly pushes the burden onto the people who are not the anchor.
• Re-check and re-send. Put the four danger dates in your own calendar. When one arrives, confirm the local times still suit everyone and re-send the invite if needed. Reliable, but it is manual work you must remember to do, twice a year.
• Let a tool do it. Use a scheduler that stores each attendee's zone with its daylight saving rules. It recalculates the local times for every date, so the invite is always correct, including inside the windows. No diary reminders, no mental arithmetic.

Why anchoring to a zone beats fixing a UTC time

It is tempting to "solve" drift by locking the meeting to a fixed UTC time. That keeps the slot stable on a clock, but it ignores the human reality: people work to their local hours, and those hours move with the seasons. A 16:00 UTC call is a comfortable late morning for New York in winter and an inconvenient hour later in summer. Anchoring to a named zone keeps the meeting tied to when a real person is actually at their desk, which is what you usually want.

How Atlas handles this

Atlas stores every person you pin with their full time zone, including its daylight saving rules, so the local times it shows are always right for the date you are looking at, windows and all. You see at a glance who is awake, pick a slot that works, and write it to your calendar in one tap. For the wider etiquette of keeping a distributed team happy, see how to schedule meetings across time zones without annoying your team.