Driver Identification Methods

Abstract 

The Motive platform offers multiple driver identification methods to ensure the correct driver is assigned to a vehicle, improving safety, compliance, and productivity. It helps eliminate unassigned trips and ensures accurate data across the Motive platform.

Overview

Identifying the driver behind each wheel is essential for managing your fleet efficiently. Motive’s driver identification features provide various methods to quickly and accurately identify drivers, reducing unassigned trips and saving time. This improves accountability, supports accurate safety coaching, compliance reporting, and operational analysis.

1. Improve safety and accountability: Link driving behavior and safety events to the correct driver for effective coaching and investigation.
2. Enhance compliance: Reduce log errors and ensure hours of service (HOS) records are accurate.
3. Increase productivity: Minimize time spent assigning unassigned trips and resolving log issues.
4. Strengthen security: Prevent unauthorized vehicle use by ensuring every trip has an identified driver.

Understanding driver identification methods

You can use one method or combine multiple options to match your fleet’s operations.

Driver App

Drivers select their vehicle in the Motive Driver App, which connects to the Vehicle Gateway via Bluetooth. This method automatically links trip data to the driver. If a driver forgets to connect, the app suggests the likely driver based on past trip data. This method is recommended for fleets that follow ELD regulations.

Face Match

Using a dual-facing AI Dashcam (DC-54), this feature identifies the driver through facial recognition. It helps with coaching and incident reviews, and for ELD-regulated drivers, it sends suggested trip assignments for approval.

ID Reader

Drivers tap their ID card on the Motive ID Reader to identify themselves. This method is quick and passcode-free. Alerts can be set when a driver forgets to scan their ID.

Manual assignment

Authorized users can manually assign unclaimed trips in the Trips page of the Motive Dashboard. For ELD drivers, log suggestions must be approved in the Driver App.

Static pairing

A driver can be permanently assigned to a vehicle. This is best for fleets where one driver always uses the same vehicle, such as owner-operators. This is not recommended for slip-seat fleets or ELD-regulated drivers.

Integrations

If your fleet uses platforms like Geotab or Platform Science, driver information can be sent through API and automatically linked to trip data in the Motive platform.  

Choosing a driver identification method

The best driver identification method depends on your fleet’s operations, hardware, and compliance needs.

• To maintain HOS and ELD compliance: Use the Driver App as the primary method to ensure proper log certification. Add Face Match to automatically generate log suggestions for approval.
• The hardware you have:
  • Dual-facing AI Dashcam (DC-54): Required for Face Match
  • ID Reader: Required for the ID Reader method.
  • No dashcam or ID Reader hardware: Use the Driver App or Static Pairing.
• The drivers’ behavior and operations:
  • Use Face Match or ID Reader if drivers don’t reliably use the Driver App
  • Choose static pairing for drivers assigned to a specific vehicle.
  • Avoid static pairing for slip-seat operations.

Example scenarios:

Dedicated long-haul driver with AI Dashcam

For a driver who consistently uses the same truck, combine static pairing and Face Match for reliable, automated identification.

Local delivery fleet with slip-seating

For operations where drivers change vehicles daily, use the Driver App with Face Match or ID Reader to ensure each trip is properly attributed.

Exempt fleet without mobile devices

For fleets not subject to ELD regulations, use ID Reader for fast driver identification.

Using Driver Walkthroughs to improve identification

To reduce unassigned trips, use Driver Walkthroughs to prompt identification steps. For example, a Beginning of Day walkthrough can include actions like Connect to Vehicle and Update Log Form, ensuring drivers are properly identified at the start of each shift.

FAQs

Troubleshooting

• Not connecting to Vehicle Gateway  
• Unassigned trips are not being identified  
• Face Match not identifying driver correctly  
• RFID Reader not working  
• Driver logs have errors after trip assignment