> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/reservations-and-operations/cleaning.md). # Cleaning Cleaning holds your cleaning teams, their people and listings, and a calendar of each team's cleanings with assignment and inspection. ## Cleaning dashboard The **Cleaning** page shows each cleaning team as a card. | Element | What it shows | | ---------------------------------------------- | ------------------------------------------------------------------------------------------ | | Name and description | The name of the team and your note about it. | | **Supervisor inspection** / **Inspection off** | Whether a supervisor inspects the cleanings of the team. | | **Assignment required** / **Open to team** | Whether each cleaning must be assigned to a member, or any member of the team can take it. | | **Supervisors**, **Members**, **Listings** | The number of supervisors, team members and linked listings. | | **Linked listings** | The nicknames of the linked listings, or *No listings linked.* | **Create** adds a team with a **Name** and an optional **Description**. ## Team information A click on a card opens the team. **Configuration** holds its settings. | Field | What it does | Limits | | ------------------------- | ---------------------------------------------------------------------------------------------------- | --------- | | **Name** | The name of the team, on the dashboard and on every reservation. | Required. | | **Description** | A note for your team, for example working hours, contact person or language. | Optional. | | **Supervisor inspection** | Completed cleanings wait for a supervisor's inspection. | None | | **Require assignment** | Each cleaning must be assigned to a team member. When off, the cleanings are open to the whole team. | None | ## Supervisors **Supervisors** are the users who oversee the work of the team. They are chosen from the users of your organization. ## Team members **Team Members** are the cleaners who pick up the tasks in the Guestway app. See [Cleaning tasks](/guestway-mobile-app/cleaning.md). ## Linked listings **Listings** are the listings the team cleans. A listing can be linked to one team only. Linking it to another team removes it from the previous team. Deleting a team cannot be undone. It cancels every task of the team, unlinks its listings and removes the team. ## Cleaning calendar The page of a team shows its cleanings. | Field | What it does | Limits | | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | | Date | The day, week or month shown, with arrows to the previous or next one. | None | | Calendar view | **Day**, **Week** or **Month**. | The month shows the number of cleanings and of unassigned cleanings per day. | | Status filter | **All**, **Open tasks**, **Awaiting inspection** or **Completed tasks**, each with a count. | None | | List | **All listings**, **Group by priority**, **Group by floor**, **Group by service** or **Group by assignee**. | **Group by assignee** only when tasks can be assigned. | | Progress | How many cleanings are assigned (for example *3 of 8 assigned*), or done (*5 of 8 cleanings done*, or *done* and *awaiting* with inspection). | None | | **Assign** | Assigns the selected cleanings to a team member. | None | The priority of a cleaning comes from its deadline: the next check-in. A cleaning without a deadline that day has a low priority. The closer the deadline, the higher the priority. ## Task details A click on a cleaning opens **Task detail**. | Area | What it shows | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | **Cleaning Job** | The listing and its address, the team, the priority and the number of guests. | | Owner warning | *The owner of the property will be the next guest. Please take extra care when cleaning.* | | Timeline | The check-out of the previous guest (**Checked out** once done), the check-in of the next guest (**Checked in** once done) and the **Deadline**. | | **Assignees** | The team members of the cleaning. **Assign** adds one. | | **Required** | The services that must be prepared, with the quantity, for example *4 ยท Baby Crib*. | | **Consumables** | The consumables to bring, with the quantity. | | **Bed Types** | The beds of the listing. | | **Notes** | The notes of the task. | Services come from [service templates](/guest-experience/service-templates.md) with **Show on clean task** on. ## Related * [How to create a cleaning team](/reservations-and-operations/cleaning/how-to-create-a-cleaning-team.md) * [How to assign a cleaning task](/reservations-and-operations/cleaning/how-to-assign-a-cleaning-task.md) * [Cleaning tasks](/guestway-mobile-app/cleaning.md): the cleaner's side, in the Guestway app. * [Multi-calendar](/reservations-and-operations/multi-calendar.md): the cleaning status of each unit. * [Review center](/reviews-and-analytics/review-center.md): the cleaning performance in reviews. --- # 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://docs.guestway.io/reservations-and-operations/cleaning.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.