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
- Assignments and readiness
Assignments and readiness
Connect each run window to an eligible driver and ready vehicle.
OverviewDriver eligibility×
School Bus Tracking · Assignments and readiness
New
Driver eligibility
Drivers
| Driver code | Name | Active | Eligibility until | External authority | |
|---|---|---|---|---|---|
| DC-783 | Driver 223 | Yes | 04 Oct | EA-436 | |
| DC-602 | Driver 873 | No | 07 Oct | EA-625 | |
| DC-162 | Driver 561 | Yes | 08 Oct | EA-248 | |
| DC-361 | Driver 455 | No | 05 Oct | EA-269 | |
| DC-853 | Driver 947 | Yes | 06 Oct | EA-954 |
6 of 6 records
DC-783Drivers · DRV-17415
YesNameDriver 223
Eligibility until04 Oct
External authorityEA-436
What you can do
Check the people and bus behind the schedule
An assignment ties a run to a driver, a vehicle, a start and an end. Its recorded status can be Held, Confirmed, Dispatched, Completed or Cancelled as the commitment changes. That interval helps a supervisor see who is expected to operate a particular run and which bus is committed at the same time.
The driver record includes an active flag, an eligibility date and an external authority reference. The vehicle record includes active and readiness values, an equipment class and an external fleet ID. These are the recorded facts the Transport Supervisor can inspect when deciding whether an assignment is fit for the run. A linked defect gives its severity, repair evidence and release date. Treat a held or maintenance bus as a readiness question before dispatch.
How the work is organized
- Driver. Confirm the chosen driver is active and their eligibility covers the planned interval.
- Vehicle. Review the bus’s readiness and any linked defect before confirming the commitment.
- Interval. Compare assignment start and end with the run’s planned stop windows and promised delivery.
A confirmed assignment identifies the intended crew and equipment. The run’s own status records the operating journey; changing the assignment should not silently move the run through dispatch or delivery.
What to agree during setup
Agree who maintains driver eligibility and which external authority provides that reference. The App Administrator maintains driver and vehicle master data; the Transport Supervisor can inspect readiness during operational review. Decide when a bus with a defect can return to Ready and who records the repair evidence and release date. Confirm the local rules for overlapping commitments before a Dispatcher uses the schedule.
Also agree how equipment class is used. It exists both on the run and on the vehicle, so the team should use the same wording and inspect mismatches before dispatch. If a fleet system supplies readiness or identity, map its identifier carefully and decide how a conflicting update is handled. The run remains the place to review the resulting assignment.
Check the handoff on an actual case
A morning run needs a bus from 7:00 to 8:15. For a morning run, inspect a driver whose eligibility extends beyond that interval and a vehicle marked Ready. A Held assignment remains distinct from a Confirmed one while the supervisor examines the driver, vehicle and stop schedule. When the run departs, the run and assignment each carry their appropriate dispatched state.
If the vehicle is marked Maintenance or has a critical defect under review, the supervisor holds the assignment and asks for an alternative. Retain the defect’s repair evidence and release date when the bus returns to service. A later reassignment should explain which driver and vehicle actually served the run, rather than overwriting the decision history.
What your team sees
- Assignment schedule — Inspect committed drivers, buses, intervals and assignment status.
- Vehicle readiness — Find buses marked Ready, Held or Maintenance before making a commitment.
- Driver eligibility — Review eligibility dates that require attention.
Follow the work through
What it keeps track of
Data model- Load assignments
- Driver and vehicle commitments for a bus run.
- Drivers
- Licensed bus drivers and their eligibility.
- Vehicles
- School buses and their readiness.
- Vehicle defects
- Reported bus defects and repair state.
- Loads
- Planned and executed school bus runs.
Who uses it
Permissions- App Administrator
- Maintains drivers and vehicles; Dispatcher prepares the run; Transport Supervisor checks readiness; Auditor inspects the history.
Set up School Bus Tracking your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.