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.
- Dance Studio Management
- Features
- Guest bookings
Guest bookings
Keep guest bookings tied to each guest stay and its operating decisions.
OverviewConfirmed arrivals×
Dance Studio Management · Guest bookings
New
Confirmed arrivals
Checked in waits for the front desk agent
| Reservation number | Guest | Unit | Arrival date | Departure date | Status | |
|---|---|---|---|---|---|---|
| BKN-19766 | STD-15536 | 07 Oct | 15 Oct | Confirmed | ||
| BKN-34272 | STD-33365 | 13 Oct | 18 Oct | Confirmed | ||
| BKN-77854 | STD-27913 | 09 Oct | 13 Oct | Confirmed | ||
| BKN-13979 | STD-28530 | 21 Oct | 27 Oct | Confirmed | ||
| BKN-58688 | STD-29062 | 23 Oct | 01 Nov | Confirmed |
6 of 6 records
STD-15536Bookings · BKN-19766
ConfirmedArrival date07 Oct
Departure date15 Oct
What you can do
Keep the work anchored to a stay
A booking brings the guest party, studio, arrival, departure, party size and agreed rate into one reservation. The Property Manager records the request and can correct the source details. The Front Desk Agent checks the current dates and studio capacity before confirmation. Because the departure day is outside the booked-night interval, a request that begins on another stay’s departure day can be evaluated without treating that shared date as an overlapping night.
The Business Overview lets the desk narrow bookings by guest party, studio and status, then open a reservation for the decision. A Requested stay is a request, not a committed unit. Confirmed, checked in, checked out and Cancelled describe different points in the stay; charges and payments have their own statuses. Keeping those decisions distinct makes it possible to explain why a guest has a reservation while a receipt is still pending.
How the work is organized
- Keep identity. Begin with the reservation and confirm the guest party and studio before updating a related record.
- Separate decisions. Record preparation, review and the resulting status as distinct steps where the workflow calls for them.
- Trace the handoff. Leave the linked task, outlet activity, charge or receipt on the stay so the next role can check its source.
What to agree during setup
Choose who records a new guest party and who corrects a booking after a date change. The Property Manager should agree how staff select a studio and capture its capacity before the desk confirms the stay. Set the minimum information for a request: guest, unit, arrival, departure and party size. Decide who compares a dated rate plan with the stay and who records the agreed rate on the booking.
Rehearse one clear interval and one that overlaps a Confirmed stay. The Front Desk Agent must check the current booking revision and booked nights before committing the unit. If the request changes while that check is under way, staff should repeat it for the new dates. Keep the booking Requested until the conflict is resolved; do not treat an earlier availability check as the final decision.
Check the handoff on an actual case
The Property Manager changes the requested dates after the desk has checked availability. The Front Desk Agent reads the current booking again and tests the new arrival-to-departure interval against confirmed stays for that studio. If a booked night overlaps, the request remains Requested. If the interval is clear and the guest count fits the studio capacity, the desk confirms the current request. Repeating the same confirmation returns its saved result; changed input needs a fresh check.
What your team sees
- Requested bookings — Bookings awaiting the capacity and date check before confirmation.
- Booking date schedule — Confirmed and checked-in stays with their arrival and departure dates.
Follow the work through
Use the related process to rehearse the next decision and the data model to check the linked records.
What it keeps track of
Data model- Bookings
- Stay and resource bookings with arrival, departure, party size and nightly rate.
- Members
- Guests, groups, companies and other booking parties.
- Studios
- Bookable inventory: rooms, suites, venues, tables, treatment rooms and other resources.
- Membership plans
- Dated nightly rate plans by unit type with minimum stay rules.
Who uses it
Permissions- Property Manager
- , Front Desk Agent.
Set up Dance Studio Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.