Employee transport management: how it works and what to measure
How employee transport management works, who does what, and the seven measures that show whether a staff transport contract is running well.
Employee transport management is the work of getting staff to and from a workplace safely and on time, usually under a contract between an employer and a transport operator. The work repeats every shift, which makes it easy to run badly without noticing and hard to prove you ran it well. This guide describes how it works and what to measure.
How an employee transport operation works
There are three parties. The employer defines who is entitled to transport, from where, and at what times. The operator supplies vehicles and drivers, and is accountable for punctuality, safety and compliance. The employees ride, and are the first to notice when something goes wrong.
Day to day, the operator receives pickup requests or a standing schedule, assigns vehicles and drivers to each shift's pickups, follows the trips, handles exceptions such as no-shows and breakdowns, and at month end bills the employer against the contract. Software helps at each step, but the order of work stays the same.
The seven measures that matter
A contract that is measured is a contract that can be improved and renewed. These seven measures cover most of what an employer asks about.
- On-time pickup rate: the share of pickups where the vehicle arrived within the agreed window. Decide the window in writing, for example the scheduled time to five minutes after, so the number means the same thing every month.
- Trip completion rate: completed trips as a share of scheduled trips, with cancellations recorded by cause (employee, employer, operator, vehicle or weather).
- Escalations: how many complaints or calls reached a manager, and how long each took to resolve. A falling escalation count is often the first sign of a healthy contract.
- Safety events: overspeed, harsh braking and long idling recorded against trips, and what was done about each one.
- Compliance: the share of vehicles and drivers with every required document valid on the day they ran. Anything under 100 per cent needs an explanation.
- Cost per trip or per employee per month: the figure the employer's finance team compares across providers.
- Invoice accuracy: how many invoices needed correction, and how many lines were disputed.
Where the numbers come from
A measure is only as good as its source. On-time rates should be built from recorded arrival times, not from a dispatcher's recollection. Safety events should come from the vehicle's location data rather than from complaints. Compliance should come from expiry dates stored per document, checked when each duty is assigned.
In MobilityDrive, recurring bookings represent the standing schedule, SLA rules raise breaches when a duty runs late, tracking records geofence entries and exits and safety events such as overspeed, harsh braking and idling, and allotment checks vehicle and driver documents against their expiry dates. Reports are read from the same records as the books, so cost and invoice figures reconcile. See employee transportation software for the full list of what the product does, including what it does not do yet.
Safety and duty of care
Employers carry a duty of care for staff who travel on their behalf, and they will ask how you manage it. The answer should be specific. Which drivers are allowed to drive night shifts, and how is that checked? What happens when a vehicle deviates from its expected path or stops for too long? Who is called, and how is the call recorded? Written answers and a record of what happened each time are what turn a safety promise into evidence. Note that MobilityDrive does not have an employee panic button today, so if your contract requires one, plan for it separately.
Handling exceptions: no-shows, breakdowns and schedule changes
Routine trips run themselves. Exceptions decide how the contract is judged. Agree in advance how a no-show is treated (waiting time, then release the vehicle, and whether it is billed), who decides to send a replacement vehicle after a breakdown, and how a change in shift timings reaches the operator. Record each exception with its cause. After a month the causes will tell you whether the problem is the schedule, the vehicles, the drivers or the information you receive from the employer.
Common failure points
- The standing schedule is out of date, because changes to who rides live in a chat group rather than a system.
- Document expiry is noticed at a roadside check instead of in the office.
- Waiting time and extra stops are not recorded, so they are not billed, or are disputed.
- Complaints are handled by phone with no record, so the same issue repeats.
- Month-end billing is rebuilt from memory and messages.
A simple monthly review
Once a month, sit down with the employer for thirty minutes and walk through the seven measures. Bring the numbers, not stories. Agree one thing to improve before next month. Doing this consistently builds more trust than any presentation, and it makes contract renewals a conversation about a shared record.
A few practical habits help. Record the reason for every late pickup, so patterns appear. Keep one list of employees entitled to transport and import it from the employer's HR system if you can, so the list stays current. Share a trip tracking link with employees so they stop phoning for updates. For the technical side of tracking, see fleet and vehicle tracking software, and for how a corporate client can book and approve for their own staff, see the corporate client portal.
See how MobilityDrive handles this in practice
Bookings, dispatch, tracking, duty slips and invoices in one system. Book a demo on your own data.