Daylight-saving appointment and schedule audit

Event date and scope

Under NIST’s current US rule, the spring transition is calculated as March 14,2027: the second Sunday in March. In observing locations,2:00 a.m. local advances to 3:00 a.m.; some US localities do not observe DST. Confirm the rule for each appointment location. Other worksheet dates are suggestions.

8 planning actions with caption examples

• 2027-02-28 — Check local observance: Confirm whether each service location and customer time zone observes the March change. Note any locations where clocks do not change. Caption: “We’re checking local time-change details for appointments scheduled around March 14. Questions about your booking? Contact [confirmed route].”
• 2027-03-02 — Review booking-system settings: Check the scheduling platform’s time-zone setting, calendar integration, daylight-saving handling, and any manual overrides. Caption: “For appointments at [location], your confirmed time is [date, local time and named time zone]. View the current booking at [link] or ask [contact] about a mismatch.”
• 2027-03-05 — Compare staff calendars: Ask staff in each location to compare their roster with the system schedule and report mismatched times to the coordinator. Caption: “Team members: please compare your March 14 schedule with the booking system and flag any mismatch through [internal route].”
• 2027-03-08 — Check reminders and confirmation templates: Review automated email and text templates for clear local time zones and a working way for customers to confirm or ask a question. Caption: “Appointments around the clock change show the local time listed in your confirmation. Check your message or contact [confirmed route] if you need help.”
• 2027-03-10 — Review queued posts and event links: Check scheduled social posts, live event links, webinar invitations, and any time-specific promotion scheduled across the transition. Caption: “[Event or appointment] is [date and local time] in [named location/time zone]. Find the current event page or booking confirmation at [link].”
• 2027-03-12 — Send location-specific confirmations: For affected appointments, use the tested booking system to send a concise confirmation that includes the local time zone and contact route. Caption: “Your [date] appointment is listed for [confirmed local time and time zone]. Reply or use [confirmed contact] if that differs from your confirmation.”
• 2027-03-14 — Check the transition-day schedule: Have the coordinator verify the day’s appointments in the live system and follow the approved process for any reported mismatch. Caption: “Today’s appointments follow the local time shown in each confirmation. For help, contact [confirmed route].”
• 2027-03-15 — Close the time-change audit: Review the next day’s appointments and log any system issue for the scheduling administrator. Update only tested procedures. Caption: “We’ve completed our time-change schedule check. Please continue to use the local time in your appointment confirmation: [link].”

Copy a cross-system audit record

Compare the same booking in each system instead of manually moving every appointment by an hour. Record any mismatch for the scheduling administrator.

Fictional comparison: a 9:00 a.m. appointment in America/New_York on March 13,2027 corresponds to 14:00 UTC; a 9:00 a.m. appointment there on March 15 corresponds to 13:00 UTC under the current spring rule. The intended local time can stay the same while its UTC offset changes. Verify the actual system’s behavior.

• Location and named time zone: [location/IANA zone]. Does this location observe the transition? [confirmed answer].
• Booking reference: [private reference]. Intended local date/time: [value]. UTC instant if available: [value].
• Booking-system display: [value]. Staff-calendar display: [value]. Customer-reminder display: [value].
• Queued post/event-link display, if relevant: [value].
• Mismatch and assigned coordinator: [finding and role]. Checked at: [timestamp]. Verified resolution: [result].

Editable action plan

The CSV matches the eight dated actions and their caption examples. Verify the organizer’s facts before sharing them.

Download the plan (CSV)

Edit the suggested dates, task owner, and organizer-confirmed details.

Add suggested dates (ICS)

The named anchor is calculated from a recurring source rule, not a directly announced 2027 schedule. Other all-day dates are editable planning suggestions; confirm your actual local or event schedule.