Reservations and resources

A requested stay begins with a booking party and a selected resource. Property Manager can read the arrival and departure dates beside the party, planned occupancy and nightly rate. Keeping those details on one reservation gives the front desk a clear record to follow at arrival. The reservation number identifies the stay when several bookings share the same party or resource.

The resource record carries availability and operating condition. Before a manager confirms a request, compare the requested interval with the resource’s other commitments. A resource shown as cleaning or maintenance needs attention before a new stay can begin. Kitchen Manager compares the planned occupancy with the resource capacity and makes the confirmation decision; a request remains requested until that review is complete.

• Booking party. Ingredients holds the guest, group or company contact details associated with a stay.
• Stay. food batches links that party to the chosen Recipes resource and keeps the planned dates, rate and lifecycle status.
• Resource. Recipes carries the room, suite, venue, table or treatment space identity and whether it is available, occupied, cleaning or under maintenance.

Settle which resources can be booked, how each is identified, and who can confirm a requested stay. Decide how the property interprets the planned portions value for its occupancy practice and how the nightly rate is entered. Keep the party contact record distinct from the stay: the same returning guest can have separate reservations with different dates and resources.

For a pilot, select a resource with a known cleaning window and a booking party with a real contact. Ask Kitchen Manager to check a requested reservation against the resource calendar before confirming it. Keep rate plan records alongside the reservation for review; a rate reference does not silently replace the rate captured for a particular stay.

Suppose a guest requests a suite from Friday to Sunday. Property Manager finds or creates the party, selects the suite and records the requested dates. Kitchen Manager checks the interval, planned occupancy, resource and current request before confirming it. At arrival, Property Manager records check-in and the release sets the selected resource to occupied. Front Desk Agent follows the arrival from the updated stay. A second request for the same suite and overlapping interval should return for review before anyone confirms it.

A cancellation is a separate reservation outcome. It does not erase the party or resource history. If dates change, the manager should assess the revised interval rather than assuming the earlier confirmation covers it. The same discipline keeps a resource from appearing available while a stay remains active.

• Requested reservations — Review stays waiting for the manager’s confirmation.
• Active stays — Find confirmed and checked-in bookings with their parties and resources.
• Resources needing attention — See cleaning and maintenance states before accepting a new booking.

Follow reservation through checkout and prepare the first operating cycle.