> 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-nightaudit/fo-nightaudit-occupancy-analysis.md).
# Occupancy Analysis
Steps to view occupancy analysis report
### **Occupancy Analysis**
The Occupancy Analysis Report shows you the information of Rooms focusing on the occupancy and sold rooms. This report also supports Multi-Property features, where users can select the property from a group of properties.
**Room Type:** Types of Rooms Available for the day/month/year.
**Rooms:** *Available* - Available no. of rooms for sale.
*Revenue* - Revenue generated by the available rooms.
.png?alt=media)
**Sold:** *Rooms* - Total Rooms sold out of available rooms.
*Room%* - Percentage of Rooms sold from available rooms.
With Occupancy of Single, Double, Triple, and Quad.
.png?alt=media)
**Pax (Person):** No. of Pax in sold rooms (People in the room).
.png?alt=media)
**ARR**: Average Room Revenue of the sold rooms (Revenue Generated / Sold Rooms= ARR).
**ARP** : Average Revenue generated per Pax (Revenue Generated / PAX= ARP).
**RevPAR**: Revenue per available room, Avg. Revenue Generated for all available rooms (Revenue Generated / Total Available rooms for sale= RevPAR).
.png?alt=media)
This report will show you the collective data of Rooms Available and Sold for the day, for the month, and for the year as of now (Closed date).
**For the Day:**
.png?alt=media)
**For the Month:**
.png?alt=media)
**For the Year:**
.png?alt=media)
It reflects the Sales happening on available rooms and division of Average Sale per room and per person.
---
# 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-nightaudit/fo-nightaudit-occupancy-analysis.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.
