Stops and windows

A load stop is an ordered visit within a parent load. The dispatcher records its sequence, address, appointment window and line number. During execution, the driver records actual arrival and departure. This separates the intended order from what happened on the road. A delivery stop adds recipient and handover evidence at the receiving end; the ordered load stop remains the route’s timing record.

The earliest load stop matters when delivery is completed. Its actual arrival and departure establish that movement was recorded before the final proof is accepted. Dispatcher should check that the sequence is unambiguous and that the first visit has both timestamps. Operations Overview can draw attention to active loads, while Load Stops by Sequence gives the team the detailed order of visits.

• Sequence. Put pickup and delivery visits in the intended order under one load.
• Window. Record the appointment start and end beside each address.
• Actual. Capture arrival and departure when the driver reaches and leaves the visit.

Agree who owns changes to stop order after a load is dispatched. Define the local time zone for windows and actual timestamps through the operating organization. The line number and sequence should have a clear convention, especially when a new visit is inserted between existing ones. Decide who confirms a changed appointment with the receiving party and where that agreement is retained.

Address quality matters to the person driving the route. Set a review step for an unclear address and make sure the dispatcher can contact the transport partner. Agree how an early arrival, missed window or site closure becomes an exception. A changed route should retain an understandable reason, so later reviewers can compare the original promise with the actual visit pattern.

Put a pickup first, followed by a delivery address with an afternoon window. The dispatcher checks that the assignment covers both visits. The driver records arrival and departure at pickup, then at the delivery address. When the recipient signs, the delivery stop holds the proof and handover time; the load stop retains the visit timestamps. An operations reviewer can look at the promised load delivery time, the appointment window and the actual arrival without treating them as the same thing.

Now enter two visits with the same earliest sequence. Dispatcher should resolve the order before the delivery is closed, because the first visit can no longer be identified uniquely. If the earliest visit lacks a departure time, the team should complete that record or investigate the gap before treating a final handover as complete.

• Load Stops by Sequence — Visits in their intended order with windows and actual times.
• Loads Default List — Parent loads and their promised delivery times.
• Loading Handoffs Default List — Submitted receiving handoffs awaiting a decision.

Follow planning to dispatch and stop to proof. Use the implementation plan to rehearse timing conventions.