Questions, answered

Click Get started, then use Proto to configure School Bus Tracking for your business. Pilot one organization and a representative morning route with ordered stops, an eligible driver, a Ready vehicle and a supervisor review.

A run has a number, subject, status, promised delivery time, organization, owner and transport partner. Stops, assignments, boarding observations, attachments, decisions and operation receipts link to it.

The run has recorded status and actual stop times. If your team needs a live location feed, agree a connection to the fleet or location service during implementation.

The Dispatcher records the route, authorized stop, boarding time and passenger count against the run. The Transport Supervisor can inspect a submitted record against the run and its supporting observations. The boarding record carries its status and decision time.

The Transport Supervisor examines the current revision and supporting evidence. A review decision, when recorded, carries an approve, reject or return value, reason and source revision.

Inspect driver activity and eligibility date, vehicle readiness and linked defects alongside the assignment interval before dispatch.

Record actual delivery time and compare it with the promised delivery time. Keep the relevant stop observations and evidence with the run.

Inspect the original operation receipt, operation key, expected revision and failure reason. Reconcile any recorded effect before treating the attempt as complete.

Each run links to its organization, owner and transport partner. Configure team membership and permissions for the operating scope and rehearse cross-organization access before release.

Bring stable organization, partner, run, driver and vehicle identifiers. Import parent runs before their stops, assignments and boarding observations, then reconcile the linked history.