Compliance as a single answer
A vehicle is either compliant or it is not, and the answer comes from three sources read together: the statutory expiries on the vehicle record (technical inspection, insurance, road tax), the vault documents that carry their own expiry, and odometer anomalies.
A rolled-back odometer shows up here rather than in a data-quality report, because it is a compliance problem, not a curiosity.
Servicing and tyres on the same screen
Both answer the same question — "what does this car need next?" — so they share a page instead of hiding tyres one tab deeper. The seasonal swap is the single most frequent fleet action in a Romanian winter; it does not deserve to be hard to find.
Maintenance plans are defined per vehicle, due by distance or by time.
Trip sheets and technical data
Trip sheets are filled in per vehicle and printed. Technical data — rated consumption, capacity, category — lives under fleet rather than transport, because it describes the vehicle and not the journey: a company with two vans and no freight operation still needs it for fuel VAT.
Cost and history per vehicle
Every vehicle carries its own costs, its own history and its own report. Fleet analytics show where the money goes — which car, which category — rather than only a monthly total.
Drivers have their own records, with their documents and assignments.
Worth knowing
A fine or an uncovered claim rarely comes from a bad decision; it comes from a date that passed unnoticed. That is why "what lapses next" is the question the module is built around, rather than a report you must remember to run.