Reminders for upcoming and overdue checks
This article explains the automatic reminders MobilityManager sends for upcoming and overdue driver's licence checks, and how licence-class and CPC expiry reminders work alongside them.
Two reminder jobs run daily
The platform runs two background jobs once per day, each waking at 06:00 UTC and processing every active driver:
- The verification reminder job — warns about upcoming and overdue licence checks (the Führerscheinkontrolle cycle).
- The expiry reminder job — warns about individual licence classes and CPC certificates that are approaching their expiry date.
Note: Both jobs are restart-safe. They keep a per-driver send log, so a reminder is not sent twice on the same day even if the service restarts.
Upcoming verification reminders
For each active driver with a NextVerificationDueDate in the future, the job checks how many days remain against the configured verification reminder thresholds (default 30, 14, and 7 days). When the due date falls within a threshold, the driver receives a reminder. Only the single most relevant threshold is sent per day, so a driver is not flooded with duplicate notices.
Overdue verification escalation
When a driver's NextVerificationDueDate has already passed, the job records an overdue reminder for that driver and adds them to a consolidated escalation for the fleet manager. Instead of one message per driver, the manager receives a single summary listing every overdue driver and how many days each is overdue.
Licence-class and CPC expiry reminders
The expiry reminder job is separate from the verification cycle. It looks at the expiry dates you recorded on each licence class and at the CPC expiry date, and sends a reminder when the remaining days fall within an expiry threshold (default 90, 60, 30, 14, and 7 days). As with verification reminders, only the most relevant threshold is sent per class per day, and already-expired items are handled separately from the advance warnings.
| Reminder type | Triggered by | Default thresholds (days) |
|---|---|---|
| Verification due | NextVerificationDueDate approaching | 30, 14, 7 |
| Verification overdue | NextVerificationDueDate passed | Escalated to fleet manager |
| Licence-class expiry | A class's expiry date approaching | 90, 60, 30, 14, 7 |
| CPC expiry | CPC expiry date approaching | 90, 60, 30, 14, 7 |
Adjusting the thresholds
Both sets of thresholds are configurable on the driver-licence settings page, which requires the driverLicense:configure permission. Verification reminder thresholds must each be smaller than the verification cycle interval, otherwise the settings are rejected.
Tip: Keep accurate expiry dates on each licence class and the CPC fields — the expiry job relies entirely on those dates to decide when to warn.
Related
- Scheduling recurring checks and setting the interval
- Configuring the driver-licence module
- Recording the licence classes a driver holds
- Generating a compliance report
