Share on print

Rand ELD Log Edit Guidance

This article is to outline some commonly encountered Rand ELD log edit restrictions and best practices when editing your logs.

Log Edit Restrictions
The first and last logs cannot be edited The last log can be deleted if needed. When it is deleted the previous duty status log will be extended to the current time.
Two adjacent logs cannot have the same duty status. Instead of using the same duty status, it is generally best to delete one of the records or edit the start time of the entries.
The start date and time is the parameter that can be moved to increase/decrease the time of the current and previous logs.
Automatically recorded driving time cannot be shortened. This is a requirement from the ELD mandate as described in the Reference Information below. If the automatic drive time is incorrect, the driver will need to annotate the proper information in the records.
Log Edit Behavior
When you delete a log, the end time of the previous log is automatically extended to the end time of the deleted log (the last log duration is increased). Example:
  • Initial logs
    • Off Duty log: 12:11 am – 8:15 am
    • On Duty log: 8:15 am – 8:33 am
    • Driving log: 8:33 am – 9:10 am
  • Edited logs
    • Deleting the On Duty log at 8:15 am – 8:33 am will result in the following logs
      • Off Duty log: 12:11 am – 8:33 am
      • Driving log: 8:33 am – 9:10 am
Logs expanding across multiple days are only available for editing on the day the duty status began. Example:
Off Duty log from 12/1/2021 to 12/4/2021 will only display the log for editing on 12/1/2021.
Best Practices
If the current log needs an earlier start time Option 1
  • On the Logbook graph
  • Select "+" and then "Edit Logs"
  • Select the "Move" option
  • Drag the start time of the current duty status to the desired time
    • If you are unable to get the exact start time from the graph edit, you can adjust the start time once you have switched to a new duty status.
Option 2
  • Select a new duty status
  • Edit the previous duty status logs start time
  • Delete the current duty status log
Assuming Unidentified Driving time When assuming unidentified driving time, the duty status following the assumed driving time will be updated to On Duty. If On Duty is not the correct duty status, you will need to edit the duty status to properly reflect your logs.
Ensure the correct rule set is applied in the Rand ELD app — US (70 Hours/8 Days) vs Canada (Cycle 1)
Reference Information
FMCSA ELD Mandate Version 2.1 (July 18, 2017)
4.3.2.8.2 Driver Edit Limitations
  1. An ELD must not allow or require the editing or manual entry of records with the following event types, as described in provision 7.25 of this Standard:
    1. An intermediate log
    2. A driver’s login/logout activity
    3. CMV’s engine power up/shut down, or
    4. ELD malfunctions and data diagnostic events
  2. An ELD must not allow automatically recorded driving time to be shortened or the ELD username associated with an ELD record to be edited or reassigned, except under the following circumstances:
    1. Assignment of Unidentified Driver records: ELD events recorded under the “Unidentified Driver” profile may be edited and assigned to the driver associated with the record; and
    2. Correction of errors with team drivers: In the case of team drivers, the driver account associated with the driving time records may be edited and reassigned between the team drivers if there was a mistake resulting in a mismatch between the actual driver and the driver recorded by the ELD and if both team drivers were respectively indicated in each other’s RODS as a co-driver. The ELD must require each co-driver to confirm the change for the corrective action to take effect.
4.3.3.1.3 Motor Carrier’s Post-Review Electronic Edit Requests
  1. An ELD may allow the motor carrier (via a monitoring algorithm or support personnel) to screen, review, and request corrective edits to the driver’s certified (as described in provision 4.3.2.3 of this Standard) and submitted RODS through the ELD system electronically. If this function is implemented by the ELD, the ELD must also support functions for the driver to see and review the requested edits.
  2. Edits requested by anyone or any system other than the driver must require the driver’s electronic confirmation or rejection.
Canadian Technical Standard for Electronic Logging Devices Version 1.2 (October 27,2020)
4.3.2.8.2 Driver Edit Limitations
  1. An ELD must not allow or require the editing or manual entry of records with the following event types, as described in provision 7.25 of this Standard:
    1. An intermediate log
    2. A driver’s login/logout activity
    3. CMV’s engine power up/shut down, or
    4. ELD malfunctions and data diagnostic events
  2. An ELD must not allow automatically recorded driving time to be shortened.
  3. An ELD must not allow the ELD username associated with an ELD record to be edited and reassigned, except under the following circumstances:
    1. Assignment of Unidentified Driver records: ELD events recorded under the “Unidentified Driver” profile may be edited only for the purpose of reassignment to the driver associated with the records.
    2. Correction of errors with team drivers: In the case of team drivers, the driver account associated with the driving time records may be edited and reassigned between the team drivers if there was a mistake resulting in a mismatch between the actual driver and the driver recorded by the ELD and if both team drivers were respectively indicated in each other’s RODS as a co-driver. The ELD must require each co-driver to confirm the change for the corrective action to take effect.
    3. Correction of errors for a driving record that was originally recorded under the “Unidentified Driver” profile and assumed by the driver: The driver account associated with the driving time records may be edited only for the purpose of reassignment to the unique “Unidentified Driver account”.
4.3.3.1.3 Motor Carrier’s Post-Review Electronic Edit Requests
  1. An ELD may allow the motor carrier (via a monitoring algorithm or support personnel) to screen, review, and request corrective edits to the driver’s certified (as described in provision 4.3.2.3 of this Standard) and submitted RODS through the ELD system electronically. If this function is implemented by the ELD, the ELD must also support functions for the driver to see and review the requested edits.
  2. Edits requested by anyone or any system other than the driver must require the driver’s electronic confirmation or rejection.