QR and NFC checkpoints
Drivers can use the same checkpoint workflow through QR or NFC, reducing the number of separate operational steps they need to remember.
Planned vs. actual
Is the Shuttle Running keeps the operating plan connected to actual driver activity so managers can review exceptions, fill-ins, pauses, and completed service with more context.
Direct answer
Is the Shuttle Running compares the planned assignment with evidence created during the operating day. That includes authenticated driver sessions, QR or NFC checkpoint activity, schedule context, rider confirmations, live operational status, and management review. The result is a service record that distinguishes a plan from actual execution.
Drivers can use the same checkpoint workflow through QR or NFC, reducing the number of separate operational steps they need to remember.
One scheduled assignment can contain multiple actual sessions when service stops for a break, vehicle issue, mistaken ending, or another real-world interruption.
When a different driver takes over, actual activity changes without rewriting the scheduled-driver history.
Rider confirmations can provide an additional operational signal for management review rather than relying on one source of evidence alone.
Is the Shuttle Running's current verification model is centered on the operating workflow: authenticated checkpoints, driving sessions, workforce schedule context, rider signals, and manager review. It is designed to answer operational questions such as who was scheduled, who actually drove, when service was active, and where the plan changed.
That makes Is the Shuttle Running useful even when the organization already has a separate vehicle or fleet system and needs a stronger record of the employee-shuttle process itself.
Is the Shuttle Running records authenticated driving sessions and can compare them with the planned assignment, schedule context, QR/NFC activity, rider confirmations, and management review signals.
Yes. Is the Shuttle Running supports multiple actual sessions under one scheduled assignment, which allows service to stop and resume without pretending it was one uninterrupted block.
The scheduled driver remains part of the plan, while the actual session records the person who drove. This keeps accountability and workload reporting clearer.
The current product is focused on operational verification rather than continuous GPS telematics. Its evidence comes from driver checkpoints, driving sessions, schedule context, rider signals, and manager review.
Is the Shuttle Running is designed to make exceptions reviewable instead of disappearing into text messages, memory, or a manually edited spreadsheet.
Request a demo