Driver Logs

Topics in this section:

* A non-driver application user must have a user role with View/Modify permission to the HOS Reports feature to modify log resources and log events. Drivers can modify and certify their own logs.

Related topics:

What is the purpose of the Driver Logs page?

The Driver Logs page allows drivers, supervisors, and other authorized personnel to view, annotate, edit, and print a driver's record of duty status (aka driver log). Drivers may also use this page to certify their records of duty status.

To view a driver's log for a particular day:

  1. Locate the driver in the Driver list by typing in their name or ID and click to select the appropriate driver. If you are the driver, you will not see an option to select a driver.
  2. Select the date you wish to view. The current date (today) is selected by default.
    To change this date:
  3. If country selection has been enabled for your organization, choose the log format desired.*
  4. Click the View Logs button.
  5. The country flag icon will indicate whether logs are displayed in US Format or Canada Format.

* If country selection has not been enabled for your organization, the log will be displayed in the format corresponding to the country of the driver's configured primary rule set. Country selection can be configured in the Organization Detail page.

What information is displayed on the Driver Logs page?

Driver Logs Page

The Driver Logs page shows all information required by US and Canadian ELD regulations for a driver's record of duty status, plus additional information to help supervisors and other personnel verify a driver's hours of service and determine whether edits have been made to the original record.

Date & Time

Carrier Information

Driver Information

ELD Information

Daily Summary Data

Graph Grid

Vehicles and Resources

Log Events

What determines the time zone of a driver log?

The time zone of a driver log is based on settings for the home terminal to which the driver was assigned on that date. If the driver's home terminal assignment was changed, the last home terminal to which the driver was assigned on a given day will determine the time zone of the log for that date.

What does the View Edits button do?

Clicking the View Edits button displays the Log Edit Report page, showing all amendments made to the record of duty status for the selected driver and date. Use this feature to see who made changes and the reasons given for each change.

What does the View Map button do?

Clicking the View Map button displays the Maps View page, showing the movements of the selected driver on the date of the driver log.

* This button will be visible only if the Mapping application is enabled and the viewer has a user role with View Only or View/Modify permission to the Telemetry Data feature.

What does the View Proposed button do?

Clicking the View Proposed button changes the graph grid to reflect the time spent in each of the four duty statuses if the driver were to accept all Inactive - Requested changes that have been proposed.

When viewing the proposed log, click the View Active button to change the graph grid back to reflect only Active events.

What does the Hide history checkbox do?

Checking the Hide history checkbox filters the Log Events table so that the current log of record is easier to see and understand. When Hide history is checked, Inactive - Changed and Inactive - Rejected events are hidden and only Active and Inactive - Requested events are shown. They will still be included as required for compliance on PDF/csv printouts and data file transfers.

What does the Hide malfunctions and diagnostics checkbox do?

Checking the Hide malfunctions and diagnostics checkbox also filters the Log Events table. When Hide malfunctions and diagnostics is checked, all Malfunction and Data Diagnostic events are hidden from the website view of the driver log. They will still be included as required for compliance on PDF/csv printouts and data file transfers.

What does the Show HOS violations checkbox do?

Checking the Show HOS violations checkbox shows all HOS violations that start, end or overlap the displayed log day.

If the driver has rule set history data, that data will be used to calculate the violations being displayed. If the driver does not have historical rule set data, their default US or Canada rule set will be used to calculate violations based on the country format selected when viewing the log.

A violation is reported if a driver operates a commercial motor vehicle in excess of the hours of service limits established for the driver's rule set, including cycle, operating zone, and rule set. Check the driver's log or Driver Details to verify under which regulation the driver was operating. If a driver runs out of driving time but does not drive after time has expired, a violation generally will not be reported. But, some violations can be reported even though the driver has stopped driving (e.g., Canada's Daily Off Duty rule which establishes a minimum off duty requirement, rather than a maximum driving or duty limit).

Violations are calculated only for Driving (D) statuses for which the end time is known. This is to prevent false reports in the case that a driver has stopped driving, but the driver's next status change has not yet been communicated to the web server.

What does the Allow multi-select checkbox do?

Checking the Allow multi-select checkbox changes the Log Events table so that a checkbox appears next to each editable event. Checking these checkboxes permits the Delete and Change CMV Number buttons to be used to take action on multiple events at one time.

What event types are listed in the Log Events table?

What information is displayed on the Log Events table for each event type?

What is a Sequence ID?

A Sequence ID is a number generated by an ELD at the time that an event is recorded. Sequence IDs start at zero for each device and increment with each event recorded; the host application also assigns a Sequence ID to events recorded or edited using the web site. Sequence IDs are used by FMCSA and Canadian authorities to determine the order of events on a log.

What is shown in the Conflicts column?

Most conflicts can be resolved by editing the event.

The Conflicts column lists all conflicts that have been detected for each event. If left unresolved, conflicts may cause the driver to be cited for log form and manner violations, or for exceeding the allowable hours of service. They may also prevent calculation of data such as Total Distance Driven Today which can affect payroll reporting.

Why might the Total Distance Driven Today not be equal to the sum of the values for the Distance Driven column in the log events table?

This can happen when the driver has recorded time as Off Duty, Personal Conveyance (PC). Distance traveled in this status is excluded from the total because it reflects the driver's personal use of the vehicle while relieved from work. The Distance Today values (for each CMV Power Unit Number and the daily total) are rounded down to the lower whole mile/kilometer as required by regulation. The Total Distance Today may also be higher than the sum of the Distance Today values for each CMV Power Unit Number due to rounding.

For example, if a driver operates “Vehicle 1” for 30.8 miles and “Vehicle 2” for 20.6 miles the Distance Today values would be calculated and display as follows:
Vehicle 1: 30.8 miles, rounded down to the nearest whole mile = 30 miles
Vehicle 2: 20.6 miles, rounded down to the nearest whole mile = 20 miles
Total Distance Today: 30.8 miles + 20.6 miles = 51.4 miles, rounded down to the nearest whole mile = 51 miles

Why is Distance Driven shown as 'Unknown' for some status changes in the table?

'Unknown' is shown when the end date and time of the Driving (D) or Off Duty, Personal Conveyance (OFF-PC) status is not yet known (the status is still 'open'), or when a start and/or end odometer has not been recorded for the status change.

Why does CMV Distance show values with 'Total' and 'Accumulated'?

ELD rules require recording and displaying Total Vehicle Distance (Odometer) for some events and Accumulated Vehicle Distance for other events.

Why does Engine Hours have values with 'Total' and 'Elapsed'?

ELD rules require recording and displaying Total Engine Hours for some events and Elapsed Engine Hours for other events.

Why do some events show 'Malfunction Detected' or 'Data Diagnostic Event Detected'?

ELD rules require the recording and display of the malfunction indicator status and data diagnostic event indicator status for Status Changes, Special Conditions Impacting Driving Time Events, and Intermediate Log Events. If an event is recorded while a Malfunction or Data Diagnostic Event is in effect, the event is marked accordingly. Run the Malfunctions and Diagnostics Report to determine the type of malfunction or diagnostic that is active and the cause for troubleshooting.

Why is 'Driver's time zone has changed' shown for this log?

This text indicates that the time zone of the log is different than the time zone of the log for the previous day.

This can occur when:

Why are some Active status changes listed in the table that do not appear in the graph grid?

This can occur when the driver's time zone has changed, particularly when a driver is reassigned to a home terminal one or more time zones to the west.

For example, suppose that Driver A is initially assigned to a home terminal in Eastern time zone. The driver operates a vehicle for two hours early this morning, between 12:30 AM Eastern and 2:30 AM Eastern. Some time later today, Driver A is reassigned to a terminal in Pacific time zone. When Driver A's log is converted to Pacific time, this two hour driving period will be shown as starting at 9:30 PM Pacific yesterday and ending at 11:30 PM Pacific yesterday. As a result, the entire driving period now begins and ends outside the 24 hour period reflected in either day's graph grid, even though it still appears in today's table.

Conversely, when a driver is reassigned to a home terminal one or more time zones to the east, this can cause status changes to appear both days' graphs and tables (that is, for the date prior to the reassignment as well as the date of the reassignment). If Driver B drove between 9:30 PM Pacific and 11:30 PM Pacific today, and today he is reassigned to a home terminal in Eastern time zone, that driving period will continue to appear in yesterday's driver log but will also now appear in today's driver log between 12:30 AM Eastern and 2:30 AM Eastern.

Because time worked and distance driven are calculated only for those statuses that occur from 12:00 AM through 11:59 PM, time zone changes can produce discrepancies between these totals (shown in the graph grid, vehicles, and other resources regions) and the sums of the values for all duty statuses listed in the Log Events table.

* To ensure that time and distance calculations are always correct, make sure that home terminal changes take place on a date when the driver is off duty.

Modifying log resources*

To add or remove co-drivers, trailers or shipments:

  1. View the log for the date for which you wish to modify resources.
  2. Click the "Edit" button located in the Vehicles and Other Resources region of the page. This displays the Log Resources page.
  3. Add or remove resources.
  4. Click the Done button to return to the Driver Logs page.

* Vehicles are associated with the driver log through duty status changes, and must be modified by changing the CMV Power Unit Number of log events on the Status Change page, or using the “Allow multi-select” option and Change CMV Number button to change multiple events at once.

Modifying log events*

Sometimes it is necessary for the driver or the driver's supervisor to make corrections to the events on a driver's log. In compliance with ELD regulations, the HOS application keeps a record of changes made to log events, including what information was changed, who made the change, and when the change was made.

When a driver makes a change to a log, the change becomes effective immediately. For example, when a driver deletes an event, the event is marked Inactive - Changed.

When a user who is not the driver makes a change to a log, the change is marked Inactive - Requested until it is reviewed by the driver; the driver may either accept or reject the change.

In some cases, edits can be avoided. Before you make any change, be sure that:

After you have verified the need to modify the active log events, keep these points in mind:

Adding a log event*

To add a new log event:

  1. View the log for the date for which you wish to add the event.
  2. Click the New Status Change, or New Exception button. This displays a separate page for the corresponding event.
  3. Enter the details for the event. Review all details carefully before saving.
  4. Click the Save button to add the event and return to the Driver Logs page.

Annotating a log event*

To annotate a log event:

  1. In the Log Events table, locate the row containing the event you wish to annotate.
  2. Click the Annotate button Annotate for the event.
  3. Enter the text of the annotation (up to 60 characters).
  4. Click the Submit button to save the annotation.

Editing a log event*

To edit an existing log event:

  1. In the Log Events table, click the Edit button Edit
    OR
    Click the link in the Status column for the Status Change, Remark, or Exception that you wish to edit. This displays a separate page for the corresponding event.
  2. Change the details for the event. Review all details carefully before saving.
  3. Click the Save button to save changes and return to the Driver Logs page.

Points to remember when editing an event:

Deleting a log event*

To delete one log event from the Driver Logs page:

  1. In the Log Events table, locate the row containing the event you wish to delete.
  2. Click the Delete button Delete for the event.
  3. Enter the reason for deletion. This reason will be recorded as an annotation to the event.
  4. Click the Submit button to delete the selected event.

To delete multiple log events from the Driver Logs page:

  1. Check the Allow multi-select checkbox.
  2. In the Log Events table, locate the row(s) containing the event(s) you wish to delete.
  3. Check the checkbox to the left of each row.
  4. Click the Delete button.
  5. Enter the reason for deletion. This reason will be recorded as an annotation to each selected event.
  6. Click the Submit button to delete the selected events.

Points to remember when deleting events:

Reassigning an automatic Driving event to a Co-Driver*

To reassign an automatic Driving status to a co-driver:

  1. Verify that the co-driver is listed in the log resources section and add them if necessary.
  2. In the Log Events table, locate the event that needs reassigned and click to view the event details.
  3. Use the drop-down selection for Reassign Co-driver to pick the co-driver the event should belong to. Reassign
  4. Enter a Reason for Change and click Save.

Points to remember when reassigning events:

Removing records mistakenly accepted from the unidentified driver*

To remove a Driving event the driver accepted from the unidentified driver profile in error:

  1. In the Log Events table, locate the Driving event that needs to be moved back to the unidentified driver profile.
  2. Click the Undo button. Undo
  3. Enter a Reason for Change and click Save.

Points to remember when reassigning events:

Certifying the log*

* Log certification is available only to drivers. Drivers may certify their logs on the ELD, or by logging in to the website and using the procedure described here.

Click the Certify... button and respond to the prompt to certify the log.

Certify...

A prompt will be shown and the Certify... button will not be available if you have not reviewed and accepted/rejected pending proposed edits.

Cannot certify - proposed edits must be accepted or rejected

The Certified label replaces the Certify... button when the log is certified.

Certified

You must recertify a log if any changes have been made after certification.

You may certify several days spent in an Off Duty (OFF) status at once if you have been in an Off Duty status for two or more full days in a row.

To certify multiple days spent in an Off Duty status at once:

  1. View the log for the last date on which you were Off Duty.
  2. Click the Certify... button.
  3. Click Agree on the prompt to certify all dates in the date range displayed.

Non-driver host users will be shown a warning notifying them that they are not permitted to edit the log if it has not been certified for the first time. This warning is dismissed after the driver certifies the log.

Warn

Note that this is not an indication of whether the log is still in a certified state. It is only a notification to the non-driver host user of why they are not permitted to edit the log. To verify if the log is still in a certified state, look for the Certified By details in the log header or run the Uncertified Logs Report.

CertBy

Why was I prompted about omitted required data elements when I certified my logs?

Canadian regulations require that the driver acknowledge and confirm that required data elements were omitted in the event record any time they certify their logs without a connection to the CMV's engine ECM.

Why can I view details for some status change events, but cannot edit them?

If the Edit button Edit does not display and the Status link is clickable, then you may only view details about that event and cannot edit it.

Reasons editing a status event may be disabled: