Fleetly
Client LoginGet PricingBook a Demo
Insight · Operations

Driver identity is an audit trail, not just a name

Resolve overlapping assignments from cards, apps, integrations and manual changes.

Keep the source

A tachograph card, RFID token, mobile sign-in and manual assignment have different evidence behind them. Retain the identity source, the recorded time, effective start and end, vehicle and person who made a change.

Resolve conflicts predictably

Agree source priority and rules for overlapping assignments. An unresolved conflict should remain visible for review rather than silently overwriting earlier history. Keep raw evidence separate from the resolved assignment used by reporting.

Correct with accountability

When an authorised user corrects an assignment, capture a reason and preserve the previous value. Re-evaluate affected journeys and events consistently so managers do not see different drivers in different screens.

Review exceptions

Use a regular queue for unknown tokens, unmapped faces, missing sign-outs and concurrent assignments. Limit identity access to roles that need it and agree retention with your organisation’s data owner.

PUT IT INTO PRACTICE

Your action checklist

  • Define source priority
  • Keep effective and recorded timestamps
  • Review unresolved identity conflicts

Product availability depends on your devices, integrations, permissions and enabled modules. Confirm your organisation’s configuration before implementation.