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.
- Driver Safety & Training
- Data Model
The tables behind Driver Safety & Training
Driver Safety & Training ships with 14 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
- 14
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Coaching and Assessment
Coaching sessions references Loads through Parent and Organizations through Organization. Driver and incident reference are text; scheduled at, assessment score and Status describe the session.
Drivers and Eligibility
Drivers carries driver code, Name, eligibility until, external authority and Active. Load assignments.Driver references the actual driver record.
Assignment Readiness
Load assignments links Load, Driver and Vehicle with starts at, ends at and Status. Vehicles carries equipment class, capacity LB and Readiness. Vehicle defects.Vehicle links repair and release evidence to that vehicle.
Load Context and Delivery
Loads references Organization, Owner and Counterparty. Load stops.Parent identifies its load and retains stop order, window start, window end and actual times.
Evidence and Decisions
Record attachments.Parent and review decisions.Parent both reference Loads. Uploaded by and Reviewer reference team members; decisions retain source revision and operation key.
Completion and Follow-up
Operation receipts.Parent references Loads and retains Action, expected revision, result state, external and effect references and failure reason.
Every table, by feature
- Coaching and Assessment6
- Drivers and Eligibility4
- Assignment Readiness5
- Load Context and Delivery7
- Evidence and Decisions6
- Completion and Follow-up5
- Shared and settings1
- Coaching sessions
Driver safety coaching sessions closed through verified review.
Linked to Loads, Organizations - Loads
Freight loads with lifecycle, promised delivery and freight amount.
Linked to Organizations, Team members, Transport partners - Organizations
Carrier organizations that own operational records.
- Record attachments
Uploaded evidence files linked to a load.
Linked to Loads, Team members - Review decisions
Independent reviewer decisions on a frozen source revision.
Linked to Loads, Team members - Operation receipts
Stable operation keys and persisted result state for guarded actions.
Linked to Loads
- Drivers
Driver eligibility and external authority records.
- Load assignments
Nonoverlapping driver and vehicle commitments for a load.
Linked to Loads, Drivers, Vehicles - Loads
Freight loads with lifecycle, promised delivery and freight amount.
Linked to Organizations, Team members, Transport partners - Coaching sessions
Driver safety coaching sessions closed through verified review.
Linked to Loads, Organizations
- Load assignments
Nonoverlapping driver and vehicle commitments for a load.
Linked to Loads, Drivers, Vehicles - Drivers
Driver eligibility and external authority records.
- Vehicles
Fleet vehicles with capacity and readiness.
- Vehicle defects
Reported vehicle defects with repair and release evidence.
Linked to Vehicles - Loads
Freight loads with lifecycle, promised delivery and freight amount.
Linked to Organizations, Team members, Transport partners
- Loads
Freight loads with lifecycle, promised delivery and freight amount.
Linked to Organizations, Team members, Transport partners - Load stops
Ordered pickup and delivery stops for a load.
Linked to Loads - Load assignments
Nonoverlapping driver and vehicle commitments for a load.
Linked to Loads, Drivers, Vehicles - Transport partners
Eligible counterparties used on loads.
Linked to Organizations - Organizations
Carrier organizations that own operational records.
- Coaching sessions
Driver safety coaching sessions closed through verified review.
Linked to Loads, Organizations - Record attachments
Uploaded evidence files linked to a load.
Linked to Loads, Team members
- Record attachments
Uploaded evidence files linked to a load.
Linked to Loads, Team members - Review decisions
Independent reviewer decisions on a frozen source revision.
Linked to Loads, Team members - Operation receipts
Stable operation keys and persisted result state for guarded actions.
Linked to Loads - Loads
Freight loads with lifecycle, promised delivery and freight amount.
Linked to Organizations, Team members, Transport partners - Coaching sessions
Driver safety coaching sessions closed through verified review.
Linked to Loads, Organizations - Team members
Internal staff with role scope and organization membership.
Linked to Organizations, Users
- Operation receipts
Stable operation keys and persisted result state for guarded actions.
Linked to Loads - Coaching sessions
Driver safety coaching sessions closed through verified review.
Linked to Loads, Organizations - Review decisions
Independent reviewer decisions on a frozen source revision.
Linked to Loads, Team members - Loads
Freight loads with lifecycle, promised delivery and freight amount.
Linked to Organizations, Team members, Transport partners - Record attachments
Uploaded evidence files linked to a load.
Linked to Loads, Team members
Keys and references
Preserve existing record identifiers and business codes such as driver code, vehicle code and Loads.record number. Agree how coaching sessions.Driver identifies the intended driver. Transport Supervisor uses the load assignments links and Drivers.driver code to confirm the person and commitment; Dispatcher records the confirmed identity in the session.
Coaching sessions, attachments, decisions and receipts can all share a load parent. Agree how operation key, effect references and supporting material identify the exact session and the meaning of source revision. Matching Parent alone cannot identify which session was reviewed. Preserve the separately recorded revisions of Loads, load stops and coaching sessions.
Team members.User maps staff to Users, while team members.Organization records membership. Resolve My Loads through the signed-in user’s team member before comparing Loads.Owner. Define and test the permitted visibility of Drivers and Vehicles explicitly before giving staff access to those records. Users.User remains a self-reference.
Vehicle defects requires both repair evidence and released at. Retain the actual evidence-backed values and distinguish that history from Vehicles.Readiness. Assignment and stop timing fields are dates; confirm the runtime’s stored precision and time-zone interpretation before using interval comparisons.
Migration order
- Establish Organizations and Users, preserving user identity and self-reference mappings.
- Link team members to the intended users and organizations, then load transport partners with organization references.
- Load Drivers and Vehicles with their stable codes and external authority or fleet references.
- Create Loads with owner and partner links, then load stops and load assignments with resolved parents and resources.
- Load coaching sessions with the correct load and organization and an explicitly reconciled driver description.
- Attach vehicle repair history and load evidence, preserving the actual reviewed subject, revision and operation identities in decisions and receipts.
Set up Driver Safety & Training your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.