Truck Dispatch System follows freight loads from preparation through assignment, pickup and delivery. Dispatchers keep the promised delivery time, freight amount in USD, ordered stops and transport partner together.
Loads in one list
Transport Supervisor independently approves, rejects or returns the current load scope with a recorded reason.
Every feature works on the same records. Pick one to see the screen your team works in.
Prepare the promised delivery and stop sequence before committing a driver or vehicle.
Loads
| Record number | Subject | Status | Promised delivery at | Actual pickup at | Actual delivery at | |
|---|---|---|---|---|---|---|
| LDS-76350 | Frozen produce, Salinas to Reno | Draft | 23 Oct | 26 Oct | 04 Nov | |
| LDS-15767 | Building panels, Tacoma to Boise | Planned | 14 Oct | 19 Oct | 22 Oct | |
| LDS-94687 | Paper rolls, Eugene to Sacramento | Dispatched | 27 Oct | 01 Nov | 08 Nov | |
| LDS-74273 | Medical supplies, Phoenix to Tucson | In transit | 21 Oct | 30 Oct | 07 Nov | |
| LDS-21093 | Furniture, Fresno to Las Vegas | Delivered | 02 Nov | 04 Nov | 10 Nov |
Review driver eligibility and equipment readiness against the whole committed assignment interval.
Drivers
| Driver code | Name | Active | Eligibility until | External authority | |
|---|---|---|---|---|---|
| DRV-1042 | Rafael Mendoza | Yes | 21 Oct | CDL-A-OR-641882 | |
| DRV-1087 | Aisha Bello | Yes | 26 Oct | CDL-A-CA-783016 | |
| DRV-1124 | Tomasz Nowak | Yes | 25 Oct | CDL-A-WA-552741 | |
| DRV-1186 | Mei Lin | Yes | 29 Oct | CDL-B-AZ-309588 | |
| DRV-1203 | Jordan Ellis | Yes | 18 Oct | CDL-A-NV-720164 |
Keep warehouse review separate from the physical transfer of custody to the driver.
Approval conditions
| Parent | Warehouse | Driver | Pallet count | Revision | Status | |
|---|---|---|---|---|---|---|
| Paper rolls, Eugene to Sacramento | Salinas cold storage | Rafael Mendoza | 27 | 750 | Submitted | |
| Frozen produce, Salinas to Reno | Tacoma panel yard | Aisha Bello | 22 | 780 | Submitted | |
| Frozen produce, Salinas to Reno | Eugene paper mill | Tomasz Nowak | 2 | 830 | Submitted | |
| Paper rolls, Eugene to Sacramento | Phoenix medical warehouse | Mei Lin | 37 | 140 | Submitted | |
| Canned goods, Stockton to Flagstaff | Stockton food depot | Jordan Ellis | 16 | 90 | Submitted |
Compare actual arrival and delivery times with the original promise and retain the supporting proof.
Record attachments
| Parent | Title | Evidence type | Visibility | Uploaded at | Uploaded by | |
|---|---|---|---|---|---|---|
| Steel fittings, Ogden to Denver | Signed delivery receipt, Reno | Signed proof of delivery | Internal | 02 Nov | Tomasz Nowak | |
| Frozen produce, Salinas to Reno | Seal photo at Salinas pickup | Bill of lading | Shared | 20 Oct | Aisha Bello | |
| Frozen produce, Salinas to Reno | Bill of lading, Tacoma panels | Seal photo | Internal | 01 Nov | Fatima Rahman | |
| Steel fittings, Ogden to Denver | Damage photo, Boise unload | Temperature log | Shared | 11 Oct | Diego Alvarez | |
| Steel fittings, Ogden to Denver | Temperature log, produce load | Scale ticket | Internal | 22 Oct | Grace Kim |
Maintain the carrier contact and organization context behind each dispatch decision.
Transport partners
| Name | Code | Organization | Contact name | Address | Eligibility note | |
|---|---|---|---|---|---|---|
| Cedar Ridge Freight LLC | CRF | Cedar Ridge Freight LLC | Nora Patel | 420 Freight Way, Reno, NV | Insured for refrigerated freight | |
| Blue Mesa Carriers | BMC | Cedar Ridge Freight LLC | Isaac Flores | 85 Mesa Yard Road, Phoenix, AZ | Approved for western dry van lanes | |
| Iron Creek Transport | ICT | Redstone Freight Services Inc | Clara Jensen | 18 Foundry Lane, Ogden, UT | Flatbed permits verified through 2027 | |
| Northvale Haulage | NVH | Redstone Freight Services Inc | Malik Hassan | 742 Depot Street, Boise, ID | Liftgate service available weekdays | |
| Summit Basin Logistics | SBL | Cedar Ridge Freight LLC | Sienna Brooks | 290 Basin Drive, Denver, CO | Hazmat authority not on file |
Tie decisions to the reviewed revision and investigate failed actions without repeating external work.
Operation receipts
| Parent | Operation key | Action | Expected revision | Result state | Occurred at | |
|---|---|---|---|---|---|---|
| Steel fittings, Ogden to Denver | load-20261015-042-pickup | Assign driver and tractor | 900 | Pending | 18 Oct | |
| Packaging film, Spokane to Portland | load-20261014-018-deliver | Confirm pickup | 680 | Failed | 27 Oct | |
| Steel fittings, Ogden to Denver | load-20261013-007-assign | Record loading handoff | 920 | Needs review | 23 Oct | |
| Frozen produce, Salinas to Reno | load-20261012-031-handoff | Accept delivery evidence | 200 | Pending | 25 Oct | |
| Paper rolls, Eugene to Sacramento | load-20261011-006-review | Close completed load | 500 | Failed | 23 Oct |
Load plan to verified delivery ships ready to use. One step needs a named approval before the work moves on: Approve dispatch (Transport Supervisor).
Keep the original delivery promise with the load and ordered stops.
Check the driver, vehicle and committed interval before confirming the assignment.
Review the current load and resource evidence before authorizing movement.
Record actual warehouse handover and physical pickup.
Keep the actual delivery time and supporting proof with the load.
Investigate failed actions and confirm their effects before further work.
Open any load to see its load assignments, the roles that work on it, its process stages and its approvals on one page.
Promised delivery at, Freight amount USD, Equipment class and Owner.
Each line is linked to this load.
Dispatcher, Transport Supervisor and Fleet Coordinator, each with their own permissions.
Establish operating scope and Plan load, with the role that acts.
Approve dispatch, with who decides.
53 ft refrigerated trailer · Draft
| Load | Driver | Vehicle |
|---|---|---|
| Medical supplies, Phoenix to Tucson | Jordan Ellis | Tractor 117, flatbed |
| Packaging film, Spokane to Portland | Elena Varga | Straight truck 42, liftgate |
| Medical supplies, Phoenix to Tucson | Omar Haddad | Straight truck 42, liftgate |
Signed in as Transport Supervisor
| Decision | Approver | |
|---|---|---|
| Approve dispatchReview the current load and resource evidence before authorizing movement. | Transport Supervisor | |
| Approve Loads, loading handoffs | Transport Supervisor |
Everyone opens Truck Dispatch System to the work that is theirs. Pick a role to see what it starts with.
Prepares loads, checks assignment feasibility and records movement against the current dispatch decision.
This is the first screen this role sees.
Load stops · Dispatcher
| Parent | Stop sequence | Address | Window start | Window end | Actual arrival at | |
|---|---|---|---|---|---|---|
| Canned goods, Stockton to Flagstaff | 70 | Salinas cold storage, dock 3 | 17 Oct | 25 Oct | 01 Nov | |
| Steel fittings, Ogden to Denver | 30 | Reno distribution center, receiving | 17 Oct | 22 Oct | 24 Oct | |
| Canned goods, Stockton to Flagstaff | 60 | Tacoma panel yard, gate B | 13 Oct | 21 Oct | 24 Oct | |
| Paper rolls, Eugene to Sacramento | 60 | Boise construction depot, dock 2 | 12 Oct | 19 Oct | 25 Oct | |
| Canned goods, Stockton to Flagstaff | 30 | Eugene paper mill, west entrance | 21 Oct | 27 Oct | 29 Oct |
Independently decides dispatch, loading handoff and correction requests against their source revision.
This is the first screen this role sees.
Load stops · Transport Supervisor
| Parent | Stop sequence | Address | Window start | Window end | Actual arrival at | |
|---|---|---|---|---|---|---|
| Canned goods, Stockton to Flagstaff | 70 | Salinas cold storage, dock 3 | 17 Oct | 25 Oct | 01 Nov | |
| Steel fittings, Ogden to Denver | 30 | Reno distribution center, receiving | 17 Oct | 22 Oct | 24 Oct | |
| Canned goods, Stockton to Flagstaff | 60 | Tacoma panel yard, gate B | 13 Oct | 21 Oct | 24 Oct | |
| Paper rolls, Eugene to Sacramento | 60 | Boise construction depot, dock 2 | 12 Oct | 19 Oct | 25 Oct | |
| Canned goods, Stockton to Flagstaff | 30 | Eugene paper mill, west entrance | 21 Oct | 27 Oct | 29 Oct |
Maintains driver eligibility and vehicle readiness with supporting defect and repair evidence.
This is the first screen this role sees.
Load assignments · Fleet Coordinator
Prepares loading handoffs and records physical custody after the applicable review.
This is the first screen this role sees.
Load stops · Warehouse Coordinator
| Parent | Stop sequence | Address | Window start | Window end | Actual arrival at | |
|---|---|---|---|---|---|---|
| Canned goods, Stockton to Flagstaff | 70 | Salinas cold storage, dock 3 | 17 Oct | 25 Oct | 01 Nov | |
| Steel fittings, Ogden to Denver | 30 | Reno distribution center, receiving | 17 Oct | 22 Oct | 24 Oct | |
| Canned goods, Stockton to Flagstaff | 60 | Tacoma panel yard, gate B | 13 Oct | 21 Oct | 24 Oct | |
| Paper rolls, Eugene to Sacramento | 60 | Boise construction depot, dock 2 | 12 Oct | 19 Oct | 25 Oct | |
| Canned goods, Stockton to Flagstaff | 30 | Eugene paper mill, west entrance | 21 Oct | 27 Oct | 29 Oct |
Investigates failed operations and compares delivery evidence with the original commitment.
This is the first screen this role sees.
Load stops · Operations Analyst
| Parent | Stop sequence | Address | Window start | Window end | Actual arrival at | |
|---|---|---|---|---|---|---|
| Canned goods, Stockton to Flagstaff | 70 | Salinas cold storage, dock 3 | 17 Oct | 25 Oct | 01 Nov | |
| Steel fittings, Ogden to Denver | 30 | Reno distribution center, receiving | 17 Oct | 22 Oct | 24 Oct | |
| Canned goods, Stockton to Flagstaff | 60 | Tacoma panel yard, gate B | 13 Oct | 21 Oct | 24 Oct | |
| Paper rolls, Eugene to Sacramento | 60 | Boise construction depot, dock 2 | 12 Oct | 19 Oct | 25 Oct | |
| Canned goods, Stockton to Flagstaff | 30 | Eugene paper mill, west entrance | 21 Oct | 27 Oct | 29 Oct |
Configures staff access, organization scope and partner reference data without substituting for a transport approval.
Compare delivery performance, resource conflicts, warehouse reviews and unresolved action outcomes.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 31 | ||
| Planned | 5 | 16% | |
| Dispatched | 2 | 40% | |
| In transit | 1 | 50% |
Sample totals per stage
Which loads remain planned, dispatched, in transit or excepted within the selected organization, and what freight amount is associated with them?
Which delivered loads finished after the original promise, and which records still need an actual delivery time before comparison?
Where do held, confirmed or dispatched assignments share a driver or vehicle during overlapping committed intervals?
Which assignments extend beyond the selected driver's recorded eligibility, and who must obtain current authority evidence?
Which vehicles are held or in maintenance, and what defect, repair and release evidence needs review before assignment?
Which submitted warehouse handoffs need Transport Supervisor to decide the current revision?
Where does actual arrival fall outside the appointment window, and which delivery proof references need supporting evidence?
Which actions remain failed or unresolved, what effects are referenced and what reason explains the discrepancy?
See how Truck Dispatch System fits your kind of team.
Coordinate load commitments with driver eligibility and equipment readiness across dispatch shifts.
Connect warehouse custody with pickup and delivery evidence for scheduled distribution loads.
Keep partner identity, operating scope and reviewed outcomes clear for contracted transport work.
Each stage of load plan to verified delivery names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Ask Proto to prepare dispatch reviews and explain the evidence behind operational exceptions.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 15 tablesStart with one team and one process, then add the rest once the basics are running.
Choose the organization, dispatch shift and loads for the pilot. Name the Dispatcher and Transport Supervisor, then agree the custody handoff and delivery completion rules with Warehouse Coordinator. Define the time zone and preserve the original customer promise.
Reconcile partner codes, staff user mappings and organization access. Fleet Coordinator checks driver eligibility, vehicle readiness and defect evidence before resources enter the assignment process.
Bring the selected loads and ordered stops with their original numbers and promised times. Link existing assignments, handoffs and evidence without re-executing historical movement. Compare the imported state with the team’s physical operating position.
Test an overlapping assignment, expired driver eligibility and a vehicle held for a defect. Return a dispatch request for correction, reject an inaccurate pallet count and record a late delivery with valid proof. Inspect a duplicate operation and an uncertain external outcome.
Transport Supervisor checks the decision trail and each team’s access. Operations Analyst reconciles the action receipts with confirmed movement. Release the reviewed configuration after the team can explain the open work and handle the agreed exceptions.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Truck Dispatch System for your business. Start with a dispatch shift and representative loads whose pickup, delivery and resource evidence your team can reconcile. Prepare active drivers, ready vehicles and the transport partner directory before importing open work.
Dispatcher prepares the load, original promised delivery and ordered stops, then links the driver and vehicle with a committed start and end. The resource review checks eligibility, readiness and competing assignments before the load reaches Transport Supervisor for release review.
Compare the complete assignment intervals for the same driver or vehicle, including held, confirmed and dispatched work. A prior job running late needs attention before the next commitment is released. Review the current resource evidence again after a substitution.
Transport Supervisor independently reviews the current load scope and records an approval, rejection or return with a reason. Dispatcher resolves returned work before seeking another decision. A change to reviewed scope requires a decision on the current revision.
Approval authorizes the reviewed warehouse work. Warehouse Coordinator records the actual handover time and completes the handoff when the driver takes custody. Dispatcher compares that evidence with pickup rather than assuming that approval means the truck has departed.
Keep the proof reference on the delivery stop and attach supporting evidence to the load. Record a useful document title, evidence type and visibility. Agree which source establishes delivery and who checks the document before treating the operational outcome as complete.
Compare actual delivery with the original promised delivery time using the agreed time zone and completion rule. Stop arrival and departure provide context for the delay. Preserve the original promise when a revised estimate is discussed, and investigate delivered records that still lack an actual time.
Operations Analyst inspects the existing action receipt and linked effects before any repeat attempt. Unresolved discrepancies stay visible for review until the authoritative source confirms the outcome. Transport Supervisor decides the permitted correction, and external work is not repeated by reconciliation.
Yes, as configured connections with agreed record ownership and stable source references. Fleet activity, warehouse inventory movement and carrier settlement each retain their own authority. Use the integration plan to define the evidence exchanged and rehearse uncertain outcomes.
There is no per-user fee. The base account and ordinary manual work in the official interface are free. Machine work, retention beyond included allowances and model usage follow the platform rate card; implementation is priced separately. See pricing for the current policy and credit behavior.
Start free, then use Proto to change fields, steps and approvals before your team goes live.