Skip to main content
Monitor Driver Log Compliance

Uncertified logs, proposed edits, violations, outstanding edits

Updated over a week ago

An easy way to ensure that all driver logs are in compliance is to use the Driver > Driver Hours/ELD > Log Filter dropdown.

Filter the log list to investigate driver logs that are uncertified, and have edits that need closing/verification, outstanding unidentified driving time, and HOS violations. Double click a log to view log details.

In particular:

Rejected Edits: Displays driver logs that include rejected edits. Double click on a log to see the daily log details. The rejected edit displays with a red dot. Given that red dots may indicate violations, hover over a red dot to confirm the status.

Proposed Edits: Displays driver logs that include proposed edits that drivers have not accepted or rejected yet, as denoted by a yellow dot in the daily log details. Hovering over the dot indicates that the change is pending approval. To cancel an edit, select the X.

Proposed Unidentified: These are subset of proposed edits and also appear with a yellow dot and X, as shown above, when drivers have not accepted or rejected them yet.

Driver Edited: You may want to check on logs that include events edited by drivers. In the daily log details, double click an event with an orange dot to read the remark (Annotation) that the driver left as explanation for the change.

On some entries, you may see a + next to the orange dot. Select the + to expand the list. The + indicates a change in duty status. Since Drive does not delete events, you see the previous duty status that is now inactive.

View Driver Log Changes Made by Drivers

On a driver log, the Show All Events option expands the event list to show all log events. Select it so you can see when drivers changed their logs, such as when they changed rulesets or enabled the 16-hour exemption.


โ€‹


โ€‹

Did this answer your question?