> 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-queries1/faq-on-queries/how-do-i-track-room-shifts-in-the-shifted-rooms-report.md).

# How do I track room shifts in the Shifted Rooms report?

To track room changes in the system, you use the Guest Shift Rooms report (also referred to as the Shifted Rooms report). This report allows you to monitor all room shifts that occurred on a specific day or within a selected time period.

**How to Use the Report**

**Reason Summary View:** If you enable the Reason Summary checkbox, the report will show a direct count of the number of shifts that occurred along with the specific reasons provided by staff.

**Detailed Information:** If you want to see a full, detailed report containing specific information about each individual shift, you must remove the Reason Summary checkbox.

This report is the primary tool for auditing room movements, whether they were performed via the visual drag-and-drop method on the Calendar or through the Change Room Menu.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-678a9e80142a23f65158a3b4b0c208ba97ddd01d%2FScreenshot%20From%202026-06-12%2013-00-04.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-queries1/faq-on-queries/how-do-i-track-room-shifts-in-the-shifted-rooms-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.
