> 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-clear-dirty-room.md).
# Clear Dirty Room
Steps to clear dirty room
The **Clear Dirty Room** option is used to remove the “Dirty” status from rooms after housekeeping cleaning is completed.
**Important Note**
* If a room status is marked as **Dirty**, the system will not allow guest check-in for that room.
* Therefore, it is mandatory to clear the dirty room status before assigning the room to a guest.
## Steps to Clear a Dirty Room
Step 1: Go to the **Housekeeping Main Menu**.
1. Click on **Transaction**.
2. Select **Clear Dirty Room**.
* The system displays the list of rooms currently marked as **Dirty**.
Step 2: Select the **Dirty Room Number** that needs to be cleared.
Step 3: Provide the required narration or remarks(Example: Room cleaned and ready, Housekeeping completed, Inspection completed).
* Proper narration helps maintain housekeeping records and operational tracking.
Step 4: Click on the **Save** button to clear the dirty room status.
* Once saved successfully, the room status will be updated and the room will no longer appear 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/hk-transactions-clear-dirty-room.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.
