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.
- Freight Brokerage Platform
- Features
- Dispatch and delivery
Dispatch and delivery
Record actual movement while retaining the delivery time originally promised.
OverviewLoads in Exception×
Freight Brokerage Platform · Dispatch and delivery
New
Loads in Exception
Loads
| Record number | Subject | Owner | Promised delivery at | Revision | Status | |
|---|---|---|---|---|---|---|
| LDS-74112 | Exception lds-194 | 16 Oct | 350 | Exception | ||
| LDS-31630 | Exception lds-637 | 13 Oct | 690 | Exception | ||
| LDS-54874 | Exception lds-129 | 27 Oct | 210 | Exception | ||
| LDS-21028 | Exception lds-672 | 17 Oct | 250 | Exception | ||
| LDS-32743 | Exception lds-733 | 26 Oct | 560 | Exception |
6 of 6 records
Exception lds-194Loads · LDS-74112
ExceptionPromised delivery at16 Oct
Revision350
What you can do
Follow movement with an unchanged promise
The Dispatcher releases a Planned load after checking its resource assignment and the relevant authorization. At physical pickup, record the actual pickup time and inspect the dispatch operation result. The load moves to Dispatched under the configured procedure. Keep the promised delivery time separate so the team can still explain the original commitment if the movement later changes.
During transit, stop records retain arrival and departure observations with proof references. On delivery, the Dispatcher records the actual delivery time and its supporting evidence. A Delivered state is useful when the team can follow it back to the movement record and the operation receipt that supports completion.
How the work is organized
- Pickup event. Record the physical pickup at the appropriate point in the dispatch procedure. Recheck driver eligibility and vehicle readiness before releasing the movement.
- Stop progress. Keep the ordered stop record with its appointment window and observed arrival or departure. The proof reference gives colleagues a route to the supporting evidence.
- Delivery comparison. Compare actual delivery with the original promise for a load whose timing evidence is complete. Investigate missing or inconsistent observations before using the result in a performance discussion.
What to agree during setup
Agree which event counts as physical pickup and which event establishes delivery. Confirm the time zone and timestamp precision used by the people recording those observations. The same movement should have an understandable sequence when read by a dispatcher on the next shift.
Define the procedure for moving a dispatched load into transit and for recording an operational exception. Decide who checks a completion receipt when the action result is uncertain. If movement observations come from a fleet or tracking service, configure that connection and rehearse its evidence mapping. Keep the delivery promise unchanged when reviewing a late arrival so the comparison remains useful to the supervisor.
Check the handoff on an actual case
Use the warehouse-to-cross-dock load with a confirmed assignment. The Dispatcher checks eligibility and readiness, records the physical pickup and inspects the dispatch receipt. During movement, enter the pickup departure and delivery arrival against the intended stops with their supporting proof references.
Complete delivery with its actual time and inspect the operation result. Ask the Transport Supervisor to compare that observation with the original promised time. Then rehearse a late delivery and confirm that the original promise remains available. Finally, inspect an uncertain completion result before repeating the action; the Dispatcher should be able to explain whether the local movement evidence already shows the load as Delivered.
What your team sees
- Load Board by Lifecycle — Follow loads through their recorded movement and exception states.
- Delivered Loads — Compare promised and actual delivery for completed movements.
- Load Stops by Sequence — Inspect appointment windows, movement observations and proof references.
Follow the work through
Follow dispatch and delivery and use exceptions and reconciliation when the recorded outcome needs investigation.
What it keeps track of
Data model- Loads
- Freight loads from pickup to delivery with promised windows, freight value and lifecycle
- Load stops
- Ordered pickup and delivery stops within a load with appointment windows
- Load assignments
- Driver and vehicle assignments to loads with committed start and end times
- Drivers
- Driver roster with eligibility expiry and external authority reference
- Vehicles
- Fleet vehicles with equipment class, capacity, readiness and external fleet id
- Record attachments
- Evidence files attached to loads with visibility and evidence type
- Operation receipts
- Idempotent operation receipts recording executed or failed actions with stable keys
Who uses it
Permissions- Dispatcher
- , Transport Supervisor, Auditor.
- The Dispatcher records movement; the supervisor examines delivery evidence and unresolved outcomes.
Set up Freight Brokerage Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.