These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- School Bus Tracking
- Features
- Student boardings
Student boardings
Record and independently review boarding observations for a bus run.
OverviewRun attachments×
School Bus Tracking · Student boardings
New
Run attachments
Record attachments
| Parent | Title | Evidence type | Visibility | Uploaded at | Uploaded by | |
|---|---|---|---|---|---|---|
| LDS-45399 | Internal ra-364 | ET-702 | Internal | 04 Oct | ||
| LDS-34641 | Shared ra-129 | ET-204 | Shared | 13 Oct | ||
| LDS-96152 | Internal ra-788 | ET-946 | Internal | 10 Oct | ||
| LDS-81477 | Shared ra-216 | ET-104 | Shared | 14 Oct | ||
| LDS-92488 | Internal ra-209 | ET-824 | Internal | 06 Oct |
6 of 6 records
Internal ra-364Record attachments · RA-23622
InternalParentLDS-45399
Evidence typeET-702
Uploaded at04 Oct
What you can do
Tie boarding evidence to the run
A student boarding record belongs to a run and an organization. It can carry a route, boarding time, passenger count and authorized stop. These facts let the team examine whether a reported boarding fits the run without copying student identity into the operational record. The Dispatcher prepares the record; the Transport Supervisor can inspect submitted evidence.
Draft and Submitted describe preparation. Approved or Rejected records a review outcome, while Completed is a later operational state. The review should be based on the recorded route, stop, time and count together with any linked run evidence. A change to the record’s revision calls for another examination. Keep the decision time visible so the next shift can tell when its recorded status was set.
How the work is organized
- Context. Link the boarding to the correct run and operator before entering route or stop detail.
- Observation. Record boarding time, authorized stop and passenger count from the operational evidence.
- Decision. Submit the record for review, then inspect its status and decision time.
The boarding register gives the Dispatcher and Supervisor the whole progression. The awaiting-review view narrows the work to submitted entries that need a decision.
What to agree during setup
Agree who supplies the boarding observation, who may correct a count, and how a correction after submission is reviewed. Keep student identity in the designated student system. Decide what constitutes sufficient proof for a boarding: an authorized stop, a time consistent with the run and a count supported by the operator’s record. Define how the Supervisor handles a disputed count while the bus run continues.
The organization link matters when several districts or contracted operators share the workspace. A Dispatcher should work within their assigned operating scope, and an Auditor should see only authorized evidence. When a boarding is marked Rejected, investigate the supporting run evidence before changing the record.
Check the handoff on an actual case
A bus reaches a scheduled pickup stop at 7:43. The Dispatcher records a boarding with that route, authorized stop, time and passenger count, linked to the morning run. The record moves from Draft to Submitted. The Transport Supervisor compares it with the run’s stop observation and any supporting attachment. The boarding status and decision time show whether a decision has been recorded.
If the count conflicts with available evidence, the supervisor can flag the discrepancy for correction. A review decision for the run refers to the run revision it examined; it does not identify a boarding revision. The run’s delivery status should be evaluated separately; an approved boarding does not itself establish that the journey finished on time.
What your team sees
- Boarding register — Follow boarding entries from draft through review and completion.
- Boardings awaiting review — Focus on submitted records that need a supervisor decision.
Follow the work through
What it keeps track of
Data model- Student boardings
- Verified student boarding records for a bus run.
- Loads
- Planned and executed school bus runs.
- Load stops
- Ordered pickup and drop-off stops on a bus run.
- Record attachments
- Files and evidence linked to a bus run.
- Review decisions
- Independent approve, reject and return decisions.
Who uses it
Permissions- Dispatcher
- Prepares boarding entries; Transport Supervisor inspects submitted evidence; Auditor reads authorized evidence; Admin manages access.
Set up School Bus Tracking your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.