Due tracking
How a due point works, from interval definition to the nightly notification
A fleet manager opens an oil change reminder for a vehicle and enters both an odometer interval and a time interval. The system calculates the due point from the vehicle's current odometer and last service date; whichever comes first is used. For a vehicle working in the city, months usually come first; on long hauls, km does. As the odometer advances through fuel, service and inspection records, the due point is recalculated. When the threshold is reached the item becomes Due Soon, and when the due point passes it becomes Overdue and triggers a nightly notification. The notification goes to the reminder's watchers; if there are none, to the vehicle's watchers; and if there are none, to managers. When the job is closed, the reminder advances. In the list you can turn on the Vehicle Type, Make / Model, Model Year and Group columns with โ and filter by the same fields. For older records whose reminders are out of date, there's an 'Update from service records' button.
Dual interval. Km and months are defined together; whichever comes first is the due point, so you don't need to track the two separately.
Three statuses. Overdue, Due Soon and Scheduled appear separately in the list; overdue and due-soon items generate nightly notifications.
Notification chain. If a reminder has no watchers, the vehicle's watchers are notified, and if there are none, organization managers; you can choose the watcher yourself.
Vehicle owner. Making a vehicle's owner a watcher sends due notifications straight to the person following the job, instead of to managers.

