Why can a recurring executive meeting move even when nobody edits it?

Abstract

NIST distributes Coordinated Universal Time and leaves local time-zone and daylight-saving corrections to current system rules [1][2][9]. IANA maintains the time-zone database used by many systems, while IETF documents explain why those rules need an update process and a stable interchange format [5][6][7]. An executive calendar should therefore preserve the named time zone and local intent, not just a memorized offset.

Methodology

This review compares ten primary sources from NIST, the U.S. Department of Transportation, IANA, IETF, and BIPM [1][2][3][4][5][6][7][8][9][10]. It addresses scheduling controls, not the health effects or policy merits of daylight-saving time. Rules outside the United States can change under different authorities [2].

Offsets are temporary facts

A label such as Eastern time can use one UTC offset during standard time and another during daylight-saving time [2]. Some U.S. locations do not observe the change [1][2]. Recording only UTC minus five can therefore shift a future meeting from the organizer's intended local hour.

Store the zone and the intent

A durable invitation needs the event's named zone, local date and time, recurrence rule, and an explicit statement of which participant's local time should remain fixed. The IANA database records civil-time rules, and IETF procedures govern changes to that database [5][6].

Transition weeks deserve a separate check

Countries and regions do not move clocks on one global date [2]. For a recurring international meeting, review every participant's displayed local time around each relevant transition. Avoid abbreviations such as CST when the intended place or UTC offset is unclear.

Current software still needs human verification

NIST notes that operating systems apply local corrections and should receive current updates [1]. That does not prove that every calendar copy, travel brief, or forwarded invitation uses the same rule set. Check the rendered invitation in the organizer and attendee views before a consequential session.

Audit the exception, not every clock

Useful evidence includes the stored zone identifier, organizer intent, attendee local display, transition date, software version where relevant, and any manual override. A small transition calendar can prompt review without turning timekeeping into a daily manual calculation [7][8][9][10].

Key findings

  • A time-zone name and a UTC offset are not interchangeable across daylight-saving transitions [1][2].
  • The organizer should state which local time remains fixed.
  • IANA rules need updates because civil-time authorities can change them [5][6].
  • Transition-week verification should include attendee views, not only the organizer view.
  • An exception record is more useful than a permanent manual conversion process.

Sources

  1. Daylight Saving Time Rules, National Institute of Standards and Technology
  2. Local Time FAQs, National Institute of Standards and Technology
  3. Official U.S. Time, National Institute of Standards and Technology
  4. Uniform Time, U.S. Department of Transportation
  5. Time Zone Database, Internet Assigned Numbers Authority
  6. Procedures for Maintaining the Time Zone Database, Internet Engineering Task Force
  7. The Time Zone Information Format, Internet Engineering Task Force
  8. Network Time Protocol Best Current Practices, Internet Engineering Task Force
  9. NIST Internet Time Service, National Institute of Standards and Technology
  10. Standard Time, Bureau International des Poids et Mesures

Return to the Research Content library