Dispatch and tracking

A planned load becomes an operational commitment when the Dispatcher knows which driver and vehicle will move it. The assignment links those resources to the load and records a start time, availability check and revision. Held work stays distinguishable from Confirmed assignments, and dispatch progress can be followed without losing the identity of the equipment selected.

The Assignment roster is the working list for this handoff. Review it with the Fleet Coordinator before the trip. Driver eligibility and vehicle readiness help the team decide whether the intended pairing is usable. An equipment change should be reflected in the assignment before the next shift relies on it.

• Confirm the resources. The Dispatcher selects the driver and vehicle for the load. Review the driver’s active state, availability and eligibility date with the Fleet Coordinator, then record the availability check supporting confirmation.
• Release the trip. The Dispatcher records the actual dispatch against both the assignment and the load. Review the stop sequence and plant appointment before departure so the driver has a consistent movement to execute.
• Review the milestones. Record departure, arrival, delay, exception and delivery events against the load. Each event retains when it occurred, its location and its source. Confirm an event after checking its evidence; keep a superseded account distinct from the current account of the trip.

Agree who records events and how quickly the team expects significant changes to reach the Dispatcher. An event source can identify a dispatcher, partner, driver app or telematics origin. Arrange and test any external feed before relying on it. Decide how staff will reconcile a partner call with a later position update describing the same movement.

Use the organization’s time convention consistently when entering assignment starts and event times. Confirm the driver eligibility review with the Fleet Coordinator and decide what happens when a vehicle is placed in Maintenance or Held. A recorded availability check should explain the decision clearly enough for someone covering the next shift to understand it.

Rehearse an inter-plant load with a Confirmed assignment. Before departure, the Fleet Coordinator reports a major defect on the selected truck. The Dispatcher keeps the trip from proceeding on the old pairing, agrees a replacement and updates the assignment revision and availability check. Compare the replacement truck with the plant’s dock arrangement before recording dispatch.

Next, enter a reported delay from the transport partner. Record its actual occurrence time and location, then compare it with the load’s delivery promise. The Dispatcher confirms the supported event and contacts the receiving plant if the appointment needs attention. A corrected event can supersede the earlier account while preserving the reason for the change.

• Assignment roster — Held, confirmed and dispatched assignments with the selected driver, vehicle and start time.
• Active Loads — Planned and moving loads grouped by transport status, including exceptions.
• Tracking event review — Reported and confirmed milestones with their source and occurrence time.

Use load planning and dispatch before continuing to delivery verification.