Overview
An overnight coverage plan needs an owner for every moment, including a clock change. This checklist helps a business and its answering provider agree on the handoff and test the configured schedule. It is suggested planning guidance, not a claim about an AnSer scheduling integration.
Identify the affected local schedule
NIST explains that the U.S. spring transition skips from 2 a.m. to 3 a.m.; the autumn transition returns from 2 a.m. to 1 a.m., repeating an hour. Its published 2026 dates are March 8 and November 1. These rules apply where daylight saving time is observed; do not apply them to every U.S. location.
Record the named time zone used by the office, receiving contact, and routing schedule. Ask the system administrator whether each configured change follows local wall-clock time or a fixed instant. Verify the effective dates against the current source when preparing a future transition.
Assign ownership of the skipped or repeated interval
For a spring handoff scheduled inside the missing hour, agree on the actual changeover instant rather than leaving a nonexistent local time in the instructions. For an autumn handoff during the repeated hour, identify which occurrence is intended, including its UTC offset.
Have the outgoing contact, incoming contact, and answering provider confirm the same boundary. Record who retains an unresolved request received before that boundary; changing the roster does not itself demonstrate that another person accepted the work.
Check the schedule that actually controls calls
Microsoft documents that new Outlook for Windows can show the affected hour as omitted or duplicated in its calendar time bars, depending on the view. That visual distinction can help review a roster, but it is not evidence that a separate phone system uses the same settings. Compare the approved roster with the schedule that selects the answering or on-call destination.
- Use an isolated test configuration or a provider-supported preview; do not change a production system clock to simulate the transition.
- Check a call before the boundary and a call after it. For the autumn repeated hour, distinguish the two occurrences in the test record.
- Verify the receiving destination, caller-facing next step, and fallback when the selected person does not acknowledge the request.
Leave an unambiguous handoff record
Record the test date, named time zone, UTC offset, intended contact, observed destination, and result. Use the same timestamp convention in any shared incident or follow-up record so two identically displayed local times are not mistaken for one event.
Before the transition, resolve failed checks and confirm who watches the handoff. Afterwards, review unresolved requests and any temporary exceptions. Keep holiday closures as separately dated changes; a clock transition does not imply that the business is closed.
