These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- SCM with Route Optimization
- Features
- Stop execution
Stop execution
Record ordered delivery stops, promised windows and actual arrival evidence for each load.
OverviewStop Windows×
SCM with Route Optimization · Stop execution
New
Stop Windows
Load stops
| Parent | Stop sequence | Address | Window start | Window end | Actual arrival at | |
|---|---|---|---|---|---|---|
| LDS-34017 | 40 | B-7 | 09 Oct | 14 Oct | 21 Oct | |
| LDS-88680 | 50 | U-23 | 08 Oct | 11 Oct | 19 Oct | |
| LDS-92221 | 70 | Z-20 | 10 Oct | 18 Oct | 24 Oct | |
| LDS-48569 | 20 | R-3 | 09 Oct | 18 Oct | 21 Oct | |
| LDS-49993 | 10 | N-19 | 14 Oct | 20 Oct | 24 Oct |
6 of 6 records
B-7Load stops · LS-43919
ParentLDS-34017
Stop sequence40
Window start09 Oct
Window end14 Oct
Actual arrival at21 Oct
What you can do
Carry the plan into the trip
Load stops gives each load an ordered set of places to visit. Dispatcher can record the address, stop sequence and time window, then add actual arrival and departure times during execution. The stop record also has a proof reference. The parent load carries the broader promised delivery time and actual pickup and delivery times, so the team can compare the overall result with events at each stop.
How the work is organized
- Ordered work. The sequence and line number keep the planned progression clear for a load.
- Time windows. Window start and end describe when a stop is expected to be served.
- Observed events. Arrival, departure and proof reference show what happened at the stop.
The load status advances through Dispatched and In Transit before Delivered. A missed window can trigger a closer review even when the load eventually arrives. If a stop is changed after the route was reviewed, the route revision should be reconsidered before the team treats it as the same plan. That handoff matters because a reviewed mileage estimate and a later stop order may describe different trips.
What to agree during setup
Decide how dispatch enters stop addresses and who verifies them before route submission. Agree the meaning of arrival and departure timestamps, including local time zone treatment. Set a consistent proof reference practice so the person reviewing a delivery can reach the relevant evidence. Choose who updates the load status during transit and who handles a missing arrival event.
For a pilot, select a load with more than one stop and at least one narrow window. Enter the stops in sequence and attach them to the same load. Review the route proposal against those windows. During rehearsal, enter actual arrival and departure times, then check the promised delivery time against the load’s actual delivery time. A late arrival should be visible in the stop and delivery reports without altering the original window.
Check the handoff on an actual case
A driver reaches the first location within its window and departs after unloading. At the second location, arrival comes after the window end. Dispatcher records both actual times and the proof reference, then checks whether the final delivery still meets the promise. If the load is placed in Exception, Transport Supervisor can inspect the stop evidence and any related attachments before the next shift takes over. The route estimate remains a planning value; the timestamps are the operating record.
What your team sees
- Stop Windows — Stops due by today with their windows and recorded arrival times.
- Active Loads — Moving freight and its promised delivery date.
- Delivery Exceptions — Loads requiring attention when the trip departs from plan.
Follow the work through
Follow delivery execution and exception reconciliation.
What it keeps track of
Data model- Load stops
- Ordered stops with time windows and actual arrival evidence for each load.
- Loads
- Freight loads planned, dispatched and delivered by the organization.
- Record attachments
- Evidence files attached to a load.
- Route proposals
- Route proposals submitted for independent review before dispatch.
Who uses it
Permissions- Dispatcher
- Maintains stop plans and event times.
- Transport Supervisor
- Reviews exceptions.
- Auditor
- Reads authorized delivery evidence.
Set up SCM with Route Optimization your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.