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
- Load planning
Load planning
Prepare each freight load with a clear owner, partner, promise and route planning boundary.
OverviewDelivery Exceptions×
SCM with Route Optimization · Load planning
New
Delivery Exceptions
Loads
| Record number | Subject | Status | Promised delivery at | Actual delivery at | Counterparty | |
|---|---|---|---|---|---|---|
| LDS-31144 | Exception lds-138 | Exception | 23 Oct | 26 Oct | TP-7374 | |
| LDS-43639 | Exception lds-236 | Exception | 18 Oct | 22 Oct | TP-2659 | |
| LDS-16293 | Exception lds-771 | Exception | 08 Oct | 11 Oct | TP-9628 | |
| LDS-94192 | Exception lds-798 | Exception | 07 Oct | 14 Oct | TP-7778 | |
| LDS-20004 | Exception lds-521 | Exception | 25 Oct | 01 Nov | TP-8758 |
6 of 6 records
Exception lds-138Loads · LDS-31144
ExceptionPromised delivery at23 Oct
Actual delivery at26 Oct
CounterpartyTP-7374
What you can do
Start with the delivery promise
Dispatcher creates a load for the responsible organization and names the transport partner, owner and promised delivery time. The freight amount and equipment class give the operating team a practical starting point. A load begins as Draft. Once the team has checked its stops and transport plan, it can be marked Planned. The record number stays the reference for conversations across dispatch, review and delivery.
How the work is organized
- One accountable owner. The owner connects each load to a team member. My Loads helps a Dispatcher focus on assigned work.
- A specific partner. The counterparty identifies the carrier or transport partner for the movement. Freight by Partner can then group the amount and outcome by that partner.
- A dated promise. The promised delivery time can be compared with the actual delivery time after completion. An exception remains visible for follow-up.
The Operations Overview page brings active loads, pending review decisions, failed operations and the exception queue together. Use it to choose the next record to inspect, then work from the load and its related records. A summary should lead to the actual decision and evidence, not replace them.
What to agree during setup
Agree which organization owns each load and who may be assigned as its owner. Confirm the transport partner list, equipment naming and local time zone conventions before the first operating cycle. Set a record number practice that dispatch, the partner and the reviewer can recognize. Decide who changes a Draft load to Planned and what evidence is needed before dispatch.
For a pilot, choose a shipment with several delivery stops and an actual promised date. Enter the load, set its partner and owner, then check that the stops belong to the same load. If a partner changes, review the assignment and route proposal before dispatch. A load revision lets the team distinguish the plan under review from an older version.
Check the handoff on an actual case
Suppose a load must arrive on Thursday afternoon. Dispatcher records the promise, selects the partner and adds the stop windows. The route proposal can carry estimated miles and a revision for Transport Supervisor to review. Once the driver and vehicle interval are confirmed, the load can move to dispatch. During transit, stop arrivals and the actual delivery time turn the original promise into a measurable outcome. If the shipment is delayed, mark Exception and attach the relevant evidence so the next shift sees the same facts.
What your team sees
- Active Loads — Planned and moving freight with the promise, owner and partner in one list.
- My Loads — Work assigned to the current owner.
- Delivery Exceptions — Loads that need an explicit follow-up after the normal plan changes.
Follow the work through
Start with load preparation, then follow the route review and delivery execution.
What it keeps track of
Data model- Loads
- Freight loads planned, dispatched and delivered by the organization.
- Load stops
- Ordered stops with time windows and actual arrival evidence for each load.
- Route proposals
- Route proposals submitted for independent review before dispatch.
- Load assignments
- Driver and vehicle intervals held for a load.
- Transport partners
- Carriers and transport partners eligible for load assignment.
- Team members
- Staff and their role scope inside an organization.
Who uses it
Permissions- Dispatcher
- Prepares and updates the load.
- Transport Supervisor
- Reviews route and exception evidence.
- Auditor
- Reads authorized outcomes.
- App Administrator
- Maintains the organization and partner records.
Set up SCM with Route Optimization your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.