ELD Time Change: Check Your Home-Terminal Clock

November 1 repeats an hour in much of the United States. Check the ELD home-terminal offset and the time zone on your pickup appointment.

ELD Time Change: Check Your Home-Terminal Clock

Illustrative archive truck photograph; no ELD screen, specific trip or November 1 event is depicted. Jon Champaigne / Pexels, Pexels License.

The November 1 clock change creates a practical question for a driver checking a log: which clock is this? In much of the United States, the local hour repeats as daylight saving time ends. The useful check is the home-terminal time reference in the electronic logging device, followed by the local time attached to the next appointment. A repeated label on a clock does not, by itself, authorize extra driving.

NIST lists November 1 at 2 a.m. local time as the end of daylight saving time for 2026. The clock moves back to 1 a.m. in places observing that change. This is a calendar event, not a new trucking regulation. For an owner-operator or small fleet, today's job is to keep the log, dispatch message and customer appointment understandable to the next person who reads them.

Start with the terminal, not the phone

FMCSA's ELD guidance explains that date and time are stored using Coordinated Universal Time, or UTC. The data file uses the UTC offset in effect at the driver's home terminal. Daylight saving time belongs in that offset when it applies there; it does not belong when it is not in effect. That reference is more specific than the time currently displayed on a phone.

Think of a driver away from the home terminal who receives an appointment screenshot. The phone, customer facility and log can involve different time references. Before deciding that one is wrong, identify what each represents. Write the facility's city and appointment time beside its confirmation. Separately check the terminal reference shown by the ELD. This is a communication check, not an instruction to reset the device or rewrite recorded driving.

The same 1:30 can identify two different moments

Here is an illustrative Houston conversion for November 1, 2026. The first 1:30 a.m., under Central Daylight Time, corresponds to 06:30 UTC. The second 1:30 a.m., under Central Standard Time, corresponds to 07:30 UTC. The local clock labels match, but the two moments are an hour apart. These are calculated examples, not records from a driver's trip.

A screenshot saying only “1:30” leaves that distinction out. Adding the date, city and applicable time reference makes the message clearer. If a facility supplied an ambiguous overnight appointment, ask it to confirm which occurrence it intended. Do not decide that an ambiguous message proves a missed appointment or a duplicate log entry. Keep the original confirmation while resolving the question.

What the ELD specification actually says

Section 4.4.3 of the ELD specifications in Appendix A to Subpart B of Part 395 addresses conversion from UTC to the time standard at the driver's home terminal, including daylight saving changes. It also ties the record of duty status to that terminal's time standard and the carrier-specified starting time. The underlying reference therefore matters when reviewing a day's record.

For a fleet handoff, distinguish the recording requirement from your own reminder system. A dispatch calendar can help people meet appointments, but its labels do not establish how the ELD stored an event. Likewise, this article does not establish that a particular device is configured correctly. Read the device's instructions and have the responsible carrier contact or provider review a discrepancy before treating it as an equipment failure.

Do not turn the repeated hour into driving permission

FMCSA's general summary for property-carrying drivers describes an 11-hour driving limit after 10 consecutive hours off duty and a 14-hour driving window under the standard rules. Its summary also identifies other provisions and exceptions. The daylight saving calendar does not itself replace those rules or establish that a particular driver's remaining time has increased.

A safe dispatch decision uses the driver's actual duty record and the rules applicable to that operation. A phone moving back an hour is not evidence of an additional hour available to drive. If dispatch and the driver disagree, resolve the time-reference question before building another load around the assumed availability. Do not make a log look convenient by deleting a real event or changing its meaning.

A short check before the next handoff

  • Identify the home terminal and the time reference used by the ELD.
  • Confirm the date, city and local time of the customer appointment.
  • Clarify an overnight time that falls in the repeated hour.
  • Keep the original appointment message and relevant log information together.
  • Ask the responsible carrier contact or provider to review an unexplained discrepancy.
  • Evaluate available driving time from the applicable duty record, not a phone clock.

These checks are TSN's practical workflow, not a new list of federally required documents. They are useful even after the overnight transition has passed: an unclear timestamp can remain in a message or handoff later on Sunday. Correcting the explanation should make the record easier to understand, rather than conceal what happened.

Keep route planning tied to information you can confirm

If the next trip also needs a planned service stop, research businesses in Truck Savers Finder and confirm their services and local hours directly. A listing does not certify ELD support or guarantee availability. The immediate takeaway for this Sunday is to name the clock before interpreting the time: terminal reference for the log, confirmed local reference for the appointment, and actual duty information for the driving decision.

Original sources: FMCSA, ELD UTC-offset guidance; NIST, 2026 daylight saving dates; eCFR, ELD specifications, section 4.4.3; FMCSA, hours-of-service summary. Reviewed November 1, 2026. Conversions, scenarios and checklist are TSN editorial examples.