How it works

A straightforward workflow for transportation teams

The district operates the buses. Schools review the route that affects them. Families see their own stop. That is the workflow in the software today.

Set up routes and assignments

The transportation office establishes schools, buses, routes, stops, and which students belong on which run. Parents are invited to their own children.

Operate and monitor bus runs

A driver starts and ends the run. Dispatch watches progress and location freshness. The Android app is still in physical-device validation. An iPhone uses the same driver page in Safari, and that page does not keep location going with the screen locked. Emulator tests are not a road trial.

Give families a focused bus view

An authorized parent opens the assigned bus and stop. An estimate appears when a recent vehicle location is on file. The product says when that location is stale.

Route changes stay reviewable

A driver or a school can propose a revision. The affected school reviews that revision. The district publishes it. Drivers do not publish. A note during a live run does not become a new official route by itself.

The phone is the location device under test

Tardy.live is being built so an Android phone or an iPhone can report the bus. The iPhone path here is Safari on the driver page, not a native app. That avoids assuming a proprietary tracker as the starting purchase. It does not mean every phone is supported, that background location is proven, or that a district’s mobile data is included. iOS Safari cannot run as a locked-screen foreground service the way the Android app can.