Load planning and dispatch

Dispatcher opens a load with a recognizable record number, an accountable owner and the transport partner involved. The original promised delivery time gives everyone a stable point for follow-up. The equipment class and freight amount add operating context before a driver and vehicle are committed.

Creating the load records the planning action and its receipt, moving the load from Draft to Planned. Dispatcher checks the roster, vehicle readiness and existing commitments before dispatch. A Planned state still needs those feasibility checks. Dispatch records the actual pickup time and its own receipt when the movement is released.

• Keep the load identifiable. Dispatcher maintains the subject, record number and operating organization. The named owner follows outstanding work across shift changes. The transport partner reference points to the carrier contact and eligibility notes that the planning team needs.
• Check feasibility before release. Dispatcher examines driver eligibility and vehicle readiness alongside committed assignment windows. A held vehicle or a conflicting driver booking needs resolution before the planned movement can proceed. The team records the assignment for the actual period of work.
• Preserve the commitment. Dispatcher records physical pickup separately from the promised delivery time. Later movement updates should remain understandable against the promise accepted at planning. Operation receipts let Transport Supervisor trace what happened when the planning or dispatch action was attempted.

Agree the load numbering convention, who owns a load after shift handover and which organization should hold the record. App Administrator prepares the partner directory and confirms who maintains eligibility notes. Use recognizable subjects that dispatchers can distinguish when several loads share a destination.

Decide which source establishes the promised time and how staff record an observed pickup. A revised expectation should not overwrite the original promise. Set the practical handoff between Dispatcher and Transport Supervisor for exceptions, including the evidence the supervisor needs to understand a delayed release.

Prepare a rehearsal load from North Depot to River Terminal with a promised arrival at 16:00. The chosen driver is already committed until 12:30, while the new assignment begins at noon. Dispatcher sees the conflict and changes the assignment plan before treating the load as feasible.

Inspect the planning receipt recorded when the load was created. Confirm a suitable assignment before dispatch, then record a physical pickup at 13:05. Check that the original 16:00 promise remains visible. At shift change, another Dispatcher should be able to identify the owner, selected partner and recorded pickup without reconstructing the decision from messages.

Rehearse a failed dispatch attempt as well. Transport Supervisor uses the receipt to establish whether the action needs review before anyone tries again. The failed attempt remains useful evidence for the eventual resolution.

• Loads Default List — Draft and planned movements awaiting preparation or release.
• My Loads — Loads associated with the signed-in Dispatcher for ownership follow-up.
• Load Board by Lifecycle — Load records grouped by their operating state.

Follow Load to dispatch, then continue with Delivery and evidence.