Reservations

Front Desk Agent records the guest, booked unit, party size, arrival and departure, and nightly rate on a reservation. A request has a meaningful Requested status until the property confirms it. Before moving it to Confirmed, compare the interval with other stays for that unit and check that the party fits its capacity. The room rate must be positive. If the dates are reversed or the unit is unavailable, return the precise problem while leaving the request as it was.

• Intake. Reservation Requests keeps new stays together with guest and unit details.
• Operating state. Stay Board follows requested, confirmed and occupied stays by status.
• Departure. Unit Occupancy places the arrival and departure dates beside the unit so staff can see the interval at handoff.

A guest record in Parties can represent a person or corporate account. The reservation carries the particular booking decision and its rate; it should not borrow a current plan later to rewrite a confirmed stay. At arrival, Front Desk Agent records the check-in, then the unit becomes occupied and the authorized room-night folio charge is appended for Finance Clerk to review. After Front Desk Agent records checkout, Finance Clerk compares posted charges with confirmed payments. An outstanding balance remains visible for the team to handle.

Agree how Front Desk Agent records a requested stay when the guest changes dates or party size. Keep the guest and unit references stable during corrections. Set who may confirm, check in, cancel and check out a reservation. Decide how the team handles a request while a unit is Cleaning or Maintenance. Rehearse access with a valid request and a conflicting request so the owner can explain why one remains Requested.

Enter a Friday arrival and Sunday departure for a guest party that fits the chosen unit. Confirm that no existing confirmed stay uses that unit for either night and that the nightly rate is positive. Front Desk Agent confirms the request, then records arrival. Repeat with a departure before arrival and with an overlapping unit booking. In each case, show the exact rejection reason and the unchanged Requested record. At departure, inspect posted charges and confirmed payments after checkout is recorded.

• Stay Board — Shows each active stay by its recorded lifecycle state.
• Reservation Requests — Shows new requests with dates, guest count and booked unit.
• Unit Occupancy — Shows confirmed and checked-in stays across arrival and departure dates.

Walk the linked records in the reservation lifecycle process. Use implementation to agree the first operating cycle and the data model to check the imported references.