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
- Data model and import order
The tables behind Truck Dispatch System
Truck Dispatch System ships with 15 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 15
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Load planning:
Loads retains record number, Subject, Status, promised delivery at, freight amount USD and Revision. Load stops carries the ordered appointment and actual movement detail through Parent.
Driver and vehicle assignments:
Load assignments joins Load, Driver and Vehicle with starts at, ends at and Status. Drivers holds eligibility until and external authority; Vehicles holds equipment class, capacity LB and Readiness. Vehicle defects references the affected Vehicle.
Loading handoffs:
Loading handoffs links Parent and Organization, retaining its own Revision, Status, decision at and handed over at with warehouse custody details.
Delivery evidence:
Load stops.proof reference and record attachments.Parent connect proof to the load. Loads.actual pickup at and actual delivery at retain actual lifecycle timing separately from promised delivery at.
Transport partners and teams:
Organizations anchors Loads, team members and transport partners. Team members.User links the operational staff identity to Users. Exchange rates is read-only reference data and does not change the USD denomination of freight amount USD.
Review and reconciliation:
Review decisions retains Parent, source revision, Reviewer and operation key. Operation receipts retains Parent, expected revision, result state and references to action effects.
Every table, by feature
- Load planning5
- Driver and vehicle assignments5
- Loading handoffs5
- Delivery evidence5
- Transport partners and teams6
- Review and reconciliation7
- Loads
Freight loads from pickup to delivery with promised windows, freight value and lifecycle
Linked to Organizations, Team members, Transport partners - Load stops
Ordered pickup and delivery stops within a load with appointment windows
Linked to Loads - Organizations
Logistics operating organizations with time zone, currency and active scope
- Team members
Staff membership linking platform users to organizations with operational roles
Linked to Organizations, Users - Transport partners
Eligible carriers and transport partners with contact and eligibility notes
Linked to Organizations
- Load assignments
Driver and vehicle assignments to loads with committed start and end times
Linked to Loads, Drivers, Vehicles - Loads
Freight loads from pickup to delivery with promised windows, freight value and lifecycle
Linked to Organizations, Team members, Transport partners - Drivers
Driver roster with eligibility expiry and external authority reference
- Vehicles
Fleet vehicles with equipment class, capacity, readiness and external fleet id
- Vehicle defects
Reported vehicle defects with severity, repair evidence and release time
Linked to Vehicles
- Loading handoffs
Warehouse-to-driver custody handoff extensions with review and completion state
Linked to Loads, Organizations - Loads
Freight loads from pickup to delivery with promised windows, freight value and lifecycle
Linked to Organizations, Team members, Transport partners - Organizations
Logistics operating organizations with time zone, currency and active scope
- Review decisions
Independent approval, rejection or return decisions on a source revision
Linked to Loads, Team members - Record attachments
Evidence files attached to loads with visibility and evidence type
Linked to Loads, Team members
- Loads
Freight loads from pickup to delivery with promised windows, freight value and lifecycle
Linked to Organizations, Team members, Transport partners - Load stops
Ordered pickup and delivery stops within a load with appointment windows
Linked to Loads - Record attachments
Evidence files attached to loads with visibility and evidence type
Linked to Loads, Team members - Load assignments
Driver and vehicle assignments to loads with committed start and end times
Linked to Loads, Drivers, Vehicles - Operation receipts
Idempotent operation receipts recording executed or failed actions with stable keys
Linked to Loads
- Organizations
Logistics operating organizations with time zone, currency and active scope
- Team members
Staff membership linking platform users to organizations with operational roles
Linked to Organizations, Users - Users
Users
Linked to Users - Transport partners
Eligible carriers and transport partners with contact and eligibility notes
Linked to Organizations - Loads
Freight loads from pickup to delivery with promised windows, freight value and lifecycle
Linked to Organizations, Team members, Transport partners - Exchange rates
Read-only effective exchange rates for this app.
- Review decisions
Independent approval, rejection or return decisions on a source revision
Linked to Loads, Team members - Operation receipts
Idempotent operation receipts recording executed or failed actions with stable keys
Linked to Loads - Loads
Freight loads from pickup to delivery with promised windows, freight value and lifecycle
Linked to Organizations, Team members, Transport partners - Load assignments
Driver and vehicle assignments to loads with committed start and end times
Linked to Loads, Drivers, Vehicles - Loading handoffs
Warehouse-to-driver custody handoff extensions with review and completion state
Linked to Loads, Organizations - Record attachments
Evidence files attached to loads with visibility and evidence type
Linked to Loads, Team members - Team members
Staff membership linking platform users to organizations with operational roles
Linked to Organizations, Users
Keys and references
Preserve the existing Id or ID keys and business codes during import. Resolve references by stable source identity rather than display names. Loads.Owner refers to team members, and team members.User supplies the user mapping for personal work queues. Load assignments.Driver is a reference to Drivers; loading handoffs.Driver is text and needs an explicit identity check during the custody process.
Keep Loads.Revision and loading handoffs.Revision distinct. A review decisions.source revision refers to its parent load revision; retain the handoff context in the agreed review evidence before treating a parent decision as approval for a particular handoff. Operation key identifies the requested action. A repeated key needs its existing outcome checked before any new execution.
Store timestamps under the agreed organization and staff time-zone convention. Preserve promised delivery at when recording actual delivery at. Keep freight amount USD in USD even when Organizations.Currency differs. Vehicle defects.repair evidence and released at remain evidence to inspect alongside Vehicles.Readiness.
Migration order
- Prepare Organizations and Users, preserving platform-managed identity references.
- Load team members and transport partners with their organization and user mappings; retain exchange rates as read-only reference data.
- Load Drivers and Vehicles, then link vehicle defects to the intended vehicle.
- Load Loads with Organization, Owner and Counterparty resolved; add load stops, load assignments and loading handoffs against those parents.
- Attach record attachments, review decisions and operation receipts to their original loads. Reconcile revisions, source references and actual movement times before opening dispatch.
Set up Truck Dispatch System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.