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.
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 (team timezone planner).
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.
Broader collaboration habits live in timezone collaboration without chaos.
Overlap beats local pride
During DST weeks, re-read overlap matters more than local time. The question is not "whose morning is sacred" but "how many shared hours remain."
DST errors look like carelessness to executives and like exhaustion to parents on bad slots. Treat the calendar like code: version it, test it twice a year, and deploy a note before production breaks.
Personal checklist for ICs
The week US or EU shifts, do this for yourself even if the company forgets:
- 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
Individual fixes reduce team-wide confusion when process lags.
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.
Rotation of admin work matters here too.
After the shift: confirm in writing
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.
Confirmation beats assuming everyone's calendar auto-fixed.