> 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-transactions/faq-on-transaction/how-can-i-mark-a-room-as-dirty.md).

# How can I mark a room as dirty?

To mark a room as dirty, you should use the Tag room as Dirty/Inspected/Pickup option within the Housekeeping module. Following these steps will update the room's status:

1. **Access the Menu:** Go to the Housekeeping Main Menu.
2. **Navigate to Transactions:** Click on Transaction > Room Blocking.
3. **Select Rooms:** Choose the specific types of rooms you wish to update.
4. **Finalize:** Click the Save button to tag the selected room as dirty.

**Key Considerations:**

* **Status Indicators:** The system allows you to mark a room as "Dirty" even if it is currently occupied or blocked. In these instances, the visual status color (for occupied or blocked) will remain unchanged, but the room will show a "dirty" text indication.
* **Operational Impact:** It is important to clear the dirty status before a new guest arrives, as the system will not allow a check-in for any room currently marked as "Dirty"


---

# 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-transactions/faq-on-transaction/how-can-i-mark-a-room-as-dirty.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.