Fleet deadlines
A missed STK or an expired PZP costs real money — this screen exists so that neither happens. Every open deadline of the whole fleet, ordered by urgency: overdue first, then everything inside its warning window, then the rest.
Two kinds of deadline
| Mode | Examples | Warns |
|---|---|---|
| By date | STK, EK, insurance, highway vignette | a configurable number of days ahead (default 30) |
| By odometer | service intervals | a configurable number of km ahead (default 1 000) |
Deadline kinds are your firm's own list — seeded with the Slovak defaults (STK, EK, PZP, havarijná, diaľničná známka, servisný interval) and editable like any vocabulary. A kind you don't use simply isn't created.
Warnings you cannot miss
An approaching or overdue deadline flags the vehicle everywhere: on the vehicle list, on its detail, and here on the overview. The vehicle's badge is always its worst open deadline.
Completing schedules the next one
Marking a deadline done records when (and at what odometer) it was completed — and when the kind repeats, the next occurrence is created automatically: STK passed in September 2026 with a 24-month period puts September 2028 on the list the same second. Completed occurrences stay as history; they never change and never delete.
Why an occurrence, not a recurring rule
Each row is one real obligation with its own due date and its own completion. That keeps the history honest — what was due, when it was actually done — instead of a rule that silently rewrites itself.