> For the complete documentation index, see [llms.txt](https://docs.guibo.travel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guibo.travel/publishing/tour-guide-app/personalized-accommodation/stage-matching.md).

# Stage Matching

All accommodations are visible in the accommodation list. In addition, accommodations can be shown as check-in and check-out items within a stage as part of the program. This only makes sense if your guidebook structure is itinerary based ([click here for more information](/get-started/getting-started/guidebook-structures.md)). If your guidebooks are structured collection based, [click here](#hide-accommodations-from-within-stages) to disable accommodation display within stages at the account level.

<figure><img src="/files/YSuqntIsddhEWJVrURp5" alt="" width="188"><figcaption><p>Check-in &#x26; check-out accommodations per day</p></figcaption></figure>

## How stage matching works

Itinerary-based stages must have destination markers, which can be any point on the map.

When accommodations are added to a release, **GUIBO matches each accommodation to the stage with the closest destination marker**. Each hotel then appears at the end of its stage as a check-in item and at the start of the next stage as a check-out item.

For this to work, the guidebook needs:

1. A destination marker in every day or stage category. Stages without a destination marker will be ignored.
2. Usually, an arrival stage with its own destination marker for the first night.

[Click here](/get-started/getting-started/create-your-first-guidebook.md#step-3-add-destination-markers-to-stages) on how to add destination markers.

### When the stage matching is not working as expected

In some cases, automated stage matching may not work correctly — for example:

* The correct accommodation is not the closest one.
* An accommodation is missing.
* Two different accommodations need to be assigned to one stage.
* There is no destination marker within 50 km of this accommodation.
* No destination marker was found within 50 km for one or more accommodations.

When this happens, GUIBO disables the release and sends a “Manual review required” email. The user is then asked to check the accommodation matching manually and correct it if needed.

The matching can be reviewed in the release dashboard via the overview map and the “Accommodations” tab on the right side.

After reviewing the matching, the user can activate the release again. This can be done after fixing the issue, such as adding a missing destination marker, or if the user confirms that the matching is already correct and no changes are needed.

#### How to match accommodations manually

Override the automatic result for a single hotel:

1. Open the **accommodation** on the Release Dashboard.
2. Set **Check-in stage** — the stage where the hotel appears as start accommodation.
3. Set **Check-out stage** — the stage where it appears as end accommodation.

## Hide accommodations from within stages

Choose if you want to **show hotels in stage timeline.** A toggle decides whether hotels show on each stage:

* **On** — Show accommodations as check-in/out items as you have structured your guidebooks as day-by-day stage program
* **Off** — Do not show accommodations as check-in/out items as you have structured your guidebooks not as day-by-day stage programs but e.g. as curated collections of specific assets.

You can decide to hide or show check-in/out accommodations within stages on different levels per account, per guidebook, or per single release:

<table><thead><tr><th width="140">Level</th><th>Where to set it</th><th>Scope</th></tr></thead><tbody><tr><td><strong>Account</strong></td><td><code>App</code> → <strong>App Settings</strong></td><td>Default for all guidebooks and releases</td></tr><tr><td><strong>Guidebook</strong></td><td><code>Channels</code> → <strong>Smartphone App</strong> (gear icon)</td><td>Overrides the account default for one guidebook</td></tr><tr><td><strong>Release</strong></td><td><code>Release Dashboard</code> → release → <code>Settings</code> → <strong>Functions</strong></td><td>Overrides for a single booking</td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.guibo.travel/publishing/tour-guide-app/personalized-accommodation/stage-matching.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.