1. Resort Activity Booking
  2. Data model
Reference

The tables behind Resort Activity Booking

Resort Activity Booking 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

Guest stays:

Parties identify guests; Reservations link a guest to a Unit for dated lodging.

Availability and rates:

Units hold operational state and capacity; rate plans hold dated nightly terms by unit type.

Guided activities:

Activity departures link a guide in People to a scheduled session; activity reservations link that session to a stay.

Stay service and account:

Service tasks link work to a unit, stay and assigned person; folio charges and Payments link to a reservation.

Access:

People link staff to Users for named responsibility.

Every table, by feature

Stay reservations

4 tablesAbout this feature
  • Parties

    Guests and guest organizations booking stays and activities.

  • Reservations

    Guest stays booked against a party and unit.

    Linked to Parties, Units
  • Units

    Rentable lodging units and their housekeeping state.

  • Rate plans

    Dated nightly rate plans by unit type.

Units and rates

4 tablesAbout this feature
  • Units

    Rentable lodging units and their housekeeping state.

  • Rate plans

    Dated nightly rate plans by unit type.

  • Reservations

    Guest stays booked against a party and unit.

    Linked to Parties, Units
  • Service tasks

    Housekeeping, maintenance and guest service work for a unit.

    Linked to Units, Reservations, People

Guest service

4 tablesAbout this feature
  • Service tasks

    Housekeeping, maintenance and guest service work for a unit.

    Linked to Units, Reservations, People
  • Units

    Rentable lodging units and their housekeeping state.

  • Reservations

    Guest stays booked against a party and unit.

    Linked to Parties, Units
  • People

    Staff and guides who work resort stays and activities.

    Linked to Users

Activity departures

3 tablesAbout this feature
  • Activity departures

    Scheduled activity departures led by a guide.

    Linked to People
  • People

    Staff and guides who work resort stays and activities.

    Linked to Users
  • Activity reservations

    Guest bookings onto a scheduled activity departure.

    Linked to Activity departures, Reservations

Activity bookings

4 tablesAbout this feature
  • Activity reservations

    Guest bookings onto a scheduled activity departure.

    Linked to Activity departures, Reservations
  • Activity departures

    Scheduled activity departures led by a guide.

    Linked to People
  • Reservations

    Guest stays booked against a party and unit.

    Linked to Parties, Units
  • Parties

    Guests and guest organizations booking stays and activities.

Folios and payments

5 tablesAbout this feature
  • Folio charges

    Itemized charges posted to a stay folio.

    Linked to Reservations
  • Payments

    Confirmed and pending guest payments against a reservation.

    Linked to Reservations
  • Reservations

    Guest stays booked against a party and unit.

    Linked to Parties, Units
  • Parties

    Guests and guest organizations booking stays and activities.

  • Units

    Rentable lodging units and their housekeeping state.

Shared and settings

1 table
  • Users

    Users

    Linked to Users

Keys and references

Use the record numbers and codes to distinguish repeated stays and departures. The departure on an activity booking identifies the actual guided session; the reservation identifies the guest stay. Folio and payment entries use the same reservation reference for account review. A task carries both its unit and reservation, while its assignee points to a staff record. Preserve those links during import so calendars, boards and account views show the same case.

Migration order

  1. Import Users, People and Parties with their identifiers and contact details.
  2. Import Units and rate plans, checking unit types, capacity and dated rates.
  3. Import Reservations linked to guests and units.
  4. Import activity departures linked to guides, then activity reservations linked to departures and stays.
  5. Import service tasks, folio charges and Payments linked to their source stays.
  6. Review a representative stay from request through unit release and compare linked activity bookings and account entries.

Set up Resort Activity Booking your way.

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

How to get started