Nexus
A Nexus trial can exist with no Tardy district, no pickup location, and no Chaperone family. Synthetic enrollment is simulated.
Open the Nexus trialSchool transportation, made clearer
A clearer view of the assigned bus.
Tardy.live is building a connected school-day view for transportation teams and families. Today that means routes, bus activity, and a parent view of one assigned bus and stop. Classroom confirmation is planned, not delivered.
Currently in pre-pilot development. Seeking school transportation teams for early product conversations. No live district deployment is implied.
Dispatch
Conceptual preview
Morning runs
Route 12Location on file
Route 4Update missing
Route 9Completed
Assigned stops stay with the families who use them. This drawing is not a recorded bus movement.
Try the local software
Each product stays on its own boundary. These pages do not start a live district, clear a Hold, or take a payment. Nexus device management here is simulated. It is not a sellable UEM and it does not replace a physical Android device test.
Tardy
This is the existing synthetic practice district. Live district activation stays gated. A synthetic or stale location is not a live bus.
Open the Tardy practice entryCommunity Pickup
This points at the existing Community Pickup director trial. Hold and release rules stay as they are. Nexus does not clear a Hold.
Open the director trial entryChaperone
Chaperone Free remains useful. Premium is 500 cents ($5.00) per month or 4800 cents ($48.00) per year per family. Checkout is not available.
Open the Chaperone entryOne school day. Clearer moments for the people who share it.
Parents want to know the bus is coming. Transportation directors need the run in front of them. Schools need a say before a route change is published. Tardy.live starts with those workflows.
Give dispatch a clearer picture
See active and completed runs, route progress, and buses whose location update is missing or stale. The location is the vehicle.
Keep route changes under district control
Drivers and authorized school staff can propose a change. Each affected school reviews that revision. The transportation office publishes it.
Show families their own bus and stop
A parent sees the assigned bus, their stop, and an estimate when a recent vehicle location is on file. Other students’ stops stay hidden. A stale location is labeled in the product.
The day a family is asking about
This is the experience we are building toward. Only the bus view is in the software today. Boarding, school entry, and classroom attendance are not field-validated.
- 7:12Bus approaching the assigned stop. Vehicle location. In the parent view today when a recent point is on file. A physical drive has not been completed.
- 7:18Boarding observed. Planned. A credential read would be an observation, not proof of identity. No physical reader is connected.
- 7:43School entry recorded. Planned. Staff rules would decide what a family may see. Not available now.
- 8:05Classroom attendance. Planned. A teacher or a school attendance record, not a nearby radio device.
- 3:42Afternoon assignment for that child’s stop. A vehicle location appears only when that run has a point. It is not proof the child reached home.
Designed around the school transportation day
District dispatch
- Active and completed bus runs
- Route progress for the service date
- Location freshness, including a missing update
- Operational exceptions on the dispatch board
Conceptual preview. The real console is the staff sign-in, not this drawing.
Route coordination
- A driver or school can suggest a revision
- The affected school reviews that exact revision
- The district publishes it as its own step
- An emergency note does not silently replace the route
Parent bus view
- The linked child’s assigned bus and stop
- Stops remaining before that pickup
- An estimate from a recent vehicle location, or a fallback label
- A stale location stays labeled as stale
Not another family’s stop. Not a student location. Not a road-matched arrival time.
Who it is for
For families
See the assigned bus when a recent vehicle location is on file. No location means the bus is not described as on the way. Alerts and student checkpoints are not field-validated. Text messages are not sent.
For transportation
Monitor routes, dispatch, and proposed changes. The software is in pre-pilot. GPS from a moving bus has been exercised on an emulator. A physical drive is still ahead.
For schools
Review the route revision that affects your building before the district publishes it. Verified classroom attendance is a later integration, not this release.
Insights, later
Dispatch can show exceptions today. Route punctuality trends, reader health, and district-wide reports are planned. They are not a dashboard you can open.
Three capabilities, one brand
Safety is a design rule across all three, not a separate product. The software can help people notice a missed handoff. It cannot promise that every child is safe.
Routes, vehicle location, dispatch, and the parent bus view.
Credential observations for boarding and arrival. Not for sale. No physical reader.
Trends and exception history for district leadership. Not built as a product.
A straightforward workflow for transportation teams
1. Set up routes and assignments
The transportation office establishes schools, buses, routes, stops, and roster assignments.
2. Operate and monitor bus runs
Drivers start and end a run in the driver experience. The office watches route activity. An Android app has passed emulator GPS tests only. An iPhone can use the driver page in Safari while that page stays open. Neither path is a moving-vehicle test. There is no native iPhone app.
3. Give families a focused bus view
An authorized parent sees the linked child’s assigned bus and stop. They do not see drafts or another student’s stop.
Built around a phone the district already has
The driver location device can be an Android phone or an iPhone. The Android path is an app that has been exercised on an emulator, not on a moving bus, and it can keep a foreground location service. The iPhone path in this software is the driver page in Safari. It is not a native app. Safari does not keep reporting location once the screen locks or the page is in the background. This is not a promise that every phone will work, that background location is reliable, or that deployment has no hardware cost.
Emulator GPS testing on Android is done. A real device on a moving bus is not. RFID readers are not part of the Transport conversation.
Visibility without tracking the student
The parent view is the assigned vehicle and that family’s stop. Bus GPS is the bus, not a child. A missing credential observation is not an absence, and a simulated credential is not identity. We do not claim a safety certification.
Help shape the next conversation about the school day
We are inviting transportation leaders to look at the development software, talk through their routes, and say what a later pilot would need. This is a discovery conversation. It is not enrollment in a district that is already live.
- Review the development demonstration
- Walk through route approval and the parent view
- Talk about phones, data, and what is not included
- Look at proposed Transport pricing
No purchase commitment. No live district deployment is implied.
Let’s make the school transportation day easier to manage.
Tell us about your district’s transportation needs and whether this approach is worth a closer look.