Key Takeaways:
- A driver’s daily log uses the time standard in effect at the driver’s home terminal, not the local clock in every state the vehicle enters.
- ELDs synchronize time with Coordinated Universal Time (UTC), while compliant records and output files apply the home-terminal time-zone offset.
- Crossing a time-zone boundary does not, by itself, require the driver to change the ELD time zone or start a new log.
- The motor carrier should maintain accurate home-terminal and time-zone information in the driver’s ELD account, including the applicable daylight-saving offset.
- Drivers should follow the registered ELD’s user instructions, review records before certification, and report a wrong time display or profile setting to the carrier.
A driver may start in Arizona, cross into New Mexico, and finish in Texas while local clocks change along the route. Which time belongs on the driver’s log? Under the federal record-of-duty-status rules, the answer is the time standard at the driver’s home terminal. The driver does not switch the regulatory log to each new local time zone.
That distinction matters because an ELD handles more than the clock shown on a phone or dashboard. It synchronizes event time with UTC and uses the driver’s configured home-terminal time information when presenting and transferring records. A correct setup keeps duty-status events in one consistent time reference and makes the log easier to review.
This guide explains the federal rule, the difference between UTC and displayed log time, what to do when a route crosses time zones, and how drivers and carriers can prevent avoidable recordkeeping errors.
What Time Zone Should a Driver Use on a Daily Log?
The FMCSA Motor Carrier Safety Planner states that the time zone used on a driver’s daily log should be the time standard of that driver’s home terminal. The underlying record-of-duty-status requirements are in 49 CFR 395.8.
The home terminal is a carrier-assigned operating location associated with the driver. It is not necessarily the driver’s residence, the vehicle’s overnight location, the point where a particular trip began, or the local time zone at the driver’s current position.
For example, a driver assigned to a home terminal that observes Mountain Time keeps the daily record in that home-terminal time standard while driving into Central or Pacific Time. Dispatch appointments, customer schedules, and personal clocks may be expressed in local time, but those local references do not change the time basis of the driver’s RODS.
How UTC and Home-Terminal Time Work Together
ELD technical specifications require device time to be synchronized with UTC. UTC provides a consistent underlying timestamp for electronic events. The ELD also maintains a time-zone offset tied to the time standard in effect at the driver’s home terminal.
FMCSA explains that although ELD date and time are recorded in UTC, event times in an ELD output file must be provided using the time zone in effect at the driver’s home terminal. The FMCSA device-compliance guidance identifies an incorrect time basis in an output file as a compliance problem.
The applicable UTC offset also needs to reflect daylight saving time when it is in effect at the home terminal. FMCSA’s ELD technical FAQ explains that the offset used when an output file is generated should include daylight saving time if the home terminal is observing it at that time.
| Time reference | Purpose | Who should manage it |
|---|---|---|
| UTC | Underlying standardized event time used by the ELD | The ELD system |
| Home-terminal time standard | Time basis used for the driver’s daily log and compliant output | The carrier or ELD account configuration |
| Local time along the route | Appointments, dispatch communication, and everyday scheduling | Driver and dispatch, with the zone stated clearly |
Should a Driver Change the ELD When Crossing Time Zones?
Normally, no. Crossing a state line or time-zone boundary does not change the driver’s home terminal and does not create a reason to switch the log to the new local time. A consistent home-terminal reference prevents an hour from appearing twice or disappearing from the graph when a clock changes.
Drivers should not improvise device-setting changes during a trip. The exact controls available to a driver or administrator vary by ELD. Follow the registered device’s user manual and the carrier’s policy. If the displayed time or account profile appears wrong, notify the carrier or ELD support team so the configuration can be checked without creating an inaccurate record.
An annotation can add context to a record, but it does not repair a bad system configuration or replace a required duty-status entry. Drivers should use annotations for a truthful explanation and follow the ELD’s correction workflow. The original electronic record and edit history remain part of the ELD data.
Common Time-Zone Scenarios
| Scenario | Correct approach |
|---|---|
| A driver crosses from Mountain Time into Central Time | Continue using the driver’s configured home-terminal time standard. Do not change the log merely because local time changed. |
| Dispatch gives a delivery appointment in local time | Confirm the appointment’s stated zone and translate it for planning, while leaving the RODS time basis unchanged. |
| A team operation has drivers assigned to different home terminals | Verify each driver’s account separately. Do not assume one vehicle setting accurately represents both driver profiles. |
| The home terminal begins or ends daylight saving time | The configured offset must reflect the time standard then in effect at the home terminal. Confirm the ELD or carrier system handles the change correctly. |
| The ELD clock differs materially from a trusted time source | Stop relying on assumptions, document the issue, and contact the carrier or provider. Follow the device’s malfunction or diagnostic instructions when applicable. |
Driver Checklist for Accurate ELD Time Records
- Confirm the account information. Check that the carrier, home terminal, driver identity, and other profile information are accurate before relying on the log.
- Know the log’s time basis. Be able to identify the home-terminal time standard shown or used by the ELD.
- Keep dispatch times unambiguous. When a route crosses zones, label appointment and call times with the zone instead of saying only “8:00.”
- Review events before certification. Look for unexpected gaps, overlaps, wrong duty statuses, unidentified driving events, and timestamps that do not match the trip.
- Use edits and annotations correctly. Add truthful context and follow the device workflow. Never use an annotation to conceal driving time or create a false record.
- Report a persistent timing problem. A clock or synchronization issue may require carrier or provider action. Follow the ELD’s instructions rather than repeatedly changing settings.
FMCSA’s Using ELDs guidance also reminds drivers to review unassigned driving time and use annotations where the rule calls for an explanation. For a broader compliance review, see Geosavi’s ELD compliance checklist and Hours of Service guide.
Carrier Checklist for Home-Terminal Time Settings
- Maintain the correct home terminal and time-zone information for each driver account.
- Confirm how the ELD handles the UTC offset and daylight-saving changes at the home terminal.
- Train drivers to distinguish the RODS time basis from local appointment time.
- Use zone labels in dispatch messages when a route spans multiple time zones.
- Review logs for unexplained timing conflicts, unidentified driving, edits, and diagnostic or malfunction indicators.
- Keep the device user manual and required supporting materials available to drivers.
- Verify that the ELD model remains on FMCSA’s registered, self-certified device list.
Carrier review should focus on whether the record truthfully represents the driver’s duty status and whether the device is configured as required. A time-zone mismatch is not solved by shifting events until the graph looks convenient. The account data, system behavior, and event history need to remain accurate and auditable.
Time-Zone Errors and Hours-of-Service Calculations
A wrong display or account setting can make a valid sequence of events difficult to interpret, especially around midnight, a daylight-saving transition, or a route that crosses several zones. It can also cause the ELD output viewed by a safety official to show event times incorrectly.
However, crossing a time-zone boundary does not add or remove actual elapsed time from a driver’s limits. Hours-of-service compliance depends on the true sequence and duration of driving, on-duty, sleeper-berth, and off-duty periods. A compliant ELD uses UTC synchronization and the correct home-terminal offset to keep those records coherent.
Drivers remain responsible for reviewing and certifying their records, and motor carriers remain responsible for maintaining required records and accurate ELD account information. Neither party should treat a time-zone label as a substitute for checking the underlying duty-status events.
What to Do When the Displayed Time Looks Wrong
- Compare the ELD display with the home-terminal time standard, not only the local clock at the vehicle’s current location.
- Check the driver profile, home-terminal information, and the device’s documented time-zone behavior.
- Look for an active diagnostic or malfunction indicator.
- Notify the motor carrier and, when appropriate, the ELD provider. Record the issue according to company policy and the device instructions.
- Do not erase, hide, or recreate driving events to make the timestamps appear correct.
If the device has actually malfunctioned, use the separate procedures in 49 CFR 395.34. A suspected display mismatch should be investigated first; not every confusing local-time comparison is an ELD malfunction.
The Bottom Line on ELD Time Zones
A driver’s daily log should use the time standard at the driver’s home terminal. The ELD synchronizes time with UTC and applies the appropriate home-terminal offset for compliant records and data transfer. Local clocks may change along a route, but the RODS time basis does not change simply because the vehicle crosses a boundary.
Accurate account setup, clear dispatch communication, driver review, and a documented correction process do more for compliance than frequent manual changes. Fleets evaluating their logging process can also review Geosavi’s guide to choosing an electronic logging device for fleet operations or contact Geosavi for product support.