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.
- Truck Dispatch System
- Features
- Load planning
Load planning
Prepare the promised delivery and stop sequence before committing a driver or vehicle.
OverviewMy loads×
Truck Dispatch System · Load planning
New
My loads
Loads
| Record number | Subject | Status | Promised delivery at | Actual pickup at | Actual delivery at | |
|---|---|---|---|---|---|---|
| LDS-76350 | Draft lds-487 | Draft | 15 Oct | 18 Oct | 27 Oct | |
| LDS-15767 | Planned lds-778 | Planned | 06 Oct | 11 Oct | 14 Oct | |
| LDS-94687 | Dispatched lds-713 | Dispatched | 19 Oct | 24 Oct | 31 Oct | |
| LDS-74273 | In transit lds-243 | In transit | 13 Oct | 22 Oct | 30 Oct | |
| LDS-21093 | Delivered lds-756 | Delivered | 25 Oct | 27 Oct | 02 Nov |
6 of 6 records
Draft lds-487Loads · LDS-76350
DraftPromised delivery at15 Oct
Actual pickup at18 Oct
Actual delivery at27 Oct
What you can do
Plan around the delivery commitment
Dispatcher starts with the load number, customer-facing subject and promised delivery time. The operating organization and transport partner establish who owns the work. The freight amount stays in USD so the team can compare the value of open loads on a consistent basis. A planned load still needs an assignment and a dispatch decision before movement begins.
Keep the pickup and delivery locations in their intended stop sequence. Each stop can carry its appointment window and later its actual arrival and departure. This gives the next dispatcher enough context to continue the job without reconstructing the journey from messages. Operations Overview helps the team identify active loads and the decisions needing attention at the start of a shift.
How the work is organized
- Record the promise. Keep the original delivery commitment with the load. A later arrival estimate must not overwrite the time against which the customer expects performance to be measured.
- Order the stops. Record the address and appointment window for each pickup or delivery. Check the stop sequence with the people who will execute it before asking for an assignment.
- Give the load an owner. Assign the responsible team member and the correct transport partner. Another dispatcher taking over should see who is responsible for the plan and which organization owns it.
What to agree during setup
Agree the source of load numbers and the time zone used by the organization. Decide who may correct a promised time and how the original evidence will be retained. Confirm which stop evidence is needed before dispatch and which proof is collected at delivery. Use the same understanding when importing work already in progress.
Planning records support a feasibility review by the team. If route optimization or travel-time calculation is needed, agree that connection separately. Dispatcher still checks that the intended stop windows fit the chosen assignment and seeks a new review when a material change affects the dispatch decision.
Check the handoff on an actual case
A load has a morning pickup at a distribution center and an afternoon delivery appointment. Dispatcher records both stops and the promised delivery time. Fleet Coordinator then reports that the intended vehicle is held. Keep the plan visible while the team finds eligible equipment; do not mark the load dispatched because the stop addresses are complete.
The replacement vehicle changes the available pickup time. Dispatcher checks the appointment with the warehouse, updates the affected plan and presents the current revision for review. Transport Supervisor must be able to explain whether the revised assignment can still meet the promise. At the next shift, the load owner can find the decision and the original commitment without guessing which message was final.
What your team sees
- Loads Default List — Draft, planned and excepted loads needing preparation or a decision.
- My loads — Loads assigned to the signed-in team member, with promised and actual movement times.
- Load Stops by Sequence — Appointment and arrival evidence for stops whose opening window has arrived.
Follow the work through
Use plan and assign a load to prepare the assignment, then review and dispatch to authorize movement. Confirm import mappings in the data model.
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
- Organizations
- Logistics operating organizations with time zone, currency and active scope
- Team members
- Staff membership linking platform users to organizations with operational roles
- Transport partners
- Eligible carriers and transport partners with contact and eligibility notes
Who uses it
Permissions- Dispatcher
- , Transport Supervisor, Operations Analyst, Admin.
- Dispatcher
- Prepares the plan.
- Transport Supervisor
- Reviews release scope, and Operations Analyst compares the retained promise with actual delivery evidence.
Set up Truck Dispatch System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.