> 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/expected-departure.md).
# Expected Departure
The **Expected Departure** report displays the list of in-house guests who are scheduled to depart from the property. Users can view departures date-wise and apply filters such as market segment, reservation status, and more to search for specific reservations.
* This report also allows users to view past departure records for reference.
## Steps to View the Expected Departure Report
Step 1: Open the **Housekeeping** module.
1. Click on **Reports**.
2. Select **Expected Departure**.
* The **Expected Departure** screen will appear.
Step 2: To view departures for a different date:
1. Click on the **Calendar Icon**..png?alt=media)
2. Select the required departure date from the calendar.
* This helps in viewing departures based on the selected time period.
Step 3: Click on the **Filter Icon**..png?alt=media)
1. Select the required search criteria.
* This helps in locating specific reservations quickly.
Step 4: Click on the **Options icon**.
To add additional information to the report:
1. Select the required fields from the available list.
* The selected fields will appear as additional columns in the report. These columns display information entered during the reservation process.
Step 5: After applying all required filters and selections, click **Display** button.
Step 6: Click the **Excel icon** to download it in Excel format, or click the **Print icon** to open the print preview and proceed with printing.
---
# 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/expected-departure.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.
