> 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/how-to-create-a-checklist.md).

# How to create a checklist

This guide shows you how to create a checklist for your properties and tick off its tasks in the inbox, so no step of a stay is missed.

## Create the checklist

{% stepper %}
{% step %}

### Choose the level

Go to **Properties** and select the level and the property. Choose **Global** if the checklist is for all properties.

{% hint style="success" %}
Create the checklist on the highest level that fits. A standard checklist on the global level or on a complex saves you a copy on every listing.
{% endhint %}
{% endstep %}

{% step %}

### Open the checklists

Open the **Checklists** tab and click **Create**.

If the property already shows a checklist with **Inherited from**, click the pencil icon (**Override checklist for this level**) instead. The tasks of the parent are filled in.
{% endstep %}

{% step %}

### Add the tasks

Enter a task in each row, for example *Send check-in instructions* or *Verify guest ID*. Click **+** to add a row. Drag the rows into the order your team follows.

{% hint style="success" %}
Start each task with a verb and keep it short. *Send check-in code* reads faster than *Make sure the guest has received the check-in code*.
{% endhint %}

{% hint style="success" %}
Order the tasks by when they happen in the stay, not by how important they are.
{% endhint %}
{% endstep %}

{% step %}

### Save the checklist

Click **Create**. You see *Checklist created successfully*. The checklist now shows on every reservation of the property.
{% endstep %}
{% endstepper %}

## Use it in the inbox

{% stepper %}
{% step %}

### Open the operations of the stay

In the inbox, open the conversation and open the **Operations** tab of the details panel.
{% endstep %}

{% step %}

### Tick off the tasks

Click a task when it is done. The change saves automatically. When all tasks are ticked, the card shows **Completed**.

{% hint style="success" %}
Check for the **Completed** badge before you move on to the next conversation. A reservation without it still has work open.
{% endhint %}

{% hint style="success" %}
Keep a matching saved reply for tasks such as *Send check-in code*, so the task takes one click in the same conversation.
{% endhint %}
{% endstep %}
{% endstepper %}

## Related

* [Checklists](https://docs.guestway.io/properties/checklists.md): all fields, and which checklist applies
* [About checklists](https://docs.guestway.io/properties/checklists/about-checklists.md)
* [How to create a saved reply](https://docs.guestway.io/inbox-and-messaging/saved-replies/how-to-create-a-saved-reply.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/how-to-create-a-checklist.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.
