Viewing a driver's verification history
This article explains the verification history for a driver — the immutable audit trail of every licence check — and how to read and use it for compliance.
What the verification history is
Every time a licence check is completed for a driver, the platform writes a permanent audit entry. The verification history is the full list of those entries for a single driver, showing each accepted or rejected check, who performed it, and when. Because entries are immutable, the history is a reliable record you can rely on during an audit.
Who can view it
Viewing a driver's verification history requires the driverLicense:manage permission, held by the FleetManager and SystemAdmin roles. Drivers can see their own current verification status but not the full historical audit trail.
Reading a history entry
Entries are listed newest first. Each one contains:
| Field | Meaning |
|---|---|
| Timestamp | When the check was recorded. |
| Outcome | Accepted or Rejected. |
| Verifier | The user who performed the check. |
| Verified licence classes | For accepted checks, the classes that were confirmed. |
| Rejection reason | For rejected checks, why it was rejected. |
| Front / back documents | References to the licence images reviewed, when the check came from an upload. |
| Verification request | The request the entry belongs to. |
What produces an entry
- Accepting an uploaded licence — creates an Accepted entry with the confirmed classes and the reviewed document references.
- Rejecting an uploaded licence — creates a Rejected entry that records the reason.
- Recording a manual check — creates an Accepted entry with the confirmed classes and no documents, reflecting an in-person inspection.
Note: Accepted checks (including manual checks) advance the driver's LastVerifiedAt and NextVerificationDueDate. Rejections are recorded in the history but do not move those dates, so the driver stays due until an accepted check is recorded.
Using the history
- Confirm when a driver was last successfully verified and by whom.
- Review why past submissions were rejected before processing a new one.
- Provide an evidence trail during an internal or external compliance audit.
Tip: Pair the per-driver history with the fleet-wide compliance report when preparing an audit — the report shows overall coverage and overdue counts, while the history proves the detail for any individual driver.
Related
- Performing a verification: accept, reject, or manual check
- Generating a compliance report
- Uploading a driving licence for verification
- Scheduling recurring checks and setting the interval
