Reservations

A reservation joins a guest party, a bookable unit, arrival and departure dates, party size, nightly rate and status. Property Manager keeps the guest and unit records usable before Front Desk Agent handles the request. Start with the actual guest party and the unit the team intends to hold. The stay record then becomes the shared reference for check-in, service work, outlet activity, payments and checkout.

A request is not yet a confirmed stay. Front Desk Agent reviews the date interval, unit capacity and overlapping nights. Confirmation locks the unit while it checks the interval again. If the source revision has changed, the decision returns a conflict for review. A repeated command with the same operation key and input returns the original saved result, which helps the desk recover from an uncertain response without creating a second decision.

• Requests. Property Manager captures the party, intended unit, dates and party size with a requested status.
• Confirmation. Front Desk Agent confirms only after the unit and nights pass the capacity and overlap checks.
• Stay history. The same reservation remains linked through check-in, outlet service, folio charges and checkout.

The reservation board shows active lifecycle states without making every desk user search the full history. Confirmed arrivals are a focused handoff for the next operating shift. In-house stays show the desk which guest and unit already have an active stay. A cancelled reservation is kept in the status history rather than being treated as an occupied unit.

Agree who maintains guest parties and unit records, who may submit a confirmation, and how the front desk resolves a changed request. Set the unit types and capacities before a trial confirmation. Check the meaning of the arrival and departure dates with the team: the overlap test treats arrival as included and departure as excluded. That allows a departure and a new arrival to share a calendar day when the unit can be prepared between them.

Choose a representative stay with a party size close to capacity and another with overlapping nights. The desk should be able to explain the result from the unit and dates on the record. Rate plans carry dated unit-type prices and minimum-night rules; agree how the nightly rate recorded on the reservation is chosen and reviewed in the property’s operating practice.

A family requests a unit for a weekend. Property Manager records the guest party, unit, arrival and departure dates and party size. Front Desk Agent opens the request, checks the unit’s capacity and confirms it. Another agent tries to confirm an overlapping stay for the same unit. That attempt must stop before a second confirmed booking is saved. If the first agent repeats the same confirmation after a lost response, the original result should return.

At arrival, the confirmed record should lead the desk to the same guest and unit. The team should find its service tasks and restaurant or spa bookings from that reservation. Finance Officer should use that same identity when reconciling charges and receipts at departure.

• Requested Stays — Requests awaiting the desk’s date, capacity and guest checks.
• Confirmed Arrivals — Confirmed stays to prepare for arrival.
• Reservation Board — Active stays grouped by lifecycle status.

Follow stay confirmation, arrival and service and checkout.