Stops and windows

Ordered stops belong to a run. Each stop carries its sequence, address and planned window when those details are known. Actual arrival and departure times belong on the same stop, so the team can compare the plan with the recorded journey. A proof reference can point to the supporting observation without turning a free-text note into a route decision.

A stop is a child of a run. That link matters when similar addresses appear on multiple routes or when the same bus serves several runs in a day. Open the parent run first, then inspect its ordered stops. Keep the run’s promised delivery time separate from individual stop windows: the former is the outcome commitment, while the latter tells the Dispatcher what is expected along the way.

• Sequence. Record each stop in order and retain the line number and revision used for that run.
• Window. Enter a start and end for a planned stop window so the Dispatcher can inspect the schedule.
• Observation. Add arrival, departure and proof reference as the journey unfolds; preserve what was actually recorded.

The stop window schedule brings planned windows and actual observations into one list. The Dispatcher can open the parent run from a stop instead of treating each row as an independent journey.

Decide who maintains the stop order, how a revised route is numbered and which observation source the team trusts. Agree whether a school or operator supplies the planned windows and who can correct an actual time. Keep an explanation with corrections so a Transport Supervisor can understand why the record changed after dispatch.

Use a consistent organization time zone when comparing windows across a day. If an external routing or location service is part of the operation, agree its identifier mapping and how its observations enter the run record. The Dispatcher can inspect the final sequence and the source of an exception before communicating a changed arrival expectation.

A morning run has a school pickup before the final drop-off. The first stop has a planned window ending at 7:40. At 7:43 the bus arrives and the observation is recorded on that stop. The team can see the gap between window and actual time without changing the original plan. The later stop records its own arrival and departure and remains attached to the same run.

If the stop sequence changes after dispatch, review the run revision and the reason for change. Do not use a new stop row to hide an older observed time. When a boarding is associated with a stop, check that the boarding’s authorized stop and time make sense alongside the stop observation. The boarding decision remains separate from the stop’s scheduling record.

• Stop window schedule — Compare each recorded window with arrival and departure on the parent run.
• Run status list — Open the active run before reviewing the related stops.

Plan the route details and record pickup and boarding.