The existing HOS logs page provided basic driver duty status data, but little else. Over time, various links were added to access different pages, which made the experience feel less cohesive. For many ELD compliance users, this page was as essential as the Map feature, so enhancing it became a top priority. Several issues were addressed with this change:

• Consolidating Information: Bringing key data together so users wouldn’t have to open multiple tabs.
• Preparing for Future Needs: Creating a foundation on which more features could be built.

Because the old HOS logs page had accumulated significant technical debt, building a new page was more practical than trying to update the existing one. Although this new Driver Logs page is eventually intended to replace the HOS logs page, it is still in beta and won’t fully replace the old page during this period. A migration plan will be determined later.

A new page was developed in MyGeotab with two main sections: -Driver Logs Overview - This fleet-wide view offers the ability to filter by the drivers a user is interested in. It gives a quick look at driver logs—including a graph view—right on the page, reducing the need to switch to other areas.

• Driver Logs Details - For those who need more in-depth information, this section displays items such as violations, availability, time spent in different statuses, co-driver details, and more.

This approach offered a more comprehensive way to view and manage driver log data while laying the groundwork for further enhancements in the future.

• Compliance teams observed a decrease in time spent troubleshooting or determining edits for specific drivers, and the overview page helped surface issues requiring attention. The long-term plan was to develop this page into a hub for managing tasks.
• The UI and user experience for viewing driver log data were updated to reduce the need for opening multiple tabs or pages to find relevant information for editing duty status logs.
• A new overview page offers an at-a-glance summary of drivers on a single screen, removing the need to navigate between different sections.

Rather than a blank state, landing on the driver logs page gives you a default overview of your drivers along with their current status. You can also filter by Group, Driver, Ruleset, and Driver status

Clicking on the icon will provide you a graph view for the individual driver for each day You can filter by the last 7, 8 or 14 days Hovering over the graph gives you more details as to how long the driver was in that status. It will also show you the same information if the status continued from a previous day.

Show logs opens up a table view of the log status for that day

Driver information gives you all the necessary information around the driver and their current availability

Clicking on Show details gives you more information about the individual log day.

• Totals - View the distance driven and time spent driving, as well as resting time
• Cycle recaps - how much time they spent each day against their cycle.
• Assets and Co-drivers - All associated assets (vehicles, trailers, shipments) and co-drivers with the log

Violations will be clearly indicated in a red warning sign which can be viewed under Show details

Some users will notice that the new workflow begins on an overview page instead of a blank page to set your options, which changes the steps they were used to. Previously, they searched for a specific driver on the HOS logs page and viewed detailed data. In the new approach, they start with a fleet-wide overview (based on group scope) to see driver data at a higher level.

Possible scenarios:

• Unexpected Navigation: Those who routinely began on the HOS logs page might initially be unsure about where to find detailed driver information.
• Maintaining Access to Detailed Data: Despite the new starting point, users could still drill down into individual driver information in a way similar to the old process.
• New Insights: By seeing an at-a-glance view of all drivers, users could spot patterns or issues they might have missed when focusing on a single driver’s page.