Stops and delivery

Each stop belongs to a load and has a sequence, address and appointment window. The Dispatcher can use the ordered stop list to show where a pickup or delivery is expected, then record actual arrival and departure times against the same stop. A proof reference gives the team a place to retain the identifier supplied at the stop. The load itself holds the promised delivery time and the actual pickup and delivery times for the whole movement.

Consider a load with a warehouse pickup followed by a recipient delivery. The pickup has its own window and observed arrival. The delivery stop has a later window and its own observed arrival. Looking at both stops shows whether the movement fell behind before it reached the recipient. Comparing the load’s actual delivery time with its original promise answers a different question: whether the overall delivery met the commitment.

• Sequence. Dispatcher orders the stops and records the address and appointment window for each.
• Observe. The operations team records actual arrival and departure as the driver reaches each location.
• Close. Dispatcher records the load’s actual delivery time and completion operation when the recipient handoff is finished.

The stop’s line and revision identify its place in the load record and its current form. An appointment change should be handled with care because the prior commitment may still matter to a dispute or review. The load promise remains independent of the stop window. If the recipient changes the appointment, the team can see the new operational window without treating it as a silent change to the original load promise.

Agree who supplies stop addresses and windows, who enters actual times, and what reference counts as proof at each location. Decide how the warehouse team records pickup evidence and how recipient evidence reaches the Dispatcher. An attachment can hold a file related to the load, while the stop proof reference can point to an external document or acknowledgment.

Use one time-zone policy across stop windows, assignment intervals and the load promise. The operating organization has its own time zone; agree which local display a dispatcher sees when a driver crosses boundaries. If proof arrives from a carrier or customer system, define that connection and its authority. The operations team should still be able to trace a completion decision to the received evidence.

Create the pickup and delivery stops in sequence for a planned load. Enter their windows, then record observed arrival and departure at pickup. After dispatch, record the recipient arrival and proof reference. Record actual delivery on the load with a completion receipt. Compare each arrival to its window and the final delivery time to the promised time.

Try a late arrival. Leave the recorded window and promise intact so the Operations Manager can explain the gap. If an operation receipt fails, inspect the linked load and stop evidence before treating the delivery as complete. The review trail should tell a new shift what happened without relying on a verbal handoff.

• Stop appointment windows — Stops due for attention with their sequence, window and observed arrival.
• Active load lifecycle — The load promise and movement state beside the stop work.
• Delivery evidence — Load attachments that support pickup, arrival and recipient handoff.

See delivery completion and load planning and dispatch.