Load coordination

Dispatcher prepares a load with its organization, responsible team member, transport partner and promised delivery time. The assignment identifies the driver and vehicle with a committed start and end. That context matters when a tire inspection leads to maintenance: the team can see the transport work affected while deciding how to handle the equipment.

Keep the delivery promise independent of the actual pickup and delivery times. A late departure or vehicle substitution should not quietly rewrite the original promise. Operations Overview helps the team triage active loads and delivery performance; the detailed load and stop records explain the case behind that summary.

• Prepare the load. Confirm the partner, operating organization and equipment needs before moving from Draft to Planned. Fleet Coordinator helps Dispatcher check the resources being considered for the assignment.
• Check the assignment. Compare the complete start and end interval for both driver and vehicle. Review eligibility, readiness and existing commitments before confirming the resources and releasing movement.
• Record the actual journey. Retain pickup, delivery and stop evidence as events occur. Use the stop sequence and appointment windows to understand where a delay or disputed handoff happened.

Choose the operating time zone and the source of the promised delivery time. Agree which team member owns each load and who updates the record during a shift change. The transport partner directory should contain usable contact details and eligibility notes for the organizations that Dispatcher will actually work with.

Prepare ordinary assignments and a vehicle substitution for the pilot. Decide how staff identify the relevant assignment when a tire inspection refers to the load. Agree how actual arrival, departure and proof references are collected at each stop. If those facts come from another transport system, configure the connection and its responsible owner before relying on its updates.

A planned load is assigned to V-18 for the afternoon. A submitted tire inspection raises a maintenance question before pickup. Dispatcher reviews Fleet Readiness Board with Fleet Coordinator and checks the affected interval. If another vehicle is selected, record the actual assignment context and ensure the inspector’s observation remains associated with the vehicle that was inspected.

Continue the rehearsal through pickup and delivery. Record the actual pickup when movement is released, then the actual delivery when the recipient handoff is confirmed. A later delivery still compares with the original promise. Review the stop evidence to explain the delay without changing the original commitment to make the comparison appear favorable.

Finally, introduce a failed dispatch operation receipt. The load owner should be able to identify the receipt and establish whether movement actually occurred. Physical evidence and the recorded result must agree before the team treats the operation as resolved.

• Load Assignments Default List — Compare committed driver and vehicle intervals while planning the next movement.
• Loads Default List — Review loads owned by the signed-in team member with their promised and actual delivery times.
• Load Board by Lifecycle — Follow active transport work and exceptions by their current stage.

Follow load planning through delivery. Use exception reconciliation when the recorded operation and observed journey disagree.