Loads and commitments

A load begins with an operating organization, a responsible owner and a transport partner. Dispatcher records the subject, load number, promised delivery time and freight amount before arranging the work. The promise is the point of comparison when the load later receives an actual delivery time. A date on its own cannot say whether an individual stop was visited within its own window, so the ordered stop record carries that detail.

The lifecycle helps the team distinguish a draft from a planned load, a dispatched load from one in transit, and a delivered load from an exception. Operations Overview surfaces active work and pending decisions for triage. Dispatcher can follow a load from the board into its assignments, stops, evidence and review history. Operations Reviewer can see which exception needs a human decision and which receipt records a failed action.

• Commitment. Keep the promise, owner, organization and partner on the load so someone can answer for a delay.
• Execution. Link each assignment and ordered stop to the same load before marking it dispatched.
• Closure. Compare the actual delivery time with the promise and inspect stop evidence before closing the work.

Agree what information must be present when a load is created and who is allowed to dispatch it. Planning records an operation receipt and marks the new load Planned; Dispatcher checks the route before release. The dispatcher needs a practical rule for checking a driver’s eligibility date, the vehicle’s readiness and capacity, and interval overlaps before confirming an assignment. The load’s equipment class also needs a common meaning with the fleet’s equipment class. These are operating decisions that affect which load can safely take a vehicle.

Set a convention for freight amount in US dollars and for local time in each organization. Decide how the transport partner’s eligibility note is reviewed. Agree who records an exception and who decides whether to return or cancel work after a disruption. A cancellation affects an operational promise and should not be inferred from a failed receipt alone.

Take a load promised for Tuesday afternoon with a partner and a team owner. Add a pickup and delivery visit with distinct appointment windows. The dispatcher checks the earliest visit, reserves a driver and ready vehicle for the committed interval, and confirms who will record movement. After dispatch, the driver records actual pickup and stop times. If delivery is late, Operations Reviewer can compare promised and actual times and inspect the linked receipt and proof. The original promise remains visible through that review.

Now try a driver whose eligibility expires before the assignment ends. The dispatcher should hold the assignment until an eligible driver is selected. Try a vehicle marked Held and a second assignment that overlaps the first. Each case should stay out of confirmed dispatch until the conflict is resolved by the responsible person.

• Loads Default List — Load numbers, owners, partners and promised delivery times in one working list.
• Load Board by Lifecycle — Loads grouped by lifecycle for dispatch and exception review.
• Operation Receipts Default List — Failed or needs-review actions attached to the load.

Follow planning to dispatch and delivery to review. Use the data model when mapping source records.