> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/front-office-module/fo-masters/faq-on-masters/what-are-the-rules-for-overbooking-a-room-type.md).

# What are the rules for overbooking a room type

**What are the rules for overbooking a room type?**

To manage overbooking for a specific **room type**, configure the settings in the **Room Type Master** under the **Front Office** module. If your property allows reservations beyond the available physical inventory, enable the **Overbooking** option for that room category.

Once overbooking is enabled, the following rules apply:

#### **1. Enter the Overbooking Percentage**

* Specify the **overbooking percentage** permitted for the selected room type.
* This defines the allowable number of reservations beyond the available rooms.

#### **2. Select the System Parameter**

* Choose the appropriate **system parameter** that determines how the overbooking logic is applied.

#### **3. Configure Occupancy Limits**

* Define the maximum occupancy allowed for the room type, including:
  * **Maximum Adults**
  * **Maximum Children**

#### **4. Specify Maximum Allotted Persons**

* If required, set the **maximum allotted persons per room** to enforce additional occupancy restrictions.

These settings allow the system to calculate room availability accurately while supporting controlled overbooking based on your property's operational policies.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rbsgo.com/front-office-module/fo-masters/faq-on-masters/what-are-the-rules-for-overbooking-a-room-type.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.