What the Führerscheinkontrolle is and why it is required

This article explains what the Führerscheinkontrolle (driver's licence check) in MobilityManager is, why it is required, and how a check moves through the system from upload to a confirmed result.

What the Führerscheinkontrolle is

The Führerscheinkontrolle is the process of confirming that a driver still holds a valid driving licence for the vehicles they operate. In MobilityManager it is a structured, repeatable check: a driver's licence is presented (as scanned documents or during a physical inspection), a fleet manager confirms the licence classes held, and the platform records the result and schedules the next check automatically.

Each driver has a driver-licence profile (Fahrerakte) that stores the licence number, issuing country, the licence classes held, any professional-driver CPC (Certificate of Professional Competence) dates, probation (Probezeit) information, and two verification dates: LastVerifiedAt (when the licence was last confirmed) and NextVerificationDueDate (when the next check is due).

Why it is required

Employers who let staff drive company vehicles carry a duty of care to confirm that each driver is licensed for the vehicle they use. Letting an unlicensed or expired driver operate a vehicle exposes the organisation to liability. The Führerscheinkontrolle turns that duty into an auditable, recurring workflow so you can demonstrate, at any time, that every active driver was checked and when.

How a check works end to end

1. A driving licence is uploaded for verification (front and back images), which creates a verification request with the status Pending.
2. A fleet manager reviews the request from the verification queue and either accepts it (confirming the licence classes) or rejects it with a reason.
3. On acceptance, the platform stamps LastVerifiedAt with the review time and sets NextVerificationDueDate to that time plus the configured verification cycle interval (180 days by default).
4. An immutable audit entry is written so the outcome, verifier, and confirmed classes are preserved for compliance.

A manager can also record a manual check (a physical, in-person inspection) without uploading documents. That produces the same confirmed result and updates the same dates.

What the module tracks

• The licence classes a driver holds, each with its own issue date, expiry date, and any EU restriction codes.
• CPC issue and expiry dates for professional drivers.
• Probationary status and the probation end date.
• The verification status (None, Pending, Accepted, or Rejected) and the two verification dates that drive reminders and reports.

Module licensing

The verification workflow is part of the licensed Führerscheinkontrolle module and is gated by the EnableFuehrerscheinkontrolle feature flag on your tenant's licence. When the module is disabled, verification endpoints return a LICENSE_CAPABILITY_DISABLED error. The base driver-licence data (profiles, licence classes, and the compliance dashboard) remains available even without the module.

Note: Viewing your own licence profile requires the driverLicense:view permission, which drivers hold by default. Reviewing and confirming other drivers' licences requires the FleetManager or SystemAdmin role.

Related

• Uploading a driving licence for verification
• Performing a verification: accept, reject, or manual check
• Who can upload versus who can verify licences
• Recording the licence classes a driver holds