Booking wizard for drivers
Pick period, purpose and vehicle or pool — with live availability and odometer capture at handover and return.
Core platform
Bookings & dispatch board
A booking wizard walks staff through period, purpose and vehicle choice — they only ever see what they are actually allowed to drive from their pools. Dispatchers do not work in that same form: they work on a board covering the whole fleet.
Assignment strategiesLeastUtilized · LowestCost
Dispatch boardDrag-and-drop · series · colours
Series lengthUp to 43 occurrences
Users & driversUnlimited
Employees book themselves. Dispatchers plan on a board.
The booking module replaces key-cabinet lists, shared Outlook calendars and shouting across the office. Bookings run a complete status chain, approvals are switchable per tenant, and the system can pick the vehicle itself — balancing utilization or minimizing cost. Dispatch gets the same data as a board: one row per vehicle, one bar per appointment, moved with the mouse.
What it does
What the module actually does
Approval workflow
Switchable per tenant. Approvers get their own queue with a counter in the navigation; approving your own booking is blocked by the system.
Automatic vehicle assignment
'LeastUtilized' spreads wear evenly, 'LowestCost' minimizes cost per kilometre. Simultaneous requests are resolved conflict-free with retry logic.
Vehicle pools & driver access
Group vehicles by department, location or type. Drivers only see and book pools they are explicitly assigned to.
Dispatch board across the fleet
One row per vehicle, one bar per appointment: gaps, overlaps and idle vehicles at a glance. Time raster, sub-divisions and a working-hours-only view are each dispatcher's own setting.
Move with the mouse instead of re-entering
Drag a booking onto another vehicle or another slot. The board can ask before every move, and conflicts with the driver, the vehicle or a trailer are named rather than silently created.
Group and hide
Group the board by pool, brand, model or body type. Hide what is not relevant today — a dedicated list always says which vehicles are missing and why: no pool, still planned, retired, in the workshop.
Colour categories instead of notes in the subject
Your own colour categories per tenant, plus a free colour per appointment. A category still in use is retired rather than deleted — existing bookings keep their colour.
Recurring series, all or nothing
Recurring trips are created as a series — up to 43 occurrences, and only if every single one is free. Editing and cancelling ask whether you mean this occurrence or the whole series.
Trailers travel with the tour
A trailer gets its own appointment on its own row but stays attached to the main one: move the tour and the trailer moves with it.
Order data on the appointment itself
Subject, destination, order number, cost centre, project and start/end odometer are all in the booking dialog. If a driver is missing, a short driver file is created straight from it.
Vehicle briefing without a context switch
For every vehicle the board shows the next roadworthiness test, the odometer, lease utilization and this month's dispatch utilization — without opening the vehicle file.
Workshop and inspection slots as blocked time
Appointments without a reservation — workshop, inspection, blocked periods — appear on the same board but stay read-only there: they are edited in the vehicle file, where they originate.
Requests without a specific vehicle
Staff can register a need without knowing a particular vehicle; dispatch assigns and confirms.
Your own driver-portal rules
Visible and mandatory fields, lead and cancellation times, the booking horizon, a charging buffer after every EV booking, ride sharing and hiding lease vehicles that are already over their mileage — all configured per tenant, no code change involved.
Workflow
Booking status
- 01Created
- 02Pending approval
- 03Confirmed
- 04In progress
- 05Completed
Frequently asked questions
Yes. The approval step is configured per tenant. Without it a booking is confirmed immediately; with it the booking lands in the queue of the authorized role.
With the driving licence control module, yes. Vehicles and models carry a licence requirement; at booking time the system checks the driver's recorded licence classes and verification status.
Unlimited. MobilityManager is licensed per vehicle, not per user — drivers, approvers and administrators cost no extra fees.
No. The board and the booking wizard are the same module on the same data — two surfaces for two roles. A dispatcher needs the right to see and manage all bookings; a driver still only sees their own.
There is a dedicated list for exactly that. It names the reason per vehicle: not assigned to a pool, still planned, retired, in the workshop, stolen, being sold — or simply hidden by your own board settings. Vehicles outside your site-based data scope are only counted, never named.
Works together with
Driving licence control
Licence data, recurring visual checks, a review queue and a booking block when the required class is missing.
Driver file
Drivers as master records rather than shadows of a user account — with credentials, blocking and a 360-degree view.
Driver submissions
Drivers report odometer, tyre change, damage and fuel receipts themselves — administration just reviews.
Reports & analytics
A report hub with 34 reports, one shared export layer and per-vehicle KPIs.
See this module with your own data
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.