1. School Bus Tracking
  2. Data model and import order
Reference

The tables behind School Bus Tracking

School Bus Tracking 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
Change it
Add fields and tables in Proto

How the model is organised

Bus runs:

Loads connects the organization, owner, transport partner, promised delivery and actual pickup and delivery.

Stops and assignments:

Load stops orders the route; load assignments connects a dated interval to Drivers and Vehicles.

Student boarding:

Student boardings links an operational boarding observation to Loads and Organizations.

Resource readiness:

Vehicles and vehicle defects retain readiness, severity, repair evidence and release date.

Review and evidence:

Review decisions, record attachments and operation receipts remain linked to their parent Loads record.

Operating parties:

Organizations, team members, Users and transport partners identify who owns, serves and reviews work.

Every table, by feature

Bus runs

5 tablesAbout this feature
  • Loads

    Planned and executed school bus runs.

    Linked to Organizations, Team members, Transport partners
  • Load stops

    Ordered pickup and drop-off stops on a bus run.

    Linked to Loads
  • Load assignments

    Driver and vehicle commitments for a bus run.

    Linked to Loads, Drivers, Vehicles
  • Operation receipts

    Durable receipts for each guarded operation attempt.

    Linked to Loads
  • Review decisions

    Independent approve, reject and return decisions.

    Linked to Loads, Team members

Stops and windows

3 tablesAbout this feature
  • Load stops

    Ordered pickup and drop-off stops on a bus run.

    Linked to Loads
  • Loads

    Planned and executed school bus runs.

    Linked to Organizations, Team members, Transport partners
  • Student boardings

    Verified student boarding records for a bus run.

    Linked to Loads, Organizations

Assignments and readiness

5 tablesAbout this feature
  • Load assignments

    Driver and vehicle commitments for a bus run.

    Linked to Loads, Drivers, Vehicles
  • Drivers

    Licensed bus drivers and their eligibility.

  • Vehicles

    School buses and their readiness.

  • Vehicle defects

    Reported bus defects and repair state.

    Linked to Vehicles
  • Loads

    Planned and executed school bus runs.

    Linked to Organizations, Team members, Transport partners

Student boardings

5 tablesAbout this feature
  • Student boardings

    Verified student boarding records for a bus run.

    Linked to Loads, Organizations
  • Loads

    Planned and executed school bus runs.

    Linked to Organizations, Team members, Transport partners
  • Load stops

    Ordered pickup and drop-off stops on a bus run.

    Linked to Loads
  • Record attachments

    Files and evidence linked to a bus run.

    Linked to Loads, Team members
  • Review decisions

    Independent approve, reject and return decisions.

    Linked to Loads, Team members

Review and evidence

5 tablesAbout this feature
  • Review decisions

    Independent approve, reject and return decisions.

    Linked to Loads, Team members
  • Operation receipts

    Durable receipts for each guarded operation attempt.

    Linked to Loads
  • Record attachments

    Files and evidence linked to a bus run.

    Linked to Loads, Team members
  • Loads

    Planned and executed school bus runs.

    Linked to Organizations, Team members, Transport partners
  • Team members

    Dispatchers, supervisors and administrators with app access.

    Linked to Organizations, Users

Organizations and partners

5 tablesAbout this feature
  • Organizations

    School districts and operators that own the transportation records.

  • Team members

    Dispatchers, supervisors and administrators with app access.

    Linked to Organizations, Users
  • Users

    Users

    Linked to Users
  • Transport partners

    Contracted bus operators and transport providers.

    Linked to Organizations
  • Loads

    Planned and executed school bus runs.

    Linked to Organizations, Team members, Transport partners

Keys and references

Use stable organization, partner, driver, vehicle and run identifiers. Import child records through their exact parent reference, not a similar route label. Preserve run revisions, decision source revisions and operation keys when migrating history. A boarding entry’s Parent and Organization should agree with the run it describes. Keep times in the correct organization context.

The model contains 14 tables. Saved lists such as Run status list and Boardings awaiting review are views over their source tables. They do not introduce another storage record.

Migration order

  1. Load Organizations and Users, then team members with their organization and user links.
  2. Load transport partners, Drivers and Vehicles; attach vehicle defects to the correct Vehicles.
  3. Load Loads with stable numbers, organization, owner and counterparty references.
  4. Load ordered load stops, dated load assignments and student boardings against their parent Loads records.
  5. Load record attachments, review decisions and operation receipts with source revisions and keys intact; reconcile totals and permission boundaries before opening daily work.

Set up School Bus Tracking your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started