> 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-reports2/faq-on-advanced-reports/which-reports-help-track-guest-upgrades-across-the-property.md).
# Which reports help track guest upgrades across the property?
The primary tool for tracking these instances is the **Upgrade Audit report**, which specifically displays in-house guest room upgrades for a selected date or date range. This report can be sorted based on various criteria and provides a date-wise view of all upgrades performed across the property.
In addition to the specific upgrade audit, you can use several other reports to monitor room moves and pricing variances:
**Guest Shift Rooms Report:** This report tracks all room shifts that occurred during a specific period. By selecting the Reason Summary checkbox, you can view a direct count of shifts categorized by their specific reasons, such as upgrades. Removing this checkbox provides a more detailed report on each individual move.
**Occupancy Statistics Report:** This report features a Difference % filter. Enabling this option adds a column that analyzes the percentage difference between the actual Tariff Charged and the room's Rack Rate. This is useful for identifying "complimentary upgrades" where the guest is in a high-value room but paying a lower rate.
**Amend Guest Stay Audit:** This audit log provides details on any modifications made to a guest's stay by staff, including the specific amendment reason provided at the time of the change.
**Guest Shift Rooms Report** (Analysis): As mentioned in our conversation history, this report can be generated from the Queries menu to see shifts as a reason summary or as a detailed log for in-depth 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-reports2/faq-on-advanced-reports/which-reports-help-track-guest-upgrades-across-the-property.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.
