
An average shuttle operation runs like this: assignment in a diary or Excel, drivers updating on WhatsApp, clients calling to ask where the shuttle is, and settlement closing at month end against what everyone remembers. It works - until it doesn't: a parent's complaint, a dispute with a client over rides performed, or an incident where suddenly everyone asks who the driver was, when they left and what exactly happened.
Student transport: responsibility that demands proof
In student transport the regulation is strict and parents' expectations absolute. Whoever drives must be whoever was approved; pickup and drop-off times must hold; and in any event - a fall, a fight, an unusual stop - the driver's version is one word against twenty parents. Automatic driver identification secures the first, real-time tracking the second, and video documentation of the cabin and road the third. The responsibility doesn't shrink - but it becomes provable.
'Where is the shuttle?' - the question that burns the dispatch desk
Anyone who has run a shuttle operation knows the morning: dozens of calls, one dispatcher, zero visibility. When every ride runs on a live map with status and ETA, and delay alerts go automatically to whoever needs to know, the question gets answered before it's asked. Dispatch stops being an inquiry switchboard and goes back to managing.
Proof of execution - the basis for settlement
The difference between 'we performed all the rides' and a report showing time, route, driver and documentation per ride is the difference between an hour of arguing and a minute of signing. When every ride closes as a documented execution event, client settlement is built from actual execution, disputes close against data, and the month closes in days.
The economics: same vehicles, less waste
A shuttle fleet accumulates the same quiet losses: engines idling while waiting for passengers, private trips between shifts, reported-vs-actual hour gaps and fuel anomalies. Detecting all of these automatically, with real-time alerts and cost per kilometer at vehicle and driver level, returns money the fleet was quietly burning - and video documentation turns every finding from an awkward conversation into a documented fact.
What it takes to start
No fleet replacement and no downtime: the system installs on the existing vehicles, vehicle by vehicle, by a team that installs, onboards and stays. Data starts flowing from the first vehicles within days - and the operation keeps carrying passengers as usual throughout. Want to see it on a real shuttle operation? Talk to us.
Contact Us
Contact usRelated articles
Bus fleet management: why GPS alone is no longer enough
Most bus fleets run on a tracking system today. It knows where the bus is - but not what happened inside it. The difference between fleet management built on GPS points and management built on evidence, and why it matters most when the cargo is people.
GPS disruptions: a fleet manager's guide
Vehicles jumping to a neighboring country on the map, mileage that doesn't add up and reports that fall apart - GPS disruptions are routine for fleets in Israel. The difference between jamming and spoofing, how to check what's happening in your area right now, and how to build an operation that keeps documenting even when the satellite lies.
