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

# About checklists

This page explains why checklists matter when much of the guest communication already runs automatically.

## Control next to automation

Guestway can do many steps of a stay on its own: messages, access codes, follow-ups and review requests. A checklist does not replace that. It is the layer where your team confirms that the work was done, that exceptions were handled, and that the manual steps really happened.

That is why a checklist is simple: a list of tasks in a fixed order, ticked off on the reservation. The work it describes can be complex. The list itself stays easy to read many times a day.

## One way of working across many properties

Checklists were made first for teams that answer guests for many properties, often for several property managers. In that kind of work, a step is easy to miss. A checklist on each reservation gives the same guest experience on every property, fewer mistakes when the volume is high, and a faster start for new team members. It also makes clear who did what, without a separate tool for operations.

## A standard with exceptions

A property uses one checklist: its own, or the one of the level above it. This lets you keep one standard way of working for the whole organization, and still change it for one client, one building or one listing. When you change the standard, every property that inherits it follows. A property with its own checklist does not.

## Related

* [How to create a checklist](https://docs.guestway.io/properties/checklists/how-to-create-a-checklist.md)
* [Checklists](https://docs.guestway.io/properties/checklists.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/about-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.
