> 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/to-manage-unassigned-arrivals-on-the-room-chart.md).

# To manage unassigned arrivals on the Room Chart

**How do I manage unassigned arrivals on the Room Chart?**

To manage unassigned arrivals on the **Room Chart** (also referred to as the **Calendar**), follow these steps:

1. **Access the Calendar:**\
   Navigate to **FRONT OFFICE → QUERIES → CALENDAR**.
2. **View Unassigned Arrivals:**\
   Click the **three dots (⋮)** in the top-right corner of the screen to view the list of unassigned arrivals for the current day.
3. **Open the Due-in Screen:**\
   Click the **Due-in** icon to access the list of guests who are due to arrive.
4. **Assign Rooms:**\
   From the **Due-in** screen, you can assign rooms by either:
   * **Manually** selecting a room number for each guest.
   * Clicking **Auto Assign** to let the system automatically allocate available rooms.

This feature enables you to quickly assign rooms and transition reserved guests to **In-House** status directly from the visual **Room Chart** interface.


---

# 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/to-manage-unassigned-arrivals-on-the-room-chart.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.