Every timezone bug is really a calendar bug

Wed, 15 Jul 2026 00:00:00 +0000

Scheduling bugs cluster around two moments in the year, and they are the same two moments for everyone: the second Sunday in March and the last Sunday in October — give or take, depending on which hemisphere and which government.

The assumption that breaks

The bug is almost always this: storing a meeting as a wall-clock time plus an offset rather than as an instant plus a timezone.

{ "startsAt": "2026-10-24T09:00:00+01:00", "recurrence": "WEEKLY" }

That looks unambiguous, and for a single meeting it is. But the recurrence rule has to answer “when is the next one?” — and on 25 October, +01:00 stops being the correct offset for Europe/London. Naively adding seven days gives you 2026-10-31T09:00:00+01:00, an instant that renders as 8:00am to the host. Their weekly standup silently moves an hour earlier, and only for the half of the team in a country that just changed its clocks.

Booking pages that convert

Wed, 08 Jul 2026 00:00:00 +0000

A booking page has exactly one job, and the gap between a good one and a bad one is mostly about how much work you ask the guest to do before they see a time.

1. Show times before you ask for anything

The single biggest drop-off is a form that appears before the calendar. A guest arrives wanting to know whether you’re free Thursday. Asking for their name, company, and reason for meeting first inverts the order — they’re paying a cost before receiving any value. Put the slots first and collect details on the confirm step, when they’re already committed.

Playbook on BunnyCal Blog

Every timezone bug is really a calendar bug

The assumption that breaks

Booking pages that convert

1. Show times before you ask for anything