Lorixen.
EN

Weekly Appointments Across the Clock Change: Store Wall-Clock Time and a Zone Name

Short answer: A customer who books "every Tuesday at 9:00" is describing a wall-clock time in a place, not a fixed moment on the universal timeline. If your app converts that booking to one UTC timestamp and repeats it every seven days, the slot slides by an hour the week the clocks change. The fix is to store the local date, the local time and an IANA zone name such as Europe/London, then work out the real moment for each occurrence separately. Do that and the series stays at 9:00 on both sides of the change.

Why a weekly series drifts

Take a physio clinic in Manchester with a patient booked for Tuesday 28 October at 09:00. In the UK the clocks go back at the end of October. If the app saved that appointment as 09:00 UTC-plus-offset and simply added 7 days of seconds each time, then the Tuesday after the change would land at 08:00 or 10:00 on the wall clock, depending on the direction of the shift. The patient turns up at the old time, the therapist's calendar shows something else, and reminders go out at the wrong hour.

Nothing is wrong with the clock. The mistake is treating "same time next week" as "604,800 seconds later". Those two ideas agree for most of the year and disagree twice a year.

This is an illustrative scenario, but the pattern is real in every system that repeats events.

Common mistakes and the fix for each

Mistake 1: saving only a UTC timestamp for the series

A UTC value is perfect for a one-off event such as a flight departure. For a repeating rule it throws away the very information you need, which is which local time the customer meant.

Fix: keep three fields for the rule: the first local date, the local start time, and the zone name. Generate each occurrence from those at the moment you need it.

Mistake 2: saving a numeric offset instead of a zone name

An offset like +01:00 describes one particular week. It says nothing about what happens when the region changes its rules. A zone identifier from the IANA time zone database carries the full history and future rules for that place.

Fix: store Europe/London, America/Toronto or Australia/Sydney, never a bare offset or an abbreviation like "BST" or "EST", which are ambiguous.

Mistake 3: using the server's own time zone

Hosting platforms often default to UTC, and developers' laptops default to wherever they live. Code that quietly relies on the machine zone behaves differently on staging, production and a colleague's laptop.

Fix: pass the zone explicitly in every function that builds or formats a time. Set the server to UTC on purpose and treat that as an implementation detail, not a business rule.

Mistake 4: ignoring the two awkward local times

Each year there is one local time that does not exist and one that happens twice. When clocks jump forward, 01:30 never occurs. When they fall back, 01:30 occurs twice. A salon open at night, a cleaner starting at 01:00 or an on-call rota will hit these.

Fix: decide a rule in writing and test it. A common choice is "if the time does not exist, use the next valid minute; if it happens twice, use the first one". Whatever you pick, put it in the specification so the developer is not guessing.

Mistake 5: reminders computed at booking time

If a text reminder is scheduled for "24 hours before" at the moment the series is created, the reminder inherits any later drift.

Fix: compute the reminder from the occurrence's own local time shortly before it is due, or recompute pending reminders whenever rules change.

What to store, field by field

Field Example Why
Series start date (local) 2027-03-23 The first Tuesday, as the customer sees it
Local start time 09:00 The promise the customer was given
Duration in minutes 45 Lengths do not shift, ends are derived
Zone name Europe/London Carries the clock-change rules
Repeat rule weekly, Tuesday Human readable, easy to edit
Exceptions list 2027-04-06 skipped Holidays and moves without breaking the series

Each real occurrence is derived: take the local date and time, apply the zone, and you get the true instant for that week. If you also cache occurrences for fast calendar views, store the derived UTC instant next to the local values and regenerate the cache when the zone data updates.

Whose zone wins when two places are involved

A therapist in Dublin may see clients in several countries online. The series should follow the zone in which the service is delivered or the one the customer was promised, and your terms should say which. Show both on the confirmation: "Tuesday 09:00 Dublin time (04:00 for you in Toronto)". On the storage side, one zone owns the series.

A short test plan before launch

Write these cases down and run them whenever the booking code changes:

  • A weekly series that crosses the spring change in your main region, in both directions.
  • A series created by someone whose browser is in a different zone from the business.
  • A booking at the nonexistent local time and one at the repeated local time.
  • A series in a region with no clock change at all, to confirm nothing shifts needlessly.
  • An export to a calendar file and a re-import, checking the time stays put.

Browsers can help with the display work. The Intl.DateTimeFormat reference on MDN shows how to format a moment in a named zone without hand-rolled offset arithmetic.

FAQ

Do I need to store UTC at all?

Yes, for single events and for derived occurrences. Just do not let it be the only truth for a repeating rule.

What happens if a country changes its clock rules?

Zone databases are updated several times a year. Keep your runtime and operating system updated, and because you stored the local time and zone name, future occurrences correct themselves once the data updates.

Should a repeating series be one record or many?

One rule plus a list of exceptions is easier to edit, with generated occurrences for the calendar view. Many separate rows are fine if edits to "this and following" are handled deliberately.

Can a spreadsheet booking sheet suffer from this?

Yes, if it stores times as plain numbers after pasting from another system. Keep the date, time and zone in separate columns and check the weeks around the change.

If your booking tool shifts appointments when the clocks change, tell us how it behaves and we will look at the fix with you.

Sources

WhatsAppBook a call