Report odometer
With a plausibility check against the last known reading — implausible values stand out immediately.
Odometer reading, seasonal tyre change, damage report with photos, and fuel or charging receipt: drivers submit from the portal, fleet management accepts, asks back or rejects.
Every submission follows the same pattern: the driver submits, the report lands in the matching review queue, and only on acceptance does a real fleet record appear — an odometer reading, a damage case, a receipt. Data quality improves without administration chasing every driver.
With a plausibility check against the last known reading — implausible values stand out immediately.
Document seasonal changes including odometer — the basis for tyre set and storage records.
With photo documentation straight from the phone. An accepted report becomes a case in damage management.
Including home charging: for home charging the system applies the flat rates configured per year.
Four queues with accept, reject with reason and request for clarification. A counter in the navigation shows what is open.
Where a ride is ordered rather than self-driven, a structured order form hangs off the booking request: department, departure location, travel purpose, contact and room, times, passengers, chauffeur or self-drive. Enabled per tenant.
Every field label of the driving-service order can be renamed tenant-wide — in German and English, addressed by field name. An empty label restores the shipped default. Departments, departure locations and travel purposes are catalogues of their own.
Reporting rights are separate permissions and can be granted independently of any administrative rights.
No. Submissions run in the browser on a phone — nothing to install, distribute or clear through an app store. That matters especially in public-sector environments.
Fleet management can reject it with a reason or ask for clarification. The driver sees status and questions under 'My submissions' and can cancel a submission themselves as long as it has not been accepted.
Only on acceptance. Until then the submission is a proposal; once accepted it becomes the vehicle's odometer reading, with its source recorded.
That is what the driving-service order is for: a form on the booking request with department, travel purpose, departure and return time, destination address and passengers. It can be edited in four places — the driver portal, the booking detail page, the booking overview and the request queue. Who may correct it is decided by the server: the driving service at any time, the requesting driver only while the request is still unassigned.
Drivers as master records rather than shadows of a user account — with credentials, blocking and a 360-degree view.
Tyre sets, tread measurements per wheel position, two thresholds and the seasonal change campaign.
Damage cases from report to settlement — with liability classification, deadlines and costs.
On-site tanks, refuellings, fuel cards, fuel prices and budgets with consumption analytics.
30 minutes, no sales pressure: we show the module in the context of your fleet — self-hosted in your data centre, GDPR-compliant, made in Germany.