For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.