Your phone changes the clock automatically. The rule behind it is surprisingly manual.

At the spring and fall transition, an updated phone can change its displayed hour without asking. That convenience hides a chain of law, maintained time-zone rules and software updates.

In the United States, federal law sets the basic schedule. Daylight saving time begins at 2 a.m. on the second Sunday in March and ends at 2 a.m. on the first Sunday in November. NIST says it is not observed in Hawaii, American Samoa, Guam, Puerto Rico, the U.S. Virgin Islands or most of Arizona; the Navajo Nation in Arizona does observe it.

Standard time needed a legal standard

In 1883, U.S. and Canadian railroads adopted four zones to reduce the confusion created by roughly 100 locally established “sun times.” Federal oversight followed with the Standard Time Act of 1918.

Today, Title 15 establishes the federal standard-time framework and daylight-saving change dates, while Department of Transportation regulations in 49 CFR part 71 contain the official listing of U.S. time zones. Federal law lets a state exempt itself from seasonal clock changes under specified conditions; DOT notes that states cannot choose permanent daylight saving time on their own.

Your device is the last link in a long chain

A phone cannot infer a legislature's choice from sunlight. IANA maintains a Time Zone Database with code and data representing local-time history for representative locations. It is updated periodically to reflect political changes to time-zone boundaries, UTC offsets and daylight-saving rules. For most NIST computer time services, NIST distributes UTC while the operating system supplies the local-zone and daylight-saving correction.

That separation explains why updates matter. A system with outdated daylight-saving rules can show the wrong local hour even while its underlying time source remains accurate.

When U.S. clocks fall back, the hour from 1:00 to 1:59 occurs twice, so “1:30 a.m.” alone does not identify one instant. An unambiguous timestamp identifies an instant; a named time zone supplies the rules for converting between that instant and local civil time. RFC 9557 defines an optional extension that can carry a time-zone name alongside an RFC 3339 timestamp.

The clock change feels automatic because software handles the final step. Behind it sit a federal schedule, lawful exemptions, maintained time-zone data and software with current rules.