A hotel guest journey map. Six stages, and the two hotels usually under-own.

The short answer on a hotel guest journey. A map most hotels already have half of.

Walk into most hotels' marketing decks and you will find a guest journey map, usually built for a rebrand or a technology pitch, usually looking tidy, and usually gathering dust within a year. The map itself is rarely the problem. The problem is that most properties genuinely invest in only two or three of the six stages, arrival and the stay, because those are the ones staff experience directly, and leave the other three running on whatever the booking engine and a generic post-stay email happen to do automatically.

A hotel guest journey map earns its place when it is used to decide where the next piece of attention or budget goes, not when it is laminated and filed. The stages that most reliably reward a closer look are the two edges: pre-arrival, before a guest has set foot on the property, and post-stay, after they have left. Both sit outside the window where staff can personally compensate for a gap, which is exactly why they drift.

This matters more than it looks like it should, because the two neglected edges are also where a hotel has the most room to influence a guest's decision for next time. Arrival and the stay happen whether or not anyone plans for them well; a guest still checks in, still sleeps in the room. Pre-arrival and post-stay are optional in a way the middle stages are not, which means they are also the first thing cut when a property is short on time, and the first thing a competitor with a tighter map can use to pull a guest away.

The six stages, mapped. Where attention concentrates, and where it drops.

Oracle's 2021 hospitality mobile and contactless maturity study found over 60% of surveyed properties had a guest-facing app supporting pre-arrival communication. That figure is dated now, and adoption has likely moved since, but the pattern it captured still holds in most guest journey maps I review: the technology for pre-arrival exists at far more properties than the practice of actually using it to do more than confirm a booking.

How to build one in practice. Four steps, in order.

1. Pull the raw touchpoints from the systems, not from memory. The PMS, booking engine, guest messaging platform and review site each hold a record of what actually happens at each stage; starting from a workshop whiteboard instead tends to map the journey as staff imagine it, not as guests experience it.
2. Separate the map by channel where the path genuinely differs. A direct booker's discovery stage runs through the hotel's own website and gets captured by the CRM at that point. An OTA booker's does not, and will not appear anywhere in the hotel's own systems until arrival, which changes when pre-arrival outreach can realistically start.
3. Mark each touchpoint with who owns it and which system delivers it. A touchpoint with no named owner and no named system is the one that will quietly stop happening the next time someone on the team changes roles.
4. Fix one weak stage before mapping the next season or property. A map that tries to improve every stage at once rarely improves any of them; picking the single worst-performing stage, usually pre-arrival or post-stay, and fixing it first produces a result that justifies doing the next one properly.

What good looks like. Signs a journey map is actually used, not filed.

• Pre-arrival and post-stay have a named owner, not a shared responsibility split across front office, marketing and F&B with nobody accountable for the handoff between stages. When three departments each own a slice of a stage, the stage itself tends to belong to none of them.
• The map is built from real data, not guesswork, pulling from the PMS, the booking engine and guest messaging rather than one team's assumption about what guests experience. A map built from a workshop discussion alone usually reflects what staff believe happens, which is rarely identical to what the booking and messaging logs actually show.
• OTA-sourced guests are mapped separately where their path actually differs, since a guest who books through an OTA often skips the hotel's own discovery stage entirely and may not surface in the property's CRM until check-in. Treating every guest as a direct booker for mapping purposes overstates how much pre-arrival contact is actually possible.
• The map gets revisited at least twice a year, and whenever the channel mix shifts, such as a change in the direct-to-OTA ratio or a new check-in system going live. A property that grows its direct bookings by even ten percentage points has meaningfully changed how much of its journey it can actually influence.

Where this goes wrong in practice. Technology at one end, nothing at the other.

A hotel group I worked with, illustrative rather than a named result, had invested seriously in the arrival stage: mobile check-in, a digital key, and a slick in-app welcome message. Guest satisfaction scores for arrival climbed noticeably. Repeat-guest rate, which the general manager had expected the same investment to move, stayed flat. The reason showed up once the full journey was mapped rather than just the arrival stage: post-stay was a single templated review-request email, sent identically to a guest who had a flawless five-night stay and one who had complained twice at the front desk. Nothing in the post-stay stage distinguished between the two, so neither got a reason to come back, and the arrival investment, while genuinely good, never reached far enough down the journey to change the metric it was meant to move. The fix cost less than the arrival technology had: a post-stay flow branched by whether any issue had been logged during the stay, with a different message and a direct-booking incentive for guests who had a clean stay. Within two seasons, the same guest-satisfaction team that had championed the arrival investment could finally point to a measurable rise in direct repeat bookings, not because the arrival experience improved further, but because the stage that had been quietly running on a single generic template finally had a decision rule attached to it.

Pitfalls to avoid. Where hotel journey maps usually fail.

• Building the map once, for a rebrand or a pitch deck, and never updating it. A map is a working document or it is decoration; it cannot be both.
• Mapping the booking engine's path and assuming every guest follows it. OTA bookings, walk-ins and corporate rate guests each enter the journey differently, and a map that only reflects direct bookings misses a large share of arrivals at most properties.
• Treating post-stay as "send a review email" rather than a stage with its own objective. Rebooking, direct-channel migration and complaint recovery are three different goals that one generic email cannot serve at once.
• No link between the map and the systems delivering each touchpoint. A beautifully designed map that nobody connects to the PMS, booking engine or guest messaging tool stays a map of intentions, not of what actually happens.

None of this requires a system overhaul. It requires picking the two stages most hotels already under-own, pre-arrival and post-stay, and giving each one a named owner and a goal distinct from "send the standard message." That alone moves most of the properties I have reviewed further than another round of arrival-stage technology would, and it costs closer to a few hours of someone's time than a line item in next year's capital budget.

The broader point carries beyond hospitality, which is why a hotel guest journey map is worth building properly even for a single-property owner who will never run a multi-brand portfolio. A journey map is only as useful as the gap it exposes, and the gap is almost always at an edge, the moment before someone commits and the moment after they have already left, because those are the two points where nobody in the building is physically present to notice that nothing is happening.