> 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/fo-queries1-monthwise-room-position.md).
# Month wise Room Position
Steps to view month wise room position report
**MONTH WISE ROOM POSITION**
Month wise room position shows the availability of rooms for a particular month. This report can be viewed room type-wise as well. This report helps in planning occupancy based on the data shown in the report.
1.To view the report, go to **“FRONT OFFICE”** module and select the following icon.
2.To view occupancy based on filters, choose the filter from top left hand side as shown below
3.To see the room allocation status, select the drop down as shown below
4. Select property from the dropdown or choose **All Properties** to view the Room Position for all the properties as shown below
5. To see the Room Position details for **Past Date** or to add more filters like ADR or RevPAR, choose rom the dropdown as shown below
---
# 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/fo-queries1-monthwise-room-position.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.
