> 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/properties/checklists.md).

# Checklists

A checklist is a list of tasks for your team that shows on each reservation of a property, on the Operations tab of the inbox.

## Checklists tab

Checklists are on the **Checklists** tab of **Properties**, on each level: global, complex, multi-unit and listing.

| Element                               | What it does                                                                              | Limits                                                                                    |
| ------------------------------------- | ----------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| **Create**                            | Creates a checklist for this level.                                                       | Only when no checklist applies to the property yet. In Hub mode, not on the global level. |
| **Checklist** card                    | The tasks of the checklist that applies. *No checklist items found* when it has no tasks. | None                                                                                      |
| **Edit checklist**                    | Edits the checklist of this level.                                                        | Only on the level of the checklist.                                                       |
| **Inherited from**                    | The level the checklist comes from, with a link to it.                                    | Only when the checklist comes from a higher level.                                        |
| **Override checklist for this level** | Creates a checklist for this level, filled in with the tasks of the parent.               | Only when the checklist comes from a higher level.                                        |

## Which checklist applies

Each level has at most one checklist. A property uses the most specific one: the checklist of the listing, then of the multi-unit, then of the complex, then the global one. Each reservation has one checklist.

## Checklist editor

The editor opens as **Create checklist**, **Edit checklist** or **Override checklist**. The checklist belongs to the property you are on, or to the whole organization on the global level.

| Field            | What it does                                                                                                                                                     | Limits                                                                                      |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| **Organization** | The organization of the checklist.                                                                                                                               | Shows only when you manage more than one organization. Cannot be changed.                   |
| **Tasks**        | The tasks, in the order your team follows them. Each task has a name (*Enter task name*). Drag a task to move it. The trash icon removes it, and **+** adds one. | Required. A new checklist starts with 3 empty tasks. Empty tasks are removed when you save. |

**Delete** in the edit dialog removes the checklist of this level.

## Checklist in the inbox

The **Checklist** card is on the **Operations** tab of the [reservation details panel](https://docs.guestway.io/inbox-and-messaging/unified-ai-inbox/reservation-details-panel.md#operations-tab). The tab is hidden for an inquiry.

| Element       | What it does                                                                                  | Limits |
| ------------- | --------------------------------------------------------------------------------------------- | ------ |
| Task          | Click the task or its checkbox to tick it or untick it.                                       | None   |
| Saving        | The changes save automatically after a short pause. You see *Checklist updated successfully*. | None   |
| **Completed** | Shows when all tasks of the reservation are ticked.                                           | None   |

The ticks belong to the reservation. Each reservation starts with no ticks.

## Related

* [How to create a checklist](https://docs.guestway.io/properties/checklists/how-to-create-a-checklist.md)
* [About checklists](https://docs.guestway.io/properties/checklists/about-checklists.md)
* [Reservation details panel](https://docs.guestway.io/inbox-and-messaging/unified-ai-inbox/reservation-details-panel.md)


---

# 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/properties/checklists.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.
