> 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-record-actions-taken-against-the-missing-and-damage.md).

# How can I record actions taken against the Missing & Damage?

Yes, you can record actions taken specifically within the Missing & Damage transaction in the Housekeeping module.When reporting a missing or damaged item, the system requires you to enter the specific nature of the resolution:

* **Action Taken Details:** You must select how the incident is being handled, with options including charged to staff, charged to guest, or charged to Company.
* **Associated Financials:** You can record the amount charged to the relevant party, which is then passed to the front office.
* **Follow-up:** You can also specify a replacement date for the missing or damaged item.

These recorded actions are later tracked in the Missing & Damage Details report, which is designed to support timely corrective action by the concerned departments and maintain accurate inventory control


---

# 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-record-actions-taken-against-the-missing-and-damage.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.