Why are some trips showing as “Unknown Driver” even though the vehicle has a Driver ID Fob?

1. Multiple RFID tags on the driver’s key ring

If a driver carries several RFID tags together, the reader may detect the wrong tag. This can result in:

• The system picking up an unregistered tag
• The correct tag not being read at all
• Trips being logged without a valid driver assignment

Fix: Drivers should keep only one RFID tag on their key ring.

2. RFID tag stuck permanently to the reader

We've had reports that some drivers stick their RFID tag onto the reader to stop the buzzer. When this happens:

• The reader stops buzzing because it detects something
• But it does not register a proper “tap” event
• No valid driver assignment is recorded at the start of each trip

Fix: RFID tags must be presented at the start of each trip, not left attached.

3. Incorrect tag presentation

If the tag is waved too quickly, held at an angle, or removed before the confirmation beep, the system may not log the driver.

Fix: Hold the tag flat to the reader until the beep is heard.

4. The tag is unregistered or faulty

If the tag is not linked to a driver profile, or if it’s damaged, the system will not assign a driver.

Fix: Check the tag in the FleetConnect or test with another known-good tag.

Summary

Even with a Driver ID Fob installed, trips can show as Unknown Driver when:

• Multiple tags interfere
• A tag is stuck to the reader
• The tag isn’t presented correctly
• The tag is unregistered or faulty

Ensuring drivers use one tag, present it properly, and don’t leave it attached will prevent almost all Unknown Driver trips.