> 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-reserv/faq-on-reservations/how-does-the-forecast-track-room-nights-and-adr.md).

# How does the forecast track room nights and ADR?

The system tracks **room nights** and **ADR (Average Daily Rate)** through several forecasting and analytical reports by evaluating both existing reservations and future booking trends.

#### **Key Reports for Tracking Nights and ADR**

* **Business on Books Report:** This report specifically calculates revenue for a given month by considering three main factors: **Total Nights, Revenue Generated (or to be generated)**, and **ADR**. It can be filtered by room type and can exclude tentative bookings to focus only on confirmed business.
* **Forecast Report:** This tool tracks the **future contribution of various market segments** (such as corporate or individuals) for metrics including **Nights, Pax, ADR, ARP, and RevPAR** over a selected future date range.
* **Segment Analysis (MTD/YTD):** This report provides a detailed breakdown of **Nights** and **ADR** for different segments, showing data for the current day, month, and year to analyze performance trends.
* **History and Forecast Report:** It combines past performance **(rooms sold and revenue collected)** with **possible future sales** based on current bookings within a selected period, allowing for a comparison of actual vs. projected nights and revenue.

#### **Analytical Breakdowns**

* **Rate Code Analysis:** This provides information on **Room Nights** based on specific rates and their overall contribution to the property's revenue.
* **Average Length of Stay:** This metric indicates the average number of days a guest remains and analyzes how this duration affects both total revenue and **ADR**.
* **Room wise Income Analysis:** This gives a specific report on income generated by room number or type, showing **Room Nights, Revenues**, and **ARR (Average Room Rate)** for a selected month range.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-c8f037e8a171e2edfcb43c0193764f886ec55bda%2Fimage%20(1123).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-reserv/faq-on-reservations/how-does-the-forecast-track-room-nights-and-adr.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.
