Load planning

The Dispatcher starts with a load number and subject that the team can recognize. The load belongs to an operating organization, has a named owner and points to the transport partner responsible for the movement. Its promised delivery time sets the point against which the actual delivery can later be read. Freight amount and equipment class stay on the same record so a transport handoff does not lose the commercial and equipment context.

A load moves from draft through planning and dispatch into transit and delivery. An exception remains visible on the load instead of disappearing into a note. A cancelled load stays identifiable as cancelled. The Operations Overview brings authorized load activity together with terminal moves and review activity for the appropriate organization and owner.

The Dispatcher prepares the load record. The Transport Supervisor can inspect the load and the evidence that later depends on it.

• Named ownership. The owner reference gives each load an accountable team member.
• Partner context. The counterparty reference identifies the carrier or terminal partner involved.
• Delivery promise. The promised and actual delivery times let a supervisor see which commitments were met.

Agree when a draft is sufficiently planned, who assigns the owner and which partner should be selected when several organizations use the same transport network. Decide how staff distinguish an exception from a cancellation and who may update the load after dispatch. Prepare a representative load with a real partner, equipment class, promised delivery and ordered stops. Confirm that the team uses its operating time zone when reading delivery dates.

The administrator should settle organization membership and partner eligibility before dispatchers begin creating loads. A name match alone is a weak operating control when similar partners serve different organizations; the reference to the partner record should be checked on the case.

A Dispatcher creates a load for an inbound container, selects the operating organization, names the responsible team member and selects the transport partner. The promised delivery is set for the next day. Ordered stop records show the terminal pickup and delivery address. The supervisor opens the same load and checks that its partner, owner and equipment class fit the assignment.

After pickup, the load records its actual pickup time and moves into transit. If a delivery issue occurs, the Dispatcher marks the load as an exception so it stays on the active board. When delivery finishes, the actual delivery time can be compared with the promise. The container move and its independent decision remain linked through the load; changing the load status does not replace that evidence.

• Active Loads — Loads in planning, dispatch or transit, with owner and promised delivery visible.
• Operations Overview — Authorized load activity by owner and operating organization.
• Load Status Board — Work grouped by lifecycle state for the dispatch conversation.

• Plan and dispatch a load.
• Review a container move.