> 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/hk-reports-lost-and-found-status.md).
# Lost & Found Status
Steps to view lost & found status
The **Lost & Found Status** report is used to track and monitor items that are either lost by guests or found within the hotel premises. This report helps hotel staff maintain proper records of guest belongings and hotel property that have been reported as lost or found.
## Steps to View Lost & Found Status
Step 1: Go to the **Housekeeping** main menu.
1. Select the **Reports** menu.
2. Click on **Lost & Found Status**.
* The **Lost & Found Status** screen will open.
Step 2: Select the **Location Type** from the available drop-down list.
Step 3: Choose the required **Status Type** from the available options then select the **Item Type** if required.
* These filters help refine the report based on specific requirements.
Step 4: After selecting the required filters, click **Display**. The system will display the **Lost & Found Status Report**.
---
# 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/hk-reports-lost-and-found-status.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.
