Attendance & Vehicle Checks

    Record Shuttle Attendance. Confirm the End-of-Route Check.

    Employees scan a vehicle QR to record attendance, with driver approval for unexpected passengers. School drivers record students who did not board and use a separate QR at the rear inside the vehicle for the post-trip cabin check.

    Attendance and Cabin Checks Need Clear Records

    An employee shuttle's attendance list and a school driver's end-of-route cabin check record different events. Paper lists and verbal confirmations make both difficult to review later. A clear digital record should show who scanned, which vehicle or service was involved, and when the action happened.

    • Employee attendance scans are hard to reconcile with the assigned passenger list
    • Vehicle checks rely on verbal confirmations that are difficult to review later
    • Attendance and end-of-route checks can be confused with each other
    • Manual attendance sheets get lost, damaged, or never filled out

    Two QR Workflows for Attendance and Vehicle Checks

    Employees scan the vehicle QR in Servistesin during an active service. RouteBot records the passenger, service, vehicle, and scan time. If the passenger is not assigned to that service, the driver is alerted and can approve adding their location to the route. The route can then be re-optimized. For schools, drivers record students who did not board; students do not need to scan a QR code. The post-trip inspection uses a separate QR at the rear inside the vehicle.

    Vehicle QR for Employee Attendance

    Employees scan the vehicle QR in the app. The timestamped record links their attendance to the active service and vehicle. Administrators can review assigned passengers and additional scans; a missing scan alone does not prove that someone did not ride.

    Driver-Approved Route Updates

    An unexpected passenger's scan alerts the driver. If the driver approves the passenger, their location is added to the current route. The updated route can then be re-optimized; the scan alone does not change it.

    Driver-Managed Student Attendance

    On school routes, drivers use the passenger list to record students who did not board. The attendance action is saved and triggers a push alert for parents who have it enabled. Students do not need a phone or QR code for this workflow.

    End-of-Route Vehicle Check

    At the end of the school route, the driver walks to the rear inside the vehicle, checks for remaining children, and scans the QR placed there. The scan supports the physical inspection; it does not by itself prove that the vehicle is empty.

    Frequently Asked Questions

    Yes, passengers need the app for self-scanning. This is mainly used on employee shuttles. School attendance is normally managed by the driver, so students do not need their own phones. The driver also uses the app for the separate post-trip vehicle check.
    No. QR attendance is an optional feature. Organizations can enable or disable it based on their needs.
    No. The QR at the rear inside the vehicle supports the driver's physical cabin inspection after the trip. It does not record passenger boarding or prove that no child remains. Passenger QR attendance and driver-recorded student absences are separate records.

    See QR Attendance in the Demo

    QR scanning takes place in the Servistesin mobile app. In the dashboard, open an employee service's tracking details to review recorded attendance scans. The web demo uses sample data.

    No signup required · Instant access · Sample data included