> 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/can-i-print-the-missing-and-damage-report.md).

# Can I print the Missing & Damage report?

While the sources provide detailed instructions on how to view and display the Missing & Damage report, they do not explicitly state that this specific report can be printed.According to the sources, the process for accessing this report is as follows:

* **Navigate to the Report:** Go to the HOUSE KEEPING module, select REPORTS, and then click on MISSING & DAMAGE.
* **Generate the View:** Select your desired Date range and click the Display button.

The report is designed to provide detailed information on items identified as missing or damaged during operations, tracking quantities, dates, and remarks to support inventory control and accountability.In contrast, the sources specifically mention printing capabilities for several other reports, such as:

* **Expected Arrivals and Departures:** Explicitly states these can be printed by clicking a specific icon.
* **Room Status Report and Blocked Rooms:** Includes options for users to choose additional details they want printed in the report.
* **In House Guest List:** Also mentions selecting options to be printed.

Since the specific "Missing & Damage" documentation only mentions the "Display" function, you may want to verify if a print icon appears on the screen once the report is displayed


---

# 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/can-i-print-the-missing-and-damage-report.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.