> 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-missing-and-damage-detail.md).
# Missing & Damage Details
Steps to view missing & damage detail
The **Missing & Damage Details** report provides detailed information about items that are reported as missing or damaged during daily operations. This report helps departments maintain accurate inventory records by tracking item details, quantities, dates, and remarks related to the issue.
The report supports better accountability and enables timely corrective actions by the concerned departments.
## Steps to View Missing & Damage Details Report
Step 1: Open the **Housekeeping** module.
1. Click on **Reports**.
2. Select **Missing & Damage list**.
* The **Missing & Damages** screen will appear.
Step 2:Choose the required **From Date** and **To Date**.
1. Ensure the selected date range covers the period for which you want to view the report.
Step 3: After selecting the date range, click on the **Display** button.
* The system will generate and display the Missing & Damage Details report based on the selected dates.
---
# 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-missing-and-damage-detail.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.
