Daylight Saving Time Checklist

A practical checklist for meetings, webinars, travel calls, and recurring schedules that cross daylight saving time changes.

Daylight saving time creates the worst time-conversion mistakes because the error often appears only for a few weeks. A meeting that was comfortable for months suddenly moves by an hour for one group but not another. The easiest way to prevent that is to review important schedules before seasonal clock changes.

Before sending a new invite

  1. Use a specific date, not only a generic offset.
  2. Convert using named time zones such as America/Chicago or Europe/London.
  3. Check whether the meeting crosses midnight for any participant.
  4. Include at least two local examples in the invitation.
  5. Avoid abbreviations such as CST or IST when the audience is international.

Before a daylight saving transition

  1. Review recurring meetings with participants in North America, Europe, Australia, New Zealand, Chile, or the Middle East.
  2. Check whether one region changes clocks earlier than another.
  3. Confirm high-stakes meetings directly with attendees.
  4. Update webinar landing pages and reminder emails if the public time changes for some locations.
  5. Re-check calendar automation after the transition week.

For webinars and public events

Public events need extra clarity because attendees may not know the host time zone. Put the host city, UTC time, and a converter link near the registration button. If the event happens during a transition week, include a short note telling visitors that local clock changes may affect the converted time.

For remote teams

Remote teams should keep a small seasonal checklist for recurring meetings. Many teams discover DST problems only after someone misses a call. A better system is to review standing meetings twice per year, identify people who gained or lost an hour, and decide whether to adjust the recurring time or keep it stable for the host.

For travel

Flights, hotel check-ins, cruise departures, and tours use local time at the location. Calendar apps sometimes display travel events in your current device time zone, which can be misleading during a trip. Before travel, write key times in plain language: “8:00 PM local Orlando time” or “10:30 AM London time.”

Best practice: If a time matters, verify it by date and city. Offset-only shortcuts are where daylight saving mistakes happen.