If you are finding that there appears to be a discrepency between the count summary displayed in the Uncertified Logs Report and Uncertified Log Summary box on the home screen of the HOS Admin Portal for a driver’s count of uncertified logs, please use the following information to alleviate any confusion.
When is a log certified?
On a driver log, the bar that states “This log has not been certified; you may annotate but cannot edit this log” disappears when the driver first certifies the log.
The absence of the bar does NOT mean the log is certified.
When a driver first certifies a log, the log becomes available for your edits or corrections (as an HOS Admin). If you make any edits or updates to the log after the initial driver certification, the log reverts to an uncertified status. The driver is then required to review the log again, accept/reject edits or corrections, and then re-certify the log.
Therefore, if your HOS Admin Portal is showing Uncertified Logs for drivers after their initial certification of the log (which removes the initial Purple dialogue box that displays “This log has not been certified […]”), it means either edits were made/requested or there are still pending conflicts that need to be corrected.
Accepted/Rejected Changes Processed
Once the driver accepts/rejects suggested edits/corrections (via the tablet or the Driver Portal), the driver must re-certify the log.
We recommend that drivers certify their log from the previous day on the following morning (either via the tablet or Driver Portal). Though the FMCSA recommends that drivers certify logs at the end of the day, the last Off-Duty status is an open status. Thus, when a driver signs into the tablet the following morning, the Off Duty event that started from the previous day’s log is updated to show the ending time of that Off-Duty status. This change to the log would result in a status change from certified to uncertified, and the log would show as an uncertified log the following day (granted that there are no conflicts or edits added).
Certifying Multiple Logs in the Driver Portal
Logs can be certified in chunks ONLY if the driver had been off for multiple days. Below is an example of the Portal screen when a driver has multiple logs to certify.
If a driver is showing X amount of Logs Uncertified, have the driver work backward from the current date to certify logs. In the example above, the driver has 30+ logs uncertified (Current day is 10/3). The driver should begin with the previous day’s log (10/2 in the example above) and certify all applicable logs via the tablet or Driver Portal.
After certifying all applicable logs, the HOS Admin Portal displays the updated count of uncertified logs. In the HOS Admin Portal example below, the Portal now displays a count of 0 for this driver’s uncertified logs as the driver has certified logs prior to 10/2 in a chunk.
If drivers require instructions on logging into the Driver Portal, please refer drivers to Exploring the Driver Portal.
If you continue to experience any issues regarding the count summary displayed in the Uncertified Logs Report and Uncertified Log Summary box on the home screen of the HOS Admin Portal for a driver’s count of uncertified logs, please contact HOS Support .