> 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/housekeeping/housekeeping-module/hk-reports/faq-on-reports/where-do-i-track-expected-arrivals.md).

# Where do I track expected arrivals?

To track Expected Arrivals, you should use the specific report located within the Housekeeping module. This report displays upcoming confirmed reservations that have not yet arrived.To access and manage this information, follow these steps as outlined in the sources:

* **Navigation:** Go to the Housekeeping module, select Reports, and then click on Expected Arrivals.
* **Viewing Options:**
  * **Date Range:** You can view day-wise arrivals or change the date to view past date arrivals.
  * **Filters:** Use the filter icon to search for specific reservations based on criteria like market segment or reservation status.
  * **Additional Details:** To see more information, you can select specific fields to add columns to the report, provided that information was entered during the initial reservation.
* **Output:** The report can be converted to Excel or printed directly from the system


---

# 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/housekeeping/housekeeping-module/hk-reports/faq-on-reports/where-do-i-track-expected-arrivals.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.