Fleet

The fleet agenda keeps the firm's vehicles in one place: who drives what, what it cost, what was done to it, and — most importantly — what is about to expire. It replaces the spreadsheet that every firm with three cars keeps somewhere, and the calendar reminder that somebody forgot to set.

The vehicle register

A vehicle carries a name, its licence plate, VIN, a type, a fuel, the year and the current odometer reading. Types and fuels come from your firm's own lists (seeded with sensible defaults, editable in the taxonomy back office) — no other firm sees your lists, and you never see theirs.

The plate names one active vehicle at a time. A retired vehicle keeps its historical plate without blocking the car that inherited it.

Drivers

A vehicle can be assigned to an employee. Reassigning ends the previous assignment and keeps it in the history — the register always answers who had the car in March. Assignment is a default, not a lock: pool vehicles are the normal case, so any colleague with the fleet permission can record a trip with any active vehicle.

The odometer only moves forward

Every trip, fuel purchase and service record carries an odometer reading, and the vehicle's clock advances with the highest one. It never silently goes backwards.

Retire, don't delete

A vehicle with any history refuses to be deleted — the trip log written with it must survive the vehicle. Retire hides it from every pick list and keeps its file readable. Only a freshly created, empty vehicle can be deleted outright.

Notes and history

The vehicle detail carries the platform activity trail and append-only notes — every change with its actor and time, plus whatever the drivers want the next driver to know ("zimné gumy sú v pivnici").

Permissions

Everything is scoped to the organization open in the toolbar; no fleet data ever crosses between firms.