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.
- Fleet Management System
- Features
- Dispatch and delivery
Dispatch and delivery
Follow the checked assignment through actual pickup, stop activity and delivery against the original promise.
OverviewDelivered loads×
Fleet Management System · Dispatch and delivery
New
Delivered loads
Loads
| Record number | Subject | Counterparty | Owner | Promised delivery at | Actual pickup at | |
|---|---|---|---|---|---|---|
| LDS-51127 | Delivered lds-137 | TP-7902 | 08 Oct | 11 Oct | ||
| LDS-40873 | Delivered lds-568 | TP-9147 | 15 Oct | 17 Oct | ||
| LDS-70591 | Delivered lds-659 | TP-1919 | 07 Oct | 10 Oct | ||
| LDS-36451 | Delivered lds-815 | TP-7830 | 05 Oct | 07 Oct | ||
| LDS-31170 | Delivered lds-269 | TP-1191 | 22 Oct | 28 Oct |
6 of 6 records
Delivered lds-137Loads · LDS-51127
DeliveredCounterpartyTP-7902
Promised delivery at08 Oct
Actual pickup at11 Oct
Actual delivery at16 Oct
Freight amount USD50
What you can do
Record the movement that actually happens
The Dispatcher releases a load for movement after checking the intended driver, vehicle and service interval. Actual pickup is recorded with the dispatch action. The load’s promised delivery time remains available independently of later discussions about progress or expected arrival.
As the load moves, stop records retain actual arrivals, departures and proof references. Delivery records the recipient’s actual receipt time and the completion action’s result. These observations let the Operations Analyst compare the outcome with the original commitment and help dispatch explain any exception that arose during the movement.
How the work is organized
- Assignment interval. The load assignment identifies the driver and vehicle with start and end dates. Held and Confirmed arrangements are reviewed before dispatch. When the intended movement begins, keep the assignment state consistent with the load that is being carried.
- Actual operating times. Record physical pickup and delivery when they occur. Stop arrival and departure details add context where the journey includes intermediate work. Keep the promised window available throughout so a revised expectation does not erase the original comparison.
- Action evidence. Dispatch and delivery actions retain operation receipts with their expected revision and result. Use those receipts to investigate an uncertain action instead of assuming that a displayed lifecycle state explains every linked effect.
What to agree during setup
Decide who confirms physical pickup and who records recipient delivery evidence. Agree the time-zone convention and the proof references used at stops. Explain how the Dispatcher should record progress and escalate a load that needs an exception review.
Set a clear handoff for completing the assignment after delivery. Identify who reconciles an action result that is failed or needs review. Carrier accounting remains a separate connection to configure, with its own evidence for financial completion; the transport team should understand what its delivery record establishes for that handoff.
Check the handoff on an actual case
A load has a confirmed assignment and any required maintenance release has been checked. The Dispatcher records pickup at the actual time and inspects the resulting dispatch receipt. Follow the load into movement and enter the observed stop arrivals and departures with their proof references.
At the recipient, record the actual delivery time and the delivery action result. Complete the assignment associated with that movement. The Operations Analyst should be able to compare the actual delivery with the retained promise and identify the transport partner responsible for the service.
Repeat the case with a delay after pickup. Keep the original promise while recording the actual stop activity. If the remaining work needs intervention, route the load for exception review. Do not let a later estimate obscure the date used to judge the original commitment. Finally, rehearse a delivery action with an unresolved receipt and locate the authoritative evidence before anyone repeats the operation.
What your team sees
- Load Assignments Default List — Held, confirmed and dispatched assignments with driver, vehicle and operating interval.
- Load Stops by Sequence — Stop order and planned windows alongside actual arrival, departure and proof information.
- Delivered loads — Completed delivery observations compared with the original promised time.
Follow the work through
Follow planning and dispatch, then delivery and correction.
What it keeps track of
Data model- Loads
- Freight loads from pickup to delivery with promised windows, freight value and lifecycle
- Load assignments
- Driver and vehicle assignments for a load over a start and end interval.
- Load stops
- Ordered load stops with planned windows and recorded actual arrivals and departures.
- Drivers
- Fleet drivers with eligibility dates and external licensing authority, linked to their load assignments.
- Vehicles
- Fleet vehicles with equipment class, capacity, readiness and external fleet id.
- Operation receipts
- Idempotent operation receipts recording each fleet action, its expected revision and result state.
- Record attachments
- Evidence attachments linked to a load, with visibility and evidence type.
Who uses it
Permissions- Dispatcher
- , Fleet Coordinator, Transport Supervisor, Operations Analyst.
- Dispatch records physical movement, fleet staff support assignment questions and the analyst reviews retained delivery evidence.
Set up Fleet Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.