1. Bus / Coach Management
  2. Booking and departure data model
Reference

The tables behind Bus / Coach Management

Bus / Coach Management ships with 11 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
11
Features
6, plus shared settings
Change it
Add fields and tables in Proto

How the model is organised

Booking desk

Bookings retains record number, Subject, customer name, starts at, ends at, quoted amount USD, Status and Revision. Organization, Owner and Counterparty connect the operating context.

Resource reservations

Booking resources links its Parent booking to Resources, with Capacity, reserved units, setup minutes, cleanup minutes and line Revision. Resources belongs to Organizations and retains contact and eligibility information.

Departure planning

Route departures links to Bookings through Parent and to Organizations directly. Route, departs at, seat capacity and Crew describe the plan under its own Revision and Status.

Departure review

Review decisions links to the booking and Reviewer in team members. Source revision, Decision, Reason and operation key retain the review context.

Payment evidence

Payment evidence links each provider event to a booking with provider event ID, provider reference, Type, amount USD, occurred at and Verified.

Operations evidence

Operation receipts retains action results under the booking. Record attachments links files to the booking and uploaded by in team members, with Visibility and evidence type.

Organization and identity

Organizations defines the carrier context. Team members belongs to an organization and references the authenticated Users identity through User.

Every table, by feature

Booking desk

5 tablesAbout this feature
  • Bookings

    Charter and scheduled booking records with reserved resources

    Linked to Organizations, Team members, Resources
  • Organizations

    Carrier organizations operating the coach network

  • Team members

    Authenticated platform identities attached to an organization

    Linked to Organizations, Users
  • Resources

    Coaches, drivers and partner operators allocated to bookings

    Linked to Organizations
  • Record attachments

    Supporting files attached to bookings and departures

    Linked to Bookings, Team members

Resource reservations

4 tablesAbout this feature
  • Booking resources

    Reserved capacity lines attached to a booking

    Linked to Bookings, Resources
  • Resources

    Coaches, drivers and partner operators allocated to bookings

    Linked to Organizations
  • Bookings

    Charter and scheduled booking records with reserved resources

    Linked to Organizations, Team members, Resources
  • Organizations

    Carrier organizations operating the coach network

Departure planning

6 tablesAbout this feature
  • Route departures

    Staffed coach departure extensions requiring review and release

    Linked to Bookings, Organizations
  • Bookings

    Charter and scheduled booking records with reserved resources

    Linked to Organizations, Team members, Resources
  • Booking resources

    Reserved capacity lines attached to a booking

    Linked to Bookings, Resources
  • Resources

    Coaches, drivers and partner operators allocated to bookings

    Linked to Organizations
  • Organizations

    Carrier organizations operating the coach network

  • Team members

    Authenticated platform identities attached to an organization

    Linked to Organizations, Users

Departure review

6 tablesAbout this feature
  • Route departures

    Staffed coach departure extensions requiring review and release

    Linked to Bookings, Organizations
  • Review decisions

    Independent review decisions recorded against a booking revision

    Linked to Bookings, Team members
  • Operation receipts

    Durable receipts for executed operations and their results

    Linked to Bookings
  • Bookings

    Charter and scheduled booking records with reserved resources

    Linked to Organizations, Team members, Resources
  • Team members

    Authenticated platform identities attached to an organization

    Linked to Organizations, Users
  • Booking resources

    Reserved capacity lines attached to a booking

    Linked to Bookings, Resources

Payment evidence

3 tablesAbout this feature
  • Payment evidence

    Provider payment events retained as evidence for a booking

    Linked to Bookings
  • Bookings

    Charter and scheduled booking records with reserved resources

    Linked to Organizations, Team members, Resources
  • Record attachments

    Supporting files attached to bookings and departures

    Linked to Bookings, Team members

Operations evidence

6 tablesAbout this feature
  • Operation receipts

    Durable receipts for executed operations and their results

    Linked to Bookings
  • Record attachments

    Supporting files attached to bookings and departures

    Linked to Bookings, Team members
  • Review decisions

    Independent review decisions recorded against a booking revision

    Linked to Bookings, Team members
  • Bookings

    Charter and scheduled booking records with reserved resources

    Linked to Organizations, Team members, Resources
  • Route departures

    Staffed coach departure extensions requiring review and release

    Linked to Bookings, Organizations
  • Team members

    Authenticated platform identities attached to an organization

    Linked to Organizations, Users

Shared and settings

1 table
  • Users

    Users

    Linked to Users

Keys and references

Preserve record identifiers independently from human booking numbers and resource codes. Parent references on booking resources, route departures, review decisions, operation receipts, payment evidence and record attachments all identify Bookings. Files used in departure review are therefore located through the booking.

Bookings and route departures each have Revision. Review decisions.source revision and operation receipts.expected revision must be interpreted with their booking context and the action being performed. Define the exact departure association through the reviewed operation mapping and retained references during setup. Operation key appears in both decision and receipt records; effect references and external reference help trace the action result.

Organizations.Currency supports USD, CAD, EUR, GBP and MXN. Bookings.quoted amount USD and payment evidence.amount USD retain explicit USD meaning. Keep that distinction when mapping provider evidence.

Migration order

  1. Establish Users identities and Organizations with active state, currency and time zone.
  2. Link team members to their organization and authenticated user, then review intended access.
  3. Load Resources with organization, code, contact and eligibility information.
  4. Load Bookings with owners, resource counterparts, service windows and revisions.
  5. Attach booking resources and route departures to the correct bookings and reconcile the intended arrangements.
  6. Import review decisions, operation receipts, provider evidence and attachments only with their original references and meaningful revision context. Reconcile event identities before treating the history as complete.

Set up Bus / Coach Management your way.

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

How to get started