> 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-move-a-guest-to-another-room-on-the-calendar.md).
# How do I move a guest to another room on the calendar?
To move a guest to another room using the Calendar (Room Chart), you can utilise the visual drag-and-drop functionality.
**Moving a Guest via the Calendar**
1. **Navigate to the Calendar:** Go to **FRONT OFFICE > QUERIES > CALENDAR.**
2. **Execute the Move:** Locate the guest's current room on the chart. Drag and drop your cursor towards the right-hand side against the desired new Room number and Date to move the guest from one room to another.
**Alternative: Using the Change Room Menu**
If you prefer to perform the move through a standard menu process rather than the visual chart, follow these steps:
1. Navigate to **Front Desk Main Menu > Front Desk > Change Room Menu**.
2. **Select the Guest:** Choose the specific Guest Name for whom you would like to change the room.
3. **Choose the New Room:** Select the destination Room no.
4. **Provide a Reason:** Enter the reason for the move in the Narration field.
5. **Finalise:** Click Save to complete the process.
Regardless of which method you use, the system will record the change. You can later verify these movements by viewing the Shifted Rooms report, which lists all room shifts that occurred on a specific day along with the reasons provided.
---
# 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-move-a-guest-to-another-room-on-the-calendar.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.
