- What is the biggest risk of not preparing for DST?
- The biggest risk is missed or mis-timed meetings. When one region changes its clocks but another has not yet (or does not observe DST at all), standing meeting times shift by one hour without participants necessarily being aware. The result ranges from meeting at the wrong time to complete no-shows.
- How far in advance should I notify my team about DST?
- One week in advance is the practical minimum. Two weeks is better. The notification should state clearly which team members are in DST-observing regions, what their new UTC offsets will be, and which recurring meetings will change in local time.
- Do calendar apps handle DST automatically?
- Most modern calendar apps (Google Calendar, Outlook, Apple Calendar) handle DST automatically for events stored with a named time zone. The problem occurs with events stored as absolute UTC times, meetings shared via plain text links, or participants who manually entered times without time zone labels.
