> 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/housekeeping/housekeeping-module/hk-queries1/hk-queries1-room-status.md).
# Room Status
Steps to view room status
The **Room Status** report provides a complete overview of the current status of all hotel rooms. This report helps hotel staff monitor room occupancy, room availability, housekeeping conditions, and blocked rooms in a single screen.Each room status is displayed with a separate color for easy identification and quick monitoring.
* The report can also be sorted floor wise, group wise, room type wise
* This feature is highly useful for the Front Office, Housekeeping, Reservation, and Management departments.
## Steps to Open Room Status
Step 1: Go to the **Housekeeping** main menu.
1. Select the **Queries** menu.
2. Click on **Room Status**.
* The **Room Status** screen will open.
Step 2: Click on the **Advanced Filter** option.
* The Advanced Filter allows users to filter room details based on specific criteria.
* Select the required sorting option from the available list.
Step 3: After selecting the sorting and filter options, the Room Status details will be displayed on the screen.
**Important Note:**
* Each room status is displayed using a separate color for quick identification.
---
# 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/housekeeping/housekeeping-module/hk-queries1/hk-queries1-room-status.md?ask=&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.
