Fleet Driver Identification: How It Works in 2026

Shared and pool vehicles create a blind spot for fleet managers: if nobody logs who drove where, journey data becomes almost useless for maintenance scheduling, fuel accountability or answering an insurer's questions after an incident. Fleet driver identification closes that gap by matching each journey to a specific person, not just a vehicle registration.

Why this matters

Shared vehicles change hands several times a day: pool cars for site visits, vans handed between shifts, HGVs shared across a depot rota. Without driver identification, tracking data only tells you where a vehicle went, not who was behind the wheel when it happened.

That gap matters when you're reconciling fuel card spend, scheduling a service against the driver who has been logging the most miles, or explaining to an insurer why a vehicle registered to twelve different names needs a single answer. Fleets already using SmartCam 4G for shared and pool vehicles know the video side of this problem well. Driver identification is the other half: confirming who was driving before anyone even looks at footage.

In 2026, more SMEs and local authorities are running pool car and shared van schemes to cut fleet size, which makes driver-level accountability harder to skip.

How fleet driver identification works for shared vehicles

The process is consistent across most systems that use it, including Crystal Ball's FleetTracker:

1. Each driver carries a small identifier, commonly a fob or key tag, registered to their name in the fleet management portal.
2. At ignition, the vehicle's tracking unit reads the identifier and checks it against the registered driver list.
3. The system logs that driver against the journey, alongside location, mileage and time data for the trip.
4. If no identifier is presented, or one the system doesn't recognise, the vehicle can usually still start, but the journey is flagged as unassigned.
5. Reports then group journeys, mileage and driver behaviour data by person, even though the vehicle itself changed hands several times that week.

Getting this right starts with clean records. Most fleets treat identifier issuing as part of onboarding drivers onto a new tracking system rather than a separate admin task bolted on afterwards.

Why driver identification results vary across shared fleets

Two fleets running the same technology can get very different results. The outcome depends on a handful of factors:

• Identifier discipline: whether drivers actually tap or scan before starting the engine, every time, not just when it's convenient.
• Booking systems: whether a separate pool car booking log is cross-checked against the identification data, or the two run in isolation.
• Vehicle rotation frequency: a van shared across three shifts a day generates more unassigned-journey risk than one driven by the same person all week.
• Multi-site sharing: vehicles moved between depots or sites need identifiers that work everywhere, not just at the home base.
• Alert review habits: unrecognised-fob alerts only help if someone actually checks them, cross-referencing against journey history data rather than letting them pile up.
• Driver turnover: temporary or agency drivers who haven't been registered yet are the most common source of unassigned journeys.

Fleets that treat this as a one-off setup task rather than an ongoing process tend to see identification data degrade within a few months, as new starters and agency cover slip through the registration process.

Does driver identification work without a fob?

Driver identification without a fob or equivalent identifier cannot tell you who drove a shared vehicle, only that it moved between two points. Some businesses rely on manual sign-out sheets alongside GPS data as a workaround, but that depends entirely on drivers filling the sheet in correctly, which is exactly the accountability problem driver identification is meant to solve.

Can driver identification stop unauthorised use of a shared vehicle?

Driver identification on its own does not stop a vehicle starting. It flags the journey as unassigned so a manager can review it afterwards, rather than preventing the trip in the first place. Fleets that need the vehicle disabled when no authorised driver is present are looking at a different function: Thatcham S5 Plus adds immobilisation when its fob is absent, which is a security feature rather than a fleet identification one.

How is driver identification different from GPS vehicle tracking?

GPS vehicle tracking shows where a vehicle is and where it has been. Driver identification adds who was driving during that journey, which turns a location record into an accountable one. For pool and shared vehicle setups, the two work together: tracking supplies the route and timing, identification supplies the name attached to it. Businesses running formal pool schemes often pair this with pool car scheme fleet software that handles bookings alongside the identification data.

Where Crystal Ball fits

FleetTracker is the simplest fit for shared fleets that need driver-level reporting without camera evidence: Automatic Driver Recognition (ADR) logs which driver used which vehicle, on top of the location, mileage and reporting functions already built into the platform. Where disputes or incidents are a bigger concern, such as pool cars used by multiple departments, SmartCam 4G adds recorded video evidence to the same driver identification data, accessed on demand through the customer portal rather than as a live stream.

Neither product replaces the other. FleetTracker handles the identification and reporting layer; SmartCam 4G adds the visual record when a journey needs more than a name attached to it.

FAQ

One last thing

The biggest failure point in fleet driver identification isn't the hardware, it's the review habit. A fob system that logs every unassigned journey is only useful if someone actually checks that report; set it as a fixed weekly task rather than something you glance at after a problem has already surfaced. Fleets that do this in 2026 catch registration gaps, like a new agency driver who hasn't been set up yet, within days rather than after the next audit.

Request a demo to see how FleetTracker’s Automatic Driver Recognition (ADR) works for a shared or pool fleet.

Related guides

• How journey history supports fleet operations
• How FleetTracker measures vehicle utilisation