Loads and dispatch

A freight job begins with a load number, subject, operating organization, owner and transport partner. The Dispatcher records the promised delivery date and freight amount before route work starts. The status then gives the team a common account of planning, dispatch, transit, delivery or an exception.

The load is the parent for bookings, stops, receipts, decisions and attachments. Its revision matters whenever a later action depends on the exact scope that was reviewed. A Dispatcher can compare the promised date with actual pickup and delivery rather than replacing one with a changing ETA.

• Name the shipment. Give the load a number, subject, owner and partner before adding related work.
• Hold the promise. Keep the promised delivery date visible when a vessel estimate changes.
• Record physical events. Use actual pickup and delivery times to support transit and completion.

Record the organization, owner and counterparty before anyone prepares a booking. Keep the freight amount with the load so a partner report can group the agreed operational amount. Use the subject to distinguish similar container movements without turning it into an unofficial status.

When planning begins, confirm that the route and intended equipment suit the job. When pickup is confirmed, record the actual pickup time before treating the load as in transit. A delivery timestamp supports completion; a refused or partial delivery remains an exception for review.

For a container due on Tuesday, the Dispatcher records the promised delivery date on the load and a separate ETA on the booking. If the vessel estimate shifts to Wednesday, the original promise stays visible. The Transport Supervisor can see the variance and the attachments that explain the handoff.

At pickup, the Dispatcher records the actual time before moving the load into transit and inspects the action receipt. At delivery, the team compares the actual time with the original promise. A refused or partial handoff remains an exception with its supporting evidence on the load.

If the operation receipt shows a failed result, the Transport Supervisor compares its expected revision with the current load before another change. The next Dispatcher can then see whether the physical event was recorded even though the requested status action failed.

• Load Board — Follow open freight work by its current operating status.
• Load Register — Find a shipment by number and compare promised and actual delivery.
• My loads — Focus the owner on the loads assigned to them.

Read the operating process and the related handoff. Set up roles and rehearse the case in implementation.