> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kitospace.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Cleaning Missions

> How housekeeping missions are planned from bookings, assigned to staff, worked through a checklist and completed.

## What is a Mission?

A **mission** is a housekeeping task attached to a unit — the turnover clean between one stay and the next. Every mission carries its unit, a deadline, a priority and a checklist.

Missions live under **Cleaning** in the sidebar. The entry appears only when the cleaning add-on is active and cleaning is switched on for at least one property.

## Where do missions come from?

Missions are planned for you from your bookings. When a reservation is confirmed, a **Scheduled** turnover mission is created for the end of that stay. It can be assigned ahead of time, but not cleaned yet — the guest is still in the room.

When the guest checks out, that mission becomes **Pending**: the unit is marked dirty and the clean is ready to pick up. There is no separate "new mission" button, because the booking is what creates the work.

<Tip>
  This booking-to-cleaning link is the **Auto-link missions** rule, in the **Cleaning** section of a property's operational rules — alongside **Cleaning enabled** and the **Simple / Advanced** mode. Turn it off and cleaning tasks stop being tied to turnovers automatically. Operational rules are set at the top of a property and inherit down to every unit beneath it.
</Tip>

## Mission statuses

| Status          | What it means                                                                                                                        |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Scheduled**   | Planned turnover for a confirmed booking. The guest is still staying, so the unit is not dirty and the clean cannot be finished yet. |
| **Pending**     | The guest has checked out. The unit is dirty and the clean is ready to start.                                                        |
| **Assigned**    | One or more staff members are responsible for the clean, but nobody has started.                                                     |
| **In progress** | The clean has started. The unit reads as *Cleaning*.                                                                                 |
| **Completed**   | The clean is done. The unit is *Ready* again, and a stay waiting on turnover finishes by itself. Final.                              |
| **Escalated**   | A problem was reported that blocks the clean. Final — it needs a person, not a status change.                                        |

Missions only move forward: **Scheduled → Pending → Assigned → In progress → Completed**. A scheduled mission can be assigned before check-out, a pending one can be started without being assigned first, and any unfinished mission can be escalated.

## How does work reach a cleaner?

A mission can be assigned to one or more staff members, and unassigned again — every change raises a toast with an **Undo** button.

When nobody is assigned to a unit directly, Kitospace looks up the property hierarchy to find who to reach, and the **Assignment strategy** rule decides how far it looks:

| Strategy         | Behaviour                                                                                                                                  |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **First match**  | Stops at the nearest level above the unit that has someone assigned. The closest responsible person gets it, and nobody else is pulled in. |
| **Accumulation** | Keeps going to the top, collecting assignees at every level. Everyone responsible for that part of the property is included.               |

First match is the default and suits a property where each floor or building has a clear owner. Accumulation suits smaller teams who would rather everyone above the unit knew.

## What does the cleaning list show?

The **Cleaning** page lists your missions as cards showing the unit, the deadline (or *Planned turnover* for a scheduled one), the priority and the status. The most urgent work sorts to the top: highest priority first, then earliest deadline.

A badge shows whether you are **Online** or **Offline**. Work done offline — ticking items on a phone in a basement — is stored on the device and syncs when the connection returns.

## How is a mission completed?

<Steps>
  <Step title="Open the checklist">
    Tap **Open checklist** on the mission card. The header counts your progress.
  </Step>

  <Step title="Work through the items">
    Tick each item as you go. Checklists come from the cleaning templates under **Settings → Cleaning**.
  </Step>

  <Step title="Add a photo">
    Use the camera button to attach proof of the finished room.
  </Step>

  <Step title="Finish">
    Ticking the last item completes the mission automatically. If a unit has no checklist, use **Mark completed** instead.
  </Step>
</Steps>

Completion raises a toast with **Undo**, which reopens the mission if you finished it by mistake.

## What if something is broken?

Use **Something is Broken** on the checklist to raise an incident. A photo is required and a description is optional — you can dictate it instead of typing. This escalates the mission so a manager picks it up, rather than letting the clean stall silently.

## Related

* [Units](/docs/units/overview)
* [Creating Units — operational rules](/docs/units/creating-units)
* [Reservations](/docs/reservations/overview)