Bus runs

A Dispatcher begins with a run number, a subject, the operating organization and the team member who owns the work. The promised delivery time anchors the schedule. The transport partner identifies who will provide service. Keeping these details on one run lets the next shift distinguish an active journey from another day’s route with a similar name.

The run starts in Draft. The Dispatcher can inspect its stops, assignment and supporting evidence when assessing the plan. Planned, Dispatched and in transit describe different points in the work. A recorded actual pickup and delivery time explain what happened; a status label alone is a poor substitute for that evidence. Mark an unusual run Exception and keep the reason in linked evidence or the associated operation receipt.

• Preparation. Record the organization, owner, partner and promised delivery time before scheduling a driver or vehicle.
• Execution. Keep stop observations and boarding entries attached to the same run number as dispatch progresses.
• Outcome. Compare actual delivery time with the promise and examine any failed operation receipt before closing the case.

The Operations Overview brings active runs, delivery performance, review backlog and failed operations into one working screen. Use it to choose the next case, then open the run and its linked records for the decision.

Agree what a run number represents, when a run becomes Planned, who is allowed to mark pickup and delivery, and who resolves an Exception. Decide how the team records a delay: the run’s actual time, the stop observation and the evidence should describe the same event. Define when a cancelled draft may be replaced and how an executed run is corrected without erasing its earlier history.

Keep the organization’s time zone consistent when entering promises and observations. The App Administrator maintains the operator and staff records. The Dispatcher owns the daily run; the Transport Supervisor owns independent review of a revision that needs a decision. The Auditor needs enough access to follow the record afterward.

Take a morning run promised by 8:10. The Dispatcher records it in Draft and inspects its ordered stops and scheduled driver and bus. Compare a Planned run with any Confirmed assignment before interpreting a Dispatched status. At the first pickup, record actual pickup time. The stop record holds its arrival and departure observations; a boarding record holds the route, authorized stop, boarding time and passenger count. At completion, record actual delivery time and compare it with 8:10.

If delivery is late, the comparison belongs in the delivery timing report and the run’s evidence. If an operation fails, inspect its receipt and failure reason before attempting a correction. A recorded review decision refers to the source revision examined; a later edit does not change that historical reference.

• Run status list — Find runs still being prepared, dispatched or handled as exceptions.
• My bus runs — Let a Dispatcher focus on runs assigned to their team member record.
• Run workboard — Move between the current status groups without using a date as the board’s organizing key.

Plan the run and reconcile its outcome.