Platform
Transportation first. The rest of the school day is the roadmap.
A transportation director can already walk through dispatch, route review, and a parent bus view in the development software. Journey checkpoints and leadership analytics are labeled by how far they have actually been built.
Transport
Pre-pilot
- District dispatch for runs, progress, and stale or missing vehicle updates.
- Route revisions reviewed by the affected school, then published by the district.
- A parent page for the assigned bus and that child’s stop.
- An arrival estimate when a recent vehicle location is on file, with a stale-location label.
Driver GPS has been tested on an Android emulator. A physical phone on a moving bus has not. An iPhone can open the parent page and the driver page in Safari. That is not a native app and not a passed road test. Safari location stops when the screen locks. Text alerts are not sent.
Journey
Simulation
- A credential observation can be posted by a development simulator.
- The observation stays separate from a boarding decision.
- A missing observation is not an absence.
- A presented credential is not proof of who is holding it.
No USB or Bluetooth reader is connected. Journey is not for sale. A detailed note lives on the privacy page.
Insights
Planned
The dispatch board can surface exceptions today. Punctuality trends, exception-resolution time, and reader health are a later product. They are not a report a district can open now.
What a parent can see today
Their linked child’s assigned bus, assigned stop, and how the product describes a recent vehicle location. Not another student’s stop. Not a draft route. Not a classroom status. Not a guarantee that the child boarded. Chaperone is a separate product and is not built here.
