> 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-queries2/faq-on-advanced-queries/how-do-the-history-and-forecast-reports-differ.md). # How do the History and Forecast reports differ? The History and Forecast and Forecast reports differ primarily in their scope of time and the specific data points they analyse. **History and Forecast Report** This report is a dual-purpose tool that provides a combined view of the property's performance by looking at both the past and the future within a single selected period. * **Past Data:** It provides insights into all rooms sold and revenues already collected. * **Future Data:** It shows possible sales in the future based on current bookings. **Forecast Report** Unlike the combined view above, the Forecast report is specifically focused on future trends and segment performance. * **Analytical Focus:** It tracks the future contribution of different segments (such as corporate, individual, etc.) for metrics like Nights, **Pax** (number of guests), **ADR** (Average Daily Rate), **ARP**, and **RevPAR.** * **Multi-Property View:** It is often used to provide a consolidated, high-level Multi-Property report. **Occupancy Forecast Report** While similar to the standard forecast, the Occupancy Forecast report specifically targets room utilisation. * **Reservation Types:** It shows future occupancy based on both confirmed and tentative reservations. * **Revenue Visibility:** It highlights specific guest names and the specific revenue expected to be generated from those future bookings. In summary, you would use the History and Forecast report to compare how your past performance aligns with your upcoming business, whereas the Forecast or Occupancy Forecast reports are used strictly for forward-looking strategic planning and segment analysis.
--- # 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-queries2/faq-on-advanced-queries/how-do-the-history-and-forecast-reports-differ.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.