Who was driving? MetraFleet already knows.

Most fleets can tell you where a truck was at 2:14 on Tuesday. Far fewer can tell you who was driving it. Vehicles get swapped, a yard driver moves a unit, a new hire covers a route, and by the time a harsh-braking event or a speeding alert shows up, it is attached to a truck rather than a person.

That matters more than it sounds. Driver scorecards are only useful if the score belongs to the right driver. A coaching conversation built on someone else's event is worse than no conversation at all. And when a claim comes in, "it was our truck" is not the same answer as "it was this driver, and here is the footage."

The old fixes don't stick

Key fobs get left in the cab. ID cards get shared. Asking drivers to log in to an app at the start of every shift works for about a week. Each of these pushes the job of identification onto the driver, and every missed tap turns into an unassigned trip someone in the office has to clean up later.

The camera takes the picture. The cloud does the rest.

Your dash cameras already watch the cabin. When the ignition turns on, the camera takes a single still and sends it up. MetraFleet's cloud matches it against the drivers enrolled for your fleet. When it matches, the trip is assigned on the spot. Events, mileage, idle time, and the scorecard all follow that driver for the rest of the trip. When it can't match, nothing is guessed.

There is nothing for the driver to carry or remember. The only setup is enrollment: a driver adds their photos from the MetraFleet mobile app, with their consent recorded, and they are identified from the next key-on onward.

Why it runs in the cloud, not on the camera

Some cameras advertise face recognition on the device itself. It sounds tidy, and it is the wrong place for the job.

A camera that identifies drivers on its own has to hold its own list of faces. Add a driver and you enroll them on every truck they might ever step into. Let one go and you hope every camera gets the update. Swap a camera and the list goes with the old one. In a fleet where drivers move between vehicles, the list is wrong somewhere almost every day.

MetraFleet does the matching in the cloud. The camera's only job is the still at key-on, which is something every cabin-facing camera already does. That changes four things.

It works on every camera you own. VisionQube, CV200, CV5000, mixed fleets, older units: if it can see the cab, it can identify the driver. No special AI model, no second SKU.

One roster covers the whole fleet. Enroll a driver once and they are recognized in any vehicle, the same day. Remove them once and they are gone everywhere.

It gets better without touching the trucks. Matching runs on our side, so accuracy improves and new capability arrives without firmware updates, installer visits, or a camera generation.

You can see its work. Every identification keeps the still it was made from, so any trip shows the face it was matched on. A yes/no from a camera leaves you nothing to look at.

Built to be trusted

Identification is enabled per fleet, so it runs only where you turn it on. Enrollment photos belong to your fleet and are not shared across customers. The key-on still is stored with the trip alongside any event footage, so the record of who was driving is as durable as the video itself.

What changes

Scorecards become something drivers believe, because they reflect their own driving. Coaching gets specific. Claims get a name, a time, and a clip. And the office stops playing detective with the dispatch board.

Driver identification works with any MetraFleet dash camera that has a cabin-facing camera. If you already run cameras with us, ask about turning it on. If you don't, this is a good reason to.