> 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-queries1/faq-on-queries/how-do-i-view-the-blocked-room-list-report-1.md).

# How do I view the Blocked Room List report

**How do I view the Blocked Room List report?**

To view the **Blocked Room List** report, navigate to:

**FRONT OFFICE → QUERIES → Blocked Room List**

This report is a comprehensive tool that helps manage and track room restrictions with the following features:

* **Historical and Current Data:** Displays all rooms that are currently blocked, as well as rooms that were blocked recently or previously.
* **Specific Filters:** Allows you to filter the list to show:
  * **Out of Order (OOO)** rooms.
  * **Out of Service (OOS)** rooms.
  * **Both OOO and OOS** rooms.
* **Sorting Options:** The report can be sorted by:
  * **Room No.**
  * **Room Type**

This report is especially useful for verifying room availability and status before the **Night Audit**, as maintenance-related room blocks can affect hotel statistical calculations.


---

# 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-queries1/faq-on-queries/how-do-i-view-the-blocked-room-list-report-1.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.