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.
- Vehicle Inspection App
- Data model and import order
The tables behind Vehicle Inspection App
Vehicle Inspection App ships with 20 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
- 20
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Inspections and checklists
Inspections references Vehicles and Drivers; vehicle defects can link back through Inspection.
Defects and repairs
Vehicle defects references Vehicles, Inspections and team members through Owner. Open Defects is a saved list over vehicle defects.
Fleet and maintenance
Vehicles and Drivers belong to Organizations. Maintenance plans and fuel transactions reference Vehicles.
Load approval and assignment
Loads references Organizations, team members and transport partners. Load assignments references Loads, Drivers and Vehicles. Routes belongs to Organizations. Active Loads and Loads Awaiting Approval are saved lists over Loads.
Dispatch and delivery
Load stops and tracking events reference Loads. Proof of delivery references both Loads and load stops; freight charges references Loads.
Evidence and review
Operation receipts and review decisions reference Organizations and team members. Record attachments belongs to Organizations. Team members.User references Users; Users.User also references Users.
Every table, by feature
- Inspections and checklists5
- Defects and repairs5
- Fleet and maintenance5
- Load approval and assignment10
- Dispatch and delivery6
- Evidence and review7
- Shared and settings1
- Inspections
Pre-trip, post-trip and periodic inspection results
Linked to Vehicles, Drivers - Vehicles
Powered units and trailing equipment in the fleet
Linked to Organizations - Drivers
Licensed drivers available for load assignment
Linked to Organizations - Vehicle defects
Defects reported against a fleet asset
Linked to Team members, Vehicles, Inspections - Record attachments
Documents, photos and signature evidence attached to records
Linked to Organizations
- Vehicle defects
Defects reported against a fleet asset
Linked to Team members, Vehicles, Inspections - Inspections
Pre-trip, post-trip and periodic inspection results
Linked to Vehicles, Drivers - Vehicles
Powered units and trailing equipment in the fleet
Linked to Organizations - Team members
Dispatch, planning, safety and maintenance staff
Linked to Users, Organizations - Record attachments
Documents, photos and signature evidence attached to records
Linked to Organizations
- Vehicles
Powered units and trailing equipment in the fleet
Linked to Organizations - Drivers
Licensed drivers available for load assignment
Linked to Organizations - Maintenance plans
Preventive maintenance and service schedules
Linked to Vehicles - Fuel transactions
Fuel and energy purchases recorded per asset
Linked to Vehicles - Organizations
Carrier, broker, shipper and operating companies using the platform
- Loads
Planned and executed transport loads
Linked to Organizations, Team members, Transport partners - Review decisions
Approval, rejection and escalation decisions on records
Linked to Organizations, Team members - Load assignments
Driver and vehicle assignment for a load
Linked to Loads, Drivers, Vehicles - Drivers
Licensed drivers available for load assignment
Linked to Organizations - Vehicles
Powered units and trailing equipment in the fleet
Linked to Organizations - Inspections
Pre-trip, post-trip and periodic inspection results
Linked to Vehicles, Drivers - Vehicle defects
Defects reported against a fleet asset
Linked to Team members, Vehicles, Inspections - Load stops
Pickup, delivery and service stops on a load
Linked to Loads - Routes
Standard lanes between an origin and destination
Linked to Organizations - Transport partners
Carriers, brokers, 3PLs and shippers linked to transport work
Linked to Organizations
- Loads
Planned and executed transport loads
Linked to Organizations, Team members, Transport partners - Load assignments
Driver and vehicle assignment for a load
Linked to Loads, Drivers, Vehicles - Load stops
Pickup, delivery and service stops on a load
Linked to Loads - Tracking events
Position and milestone events reported against a load
Linked to Loads - Proof of delivery
Delivery confirmation captured at the stop
Linked to Loads, Load stops - Freight charges
Freight, accessorial and service charges billed against a load
Linked to Loads
- Operation receipts
Recorded operational outcomes awaiting verification
Linked to Organizations, Team members - Review decisions
Approval, rejection and escalation decisions on records
Linked to Organizations, Team members - Record attachments
Documents, photos and signature evidence attached to records
Linked to Organizations - Proof of delivery
Delivery confirmation captured at the stop
Linked to Loads, Load stops - Loads
Planned and executed transport loads
Linked to Organizations, Team members, Transport partners - Load assignments
Driver and vehicle assignment for a load
Linked to Loads, Drivers, Vehicles - Tracking events
Position and milestone events reported against a load
Linked to Loads
Keys and references
Preserve the original record identity and use stable references for imports. Match vehicle defects.Vehicle with the vehicle on its linked Inspections record. Match proof of delivery.Stop with the same Loads record identified by proof of delivery.Load. A similar display name is insufficient to establish either relationship.
Review decisions.source record and source table, operation receipts.source record and record attachments.related record are text references. Agree their formatting and resolve them explicitly during migration; they do not create a foreign-key relationship by themselves. Keep review decisions.Revision with the decision being imported. Team members.User supplies the identity mapping needed by owner-based personal work.
Use an agreed organization-level purchase currency convention when reporting fuel transactions.total amount; retain freight charges.Currency for each freight charge. Preserve fuel type and unit conventions rather than adding unlike volumes.
Migration order
- Load Organizations and Users, resolving the Users.User reference according to the target account mapping.
- Load team members, Drivers, Vehicles, transport partners and Routes with their organization links.
- Load Inspections, then vehicle defects with the originating inspection and responsible Owner; follow with maintenance plans and fuel transactions.
- Load Loads before load assignments, load stops and tracking events; then load proof of delivery and freight charges.
- Load review decisions, operation receipts and record attachments after resolving their textual source references. Reconcile the current operating state before using imported work in dispatch.
Set up Vehicle Inspection App your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.