DST is two weeks of silent bugs
Daylight saving time does not only shift clocks. It shifts overlap windows, standup attendance, on-call handoffs, and the mental map of "what time is friendly for everyone."
Remote teams feel DST twice a year because members sit in regions that change on different dates or not at all. A meeting that was fair in March becomes cruel in April without anyone editing the invite.
Treat the calendar like code: version it, test it twice a year, and deploy a note before production breaks.
Mistake 1: Storing "EST" instead of a real zone
Labels like EST, CET, or GMT+2 are ambiguous half the year. They do not encode whether daylight rules apply.
Store IANA names: America/New_York, Europe/Zagreb, Australia/Sydney. Put them in team docs next to people's names.
Calendar tools usually convert correctly when the event time zone is set properly. Text in Slack does not.
Mistake 2: Repeating "same local time" globally
"Let's always meet at 9:00 our time" sounds stable. For colleagues elsewhere, 9:00 your time jumps relative to their sleep when DST diverges.
Fix: anchor shared events to UTC in the invite description, even if the UI shows local.
Example line in the invite body: "14:00 UTC (see local conversion)."
The timezone collaboration guide helps sanity-check conversions and team norms without mental math.
Mistake 3: Forgetting regions that do not observe DST
Parts of Australia, Asia, Africa, and Arizona ignore US or EU shifts. Your US team "spring forward" may move overlap without a matching move in their city.
Maintain a simple table of who shifts when. Update it the week before US and EU changes.
Mistake 4: SLA and on-call math in local heads
"We respond within one business day" breaks when business day start times drift relative to each other.
Write SLAs against UTC cutoffs or name explicit hours in one zone everyone agrees is canonical for ops.
On-call rotations need the same discipline. Handoff at "17:00 local" is two different UTC instants across half the year if you picked the wrong local.
Mistake 5: No rehearsal meeting
Two weeks before major shifts, run a fifteen-minute calendar audit:
- List standing meetings
- List external client calls
- Note who is affected
- Confirm each invite's time zone field
- Post the new overlap chart
Finding fair meeting times is easier when the inputs are correct.
Mistake 6: Blaming people for missing one occurrence
Someone will miss the first weird standup. The fix is process, not shame.
Send a single correction message with UTC, updated overlap, and a link to the shared planner if you use one.
Async as DST shock absorber
Decisions that must happen in overlap should shrink during DST transition weeks. Push readouts async; keep live time for true conflicts.
Re-read overlap matters more than local time during DST weeks. The question is not "whose morning is sacred" but "how many shared hours remain."
Example: the standup that moved silently
Example: Team stands at 09:00 London all year. After spring forward, New York is five hours behind, not four. For two weeks half the room is late until someone notices.
Fix: publish standup time in UTC in the calendar series and verify overlap after each DST change.
Personal checklist for ICs
The week US or EU shifts:
- Re-open each recurring invite and read the time zone field
- Compare phone world clock to laptop clock after the jump
- Update your auto-reply or status with corrected UTC overlap
- Tell family when your "late meeting" night moves
Document in the team wiki
Maintain a short "DST runbook" page: dates you care about, last audit date, owner, link to overlap chart. Assign an owner who is not the most time-zone-punished person on the team.
After the shift, send one team message the day after clocks change: "Standup is now 14:00 UTC until next shift." Link the wiki runbook. Repeat for two weeks because stragglers exist.
Automate reminders
Put a recurring calendar task on the Monday after DST for every shared series: verify UTC offset and attendee list.
Runbook for twice-yearly clock changes
Two weeks before DST: list every recurring meeting, export attendee zones, recompute overlap. Week of: post updated times in team channel. Week after: ask who missed anything.
New hires are the canary. If someone joins the week after DST and immediately misses standup, onboarding docs still describe yesterday's offset.
Onboarding docs should show how to convert meeting times to local time using the team reference zone, not memorized offsets. Include a worked example crossing spring forward.
Async response windows shift
When clocks jump, restate message windows in status for two weeks. People muscle-memorize times. See async response expectations across time zones.
Store meeting times in UTC or one agreed reference in tickets, not "3pm" alone.
DST errors look like carelessness to executives and like exhaustion to parents on bad slots. Individual fixes reduce team-wide confusion when process lags.
Walkthrough: EU spring forward with US still on standard time
Example: For one week, London and New York overlap shifts by an hour relative to what muscle memory says. A standup series anchored to "10:00 London" still fires, but the New York attendee's local time jumps.
The organizer posts: "This week only: standup is 10:00 Europe/London / 05:00 America/New_York / 10:00 UTC until US catches up." After US shifts, recompute and post again.
Without that post, half the room attends at the wrong local hour and the other half wonders why attendance dropped.
Walkthrough: engineer in non-DST region
Example: A teammate in Japan does not shift. US spring forward moves US overlap earlier relative to their evening. They did nothing wrong; the map changed.
Update the overlap chart, not the person. Ask whether recurring US evening calls should move async for two weeks or rotate to a US morning slot.
Product and marketing deadlines
Campaign launches tied to "midnight local" without zone create duplicate posts or early releases. Store launch instants in UTC in runbooks the same way engineering stores deploy times.
Marketing and support should share the DST runbook link, not a separate oral tradition.
Inventory your recurring series like production jobs
Export a list of recurring calendar events quarterly. Columns: title, organizer, time zone field value, attendee zones, last manual audit date.
During DST prep, sort by attendee spread. Fix the widest series first. Standup and on-call handoffs beat optional socials for priority.
Treat a wrong time zone field on a recurring invite like a config bug: patch, announce, verify next occurrence.
Client-facing SLAs
If you promise "response by next business day" to clients in multiple countries, define business day in one reference zone or in UTC hours. DST week is when vague SLAs become support tickets about support tickets.
Calendar software lies in subtle ways
Most tools show local time and assume you never travel. Recurring events inherit a time zone from the organizer's laptop at creation time. If that field was wrong years ago, every occurrence since has been wrong in UTC even when the wall clock looked fine.
Export one recurring series once a year and read the time zone field, not only the friendly label. Example: A series created while someone was visiting another city can anchor to the wrong zone forever. Fixing the next occurrence without fixing the series root replays the bug in six months.
Contractors and mixed employment types
Employees, contractors, and clients often live under different DST rules in the same call. A contractor in a non-observing region does not shift when the US does. Your overlap chart must list people, not countries.
When legal or finance joins from a single headquarters, they may assume everyone shifted together. Send the UTC table in the invite body the week before US and EU changes.
Incident handoffs across the jump
On-call rotations keyed to local midnight need explicit UTC handoff times in the runbook for the two weeks around a change. Example: Handoff documented as 00:00 America/Chicago becomes a different instant relative to Dublin than it was last month. Update the runbook line, not only the calendar invite.
Pair DST audits with meeting budget
DST weeks are a good time to delete recurring meetings that no longer earn their overlap. If a weekly sync barely fits after the shift, move it async rather than slide it into someone's dinner hour. When a remote team needs a meeting is the filter; DST is the forcing function.
DST is boring infrastructure. Teams that treat it that way lose fewer hours to apologies and regain sleep where overlap actually lives.