Scheduling recurring checks and setting the interval

This article explains how MobilityManager schedules recurring driver's licence checks, how the verification cycle interval works, and how to bring every active driver due for a check at once.

How the recurring schedule works

Each driver-licence profile carries a NextVerificationDueDate. When a fleet manager accepts an uploaded licence or records a manual check, the platform sets LastVerifiedAt to the review time and calculates the next due date as that time plus the verification cycle interval. The driver then stays compliant until that date, when the next check becomes due.

Setting the verification cycle interval

The interval is the VerificationCycleIntervalDays setting on the driver-licence settings page. Changing it requires the driverLicense:configure permission (FleetManager or SystemAdmin).

• The default interval is 180 days, applied whenever no explicit interval is configured.
• Valid values range from 30 to 730 days; values outside that range are rejected.

Note: Changing the interval affects future calculations only. Drivers verified before the change keep the due date they were given at that time; their new interval applies from their next accepted check.

Choosing an interval

A shorter interval (for example 90 days) means more frequent checks and stronger assurance but more administrative load; a longer interval (up to 730 days) reduces the workload. Pick the interval that matches your organisation's driver-safety policy.

Bringing everyone due at once

You can force a verification cycle so that every active driver becomes due immediately. This is useful for an annual audit or when you first roll out the module. Triggering a cycle requires the licenseVerification:verify permission.

1. Trigger the verification cycle from the Führerscheinkontrolle module.
2. Every active driver's NextVerificationDueDate is set to today, marking them due.
3. Drivers who already have a Pending verification request are left untouched, so an in-progress review is not disrupted.

Warning: Triggering a cycle makes all eligible active drivers overdue for their next check on the same day, which will generate reminders and populate the overdue lists. Use it deliberately.

How the schedule connects to reminders and reports

• The daily reminder job reads NextVerificationDueDate to warn drivers before a check is due and to escalate overdue drivers to fleet managers.
• The compliance dashboard and report count drivers whose next due date has passed as overdue.

Tip: Set the verification reminder thresholds to values smaller than the cycle interval so drivers receive advance warning within a single cycle. The settings page enforces this rule.

Related

• Reminders for upcoming and overdue checks
• Configuring the driver-licence module
• Performing a verification: accept, reject, or manual check
• Generating a compliance report