> 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/faq-on-night-audit/how-do-i-use-the-occupancy-analysis-report.md).

# How do I use the Occupancy Analysis report?

The Occupancy Analysis report is a management tool designed to provide a focused look at room occupancy and sales performance. It allows you to analyse room utilisation across different time frames and supports multi-property viewing, enabling you to select specific properties or a group of properties for analysis.

**Key Metrics Tracked**

The report breaks down data by Room Type and includes the following performance indicators:

* **Rooms (Available & Revenue)**: Displays the number of rooms available for sale and the total revenue they generated.
* **Sold Rooms:** Shows the total number of rooms sold and the Room% (the percentage of total available rooms that were sold).
* **Occupancy Breakdown:** Categorises sold rooms by their specific occupancy type, such as Single, Double, Triple, and Quad.
* **Pax (Person):** Tracks the total number of guests residing in the sold rooms.

**Financial Statistics**

The report automatically calculates critical financial ratios that reflect the division of average sales per room and per person:

* **ARR (Average Room Rate)**: This is the revenue generated divided by the number of sold rooms.
* **ARP (Average Revenue per Pax)**: This is the revenue generated divided by the total number of guests (Pax).
* **RevPAR (Revenue per Available Room)**: This is the average revenue generated for all available rooms, calculated as Revenue Generated divided by Total Available rooms for sale.

**Time frame Analysis**

The report provides collective data for three distinct periods based on the last closed accounting date:

* **For the Day:** Current daily performance.
* **For the Month:** Cumulative performance for the current month.
* **For the Year:** Cumulative performance for the current year.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-4ed62b54553f92d6f9291cc1de33eb43e2ea261e%2Fimage%20(1391).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/faq-on-night-audit/how-do-i-use-the-occupancy-analysis-report.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.
