> 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/how-can-i-see-past-date-arrivals.md).

# How can I see past date arrivals?

To view arrivals from a past date, you must access the Expected Arrivals report within the Housekeeping module. This report is designed to show upcoming confirmed reservations but also allows you to look back at previous dates.Follow these steps to see past date arrivals:

1. **Navigate to the Report:** Go to the HOUSE KEEPING module, select REPORTS, and then click on EXPECTED ARRIVALS.
2. **Change the Date:** Click on the calendar/date icon and select the specific past date you wish to view.
3. **Select Past Arrivals:** Ensure you select the specific viewing option (represented by an icon in the system) designated for displaying past date arrivals in the report.
4. **Display the Report:** Click the view/display icon to generate the report once your date and filters are applied.

Additionally, you can use the filter icon to search for specific reservations or click the more details icon to add specific columns of information that were entered during the initial reservation process. The resulting report can be printed or converted to Excel


---

# 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/how-can-i-see-past-date-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.