> 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-analysis/fo-analysis-occupancy-forecast.md).
# Occupancy Forecast
Steps to view occupancy forecast report
**Navigation Path:**
1. Navigate to the **Front Office** module.
2. Click the **Analysis** menu.
3. Select **Occupancy Forecast.**
**Occupancy Forecast**
The Occupancy Forecast report shows you the information about the Future Occupancy based on reservations made (including tentative). It shows the Guest Name and Revenue to be generated out of these future bookings. You can select the period of future dates for generating the report.
**With Compl/HU:** This shows the report including Complimentary Booking or House Use or Management Booking.
**With Day Use:** If you click on this, the report will show the forecast for Day Use Guests.
.png?alt=media)
Columns and rows can be added and sorted based on two types of Filters provided. Options Filter (Checkbox) and Funnel Filter (Dropdown specific).
**Options Filter:** It adds the checked box information, by adding a corresponding column within the report in a predefined sequence, Such as Business Source, Segment, Room type etc. This will always show you all data of all future reservations.
**Funnel Filter:** This you can use to filter and sort the report based on your requirement. For example if you want a report based on one source of booking only etc. In this you can select specific Company, Travel Agent etc. or select all.
---
# 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-analysis/fo-analysis-occupancy-forecast.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.