> 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/hk-transactions-tag-room-as-dirty-inspected-pickup.md).
# Tag room as Dirty/Inspected/ Pickup
Steps to tag room as dirty inspected pickup
The **Tag Room as Dirty / Inspected / Pickup** option is used to update the housekeeping status of rooms. This feature helps the housekeeping department track room cleaning progress and room readiness efficiently.
**Important Note**
* The system allows rooms to be marked as **Dirty** even if the room is **Occupied** or **Blocked**.
* In such cases the room colour/status remains the same based on occupancy or block status.
* However, the room will display a **“Dirty”** text indication.
## Steps to Tag a Room as Dirty / Inspected / Pickup
Step 1: Go to the **Housekeeping Main Menu**.
1. Under **Transactions,** select **Tag a Room as Dirty.**
* The Room Status screen will appear displaying the list of available rooms.
Step 2: Select the required room status type.
Step 3: Choose the room for which the status needs to be updated.
Step 4: Click on the **Save** button.
* Once saved successfully, the selected room status will be updated in the system.
---
# 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/hk-transactions-tag-room-as-dirty-inspected-pickup.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.
