Stops and delivery

A freight load may call at more than one destination. The Dispatcher records Load Stops against a single parent load, with a line number and stop sequence so everyone reads the same route order. The address and delivery window explain where and when the vehicle is expected. Actual arrival and departure times show what happened at the stop; the proof reference connects the handoff to recipient evidence.

The load’s promised delivery time remains its overall commitment. A stop window describes a specific visit. Keeping both lets the team investigate whether a delay began at an earlier stop, during transit or at the final destination. A late stop does not by itself say that a load was delivered. The Dispatcher still records the actual delivery time on the load after the recipient handoff.

• Sequence. The Dispatcher orders stops before route review and checks that each window belongs to the intended load.
• Arrive. The team enters actual arrival and departure against the specific stop, preserving the planned window for comparison.
• Prove. At final handoff, the Dispatcher retains the recipient proof reference and the load’s actual delivery time before closing delivery.

Load Stops carry a revision. When an owner asks to change a destination after planning, the revised stop should be reviewed with the load’s current scope. Existing arrival or proof evidence should remain attached to the original stop record so a later correction does not erase what occurred.

Decide how the team numbers stops, who may change their sequence and which stop represents final delivery. Agree how a recipient proof reference is collected and how the supporting file is attached to the load. The app stores a reference and can retain an attachment; the team must set the handoff with the system that produces the actual proof.

Set a rule for partial routes. If a vehicle visits an earlier stop but the last stop moves, the owner should say what happens to accepted work and what needs a successor record. The Operations Reviewer should see the exact route revision before deciding. Transport Partners need a clear contact path for a missed window; the partner record holds contact details and an eligibility note.

Consider a load with a collection stop and a delivery stop. The Dispatcher records each address and window, then confirms that stop sequence matches the physical route. After pickup, the first stop receives actual arrival and departure times. The load moves through Dispatched and in transit while its original promise stays available.

At delivery, the second stop receives an actual arrival time and proof reference. A Record Attachment can hold the supporting file with its visibility set for Internal or Shared access. The Dispatcher enters actual delivery time on the parent load and marks it Delivered. The Operations Analyst compares stop arrival with the window and load delivery with the promised time. If the recipient proof is disputed, the team can review the stop, attachment and load revision together.

• Stop windows — Ordered visits due in the current window with actual arrival and departure alongside plan.
• Delivery commitments — Loads whose promised time needs an outcome check.
• Delivery exceptions — Loads requiring follow-up before the delivery story is closed.

See planning and route review, delivery evidence and corrections.