Marking an Event As Sent in Schedule Editor

When changes are made to a schedule (for example, a trip is added to a run, information regarding a trip has changed, or a trip has been canceled), they must be relayed to drivers so that the necessary modifications can be made to the routes.

Before you begin

Schedule Editor must be open to Run Itinerary view.

About this task

Once the change has been recorded on the schedule and dispatched to the driver, you can record the method by which it was sent. Marking an event as sent is typically done in Dispatch but can also be done in Schedule Editor.

Procedure

  1. Highlight the dispatched event.
  2. Click the Mark menu, and then click Sent by Voice or Sent by MDT.

Results

A code appears in the Send column of the run’s itinerary.
DV
The event was dispatched by voice.
DM
The event was dispatched by MDT.
DL
The event was dispatched by a log sheet (the DL code can only be selected in Dispatch).

Any event you mark as sent in Schedule Editor is automatically taken off the Incidents list in Dispatch (Task > Dispatching). However, you may still have to go back to Dispatch to mark off certain incidents.

For example, if Run 101 is running late and the scheduler/dispatcher decides to reschedule a trip from Run 101 to Run 102, there are four incidents to relay to the drivers and to mark as sent:
  • The removed pick-up of the trip in run 101.
  • The removed drop-off of the trip in run 101.
  • The added pick-up to run 102.
  • The added drop-off to run 102.

In Schedule Editor, you can pull the itinerary for Run 102 and mark the event as sent, but because the trip is taken off the itinerary on Run 101, you must mark the first two events in the Incidents list in Dispatch as sent.