Dispatch and delivery

Dispatcher works from a planned load with a transport partner, ordered stops and a confirmed driver and vehicle assignment. Before release, the team checks driver eligibility, vehicle readiness and overlapping committed intervals. The physical pickup time is recorded when the load actually moves, rather than when the assignment was created.

A dispatch operation receipt uses a stable key and expected revision. It separates a pending action from a completed or failed one. A retry should resolve against that same operation identity, so a repeated request does not create an unexplained second dispatch effect. The load moves to dispatched while its promised delivery time remains the original comparison point.

Stop records provide appointment windows, actual arrival and departure times, and a proof reference. Dispatcher can follow the load in transit by comparing the expected sequence with observed events. An exception state makes a problem visible without rewriting the plan as though it had been met.

• Movement status. Planned, dispatched, in transit, delivered and exception describe different operating states.
• Actual times. Pickup and delivery observations remain separate from the promised delivery time.
• Execution receipt. A stable operation key supports investigation and safe retry handling.

Agree who is allowed to dispatch and who records actual pickup when the driver and dispatcher are in different locations. Set a procedure for obtaining stop proof references and checking a missing arrival. Decide when a delayed movement becomes an exception requiring Review Manager attention. The carrier contact process should use the selected transport partner directory entry.

Use a load promised to a market by late afternoon. Confirm its resource assignment and pickup check, record physical departure, then enter actual arrival at each stop. If the vehicle reaches the market after the promise, leave the promised time intact and record the actual delivery time. The completed operation receipt should point to the same load revision. Operations Analyst can then compare promise and actual without reconstructing the trip from messages. If dispatch fails, the receipt should show the failure for review instead of quietly advancing the load.

• Load Board by Lifecycle — Loads grouped by lifecycle so Dispatcher can distinguish planned, moving and delivered work.
• Load Stops by Sequence — Appointment windows beside actual arrival and departure at each stop.

See the operating process and implementation for the first rehearsal.