Marking Loads 'Ready to Return' Best Practices

A load may appear stuck in the "drop loaded" status on the dispatch board, even when the system indicates a change. This behavior is typically due to an incomplete workflow, specifically an unconfirmed delivery event and an untendered return move.

• Observed Status:

  • Dispatch board displays a persistent "drop loaded" status.

  • System interface indicates a change (e.g., timestamp or status update), but this is not reflected on the dispatch screen.

• Root Cause:

  • The delivery event has not been confirmed, preventing further progression in the workflow.

  • The original tender included only a single move (pull, deliver, drop).

  • The return move was not tendered, resulting in a stalled status and an open item.

Resolution Steps

To resolve the open item:

1. Confirm the Delivery Event

   • Ensure the delivery has been accurately marked as complete in the system.

2. Verify Tendering of the Return Move

   • Check that the return leg of the trip has been properly tendered.

   • If not, coordinate with the relevant team (e.g., brokerage or planning) to have the return move issued.

3. Mark as “Ready to Return”

   • After delivery confirmation, update the container or load status to “Ready to Return.”

   • This triggers visibility for the next leg of the move across systems.

Is This an Intentional System Design?

Yes. The system is designed to prevent status updates on the dispatch board until:

• The delivery event is confirmed.

• All necessary movement legs, including return moves, have been tendered and accepted.

This design helps ensure that only complete and actionable loads are marked as ready for the next step.

Best Practices

• Always confirm delivery events promptly to avoid status delays.

• Double-check that both outbound and return legs are included in the original tender.

• Regularly review load audit and routing details to ensure full workflow visibility.

• Provide training for dispatch and operations teams on event confirmation procedures.

Additional Notes

Once the container or load is marked “Ready to Return” on the carrier side, the update becomes visible to the broker or solutions team as well. This synchronization supports smooth handoffs and operational clarity between systems.