---
title: Guest Touchpoint Map
description: "## Definition A four-column diagnostic instrument naming every touchpoint across the full Guest journey — from the first thought of going out through the decision on whether to return — and forcing the operator to mark each one Elevated or…"
url: "https://kb.jeffreysummers.com/docs/guest-touchpoint-map/"
updated: "2026-10-25"
category: "The Operator's Dictionary"
---

# Guest Touchpoint Map

## Definition

A four-column diagnostic instrument naming every touchpoint across the full Guest journey — from the first thought of going out through the decision on whether to return — and forcing the operator to mark each one Elevated or Static. Column one names the touchpoint. Column two names the Ideal state. Column three names the [Miasma] — the transactional pressure working against the Ideal. Column four records the operator’s honest call.

The map runs the full Guest journey as a loop, not a line: fourteen touchpoints — Contemplation, Decision, Pre-arrival, Arrival, Entry, Greeting, Seating, Order, Service, Meal, Resolution, Departure, Post-visit, Re-contemplation — with the Post-visit touchpoint feeding Re-contemplation, which feeds the next round of Contemplation. [Guest Touchpoint Map] is the instrumentation of the [Guest Experience]: the GX is the Product, and the map is how the operator reads, touchpoint by touchpoint, whether the operation is producing it.

## Mechanism

**Every row runs the same structure.** What the touchpoint actually is, what the Ideal looks like, what the [Miasma] looks like when the operator defaults instead of designs, and an honest mark of which one is actually happening. The value of the instrument isn’t the definitions — an operator can read what Elevated looks like without ever changing anything. The value is in making the Static mark impossible to avoid seeing once it’s written down next to the Ideal it’s failing to reach.

| Guest Touchpoint | Ideal | The Miasma | Your Experience: Elevated or Static? |
| --- | --- | --- | --- |
| 1. **Contemplation.** The Guest is thinking about going out. No decision made. They are scanning their mental map — restaurants, memories, moods, needs. | The operation has already made itself known to this Guest. Through consistent signal, memorable identity, and earned recall, the operation is on the Guest’s mental map before the decision moment opens. The Guest does not have to search for it. | Operator is absent from this touchpoint entirely. Assumes presence equals consideration. Waits passively to be chosen. Nothing has been built to occupy mental real estate before the decision moment arrives. | Elevated ○ Static ○ |
| 2. **Decision.** The Guest is actively choosing. Comparing the operation against alternatives, including the alternative of not going out at all. | The Guest has a specific reason to choose this operation that only this operation can deliver. The decision is not between restaurants. It is between this experience and everything else the Guest could do with the night. | Operator competes on menu, price, proximity. Sameness against the restaurant next door. The Guest has no reason to pick this operation over the mirror across the street. | Elevated ○ Static ○ |
| 3. **Pre-arrival.** The Guest is coming. Reservation confirmed. Directions, parking, menu glance, expectation setting are all in motion. | The pre-arrival window is used to warm the Guest before they walk in. Personal touches, useful information, signals that tell the Guest this visit will not be ordinary. The operation is already hosting before the Guest arrives. | Reservation is treated as a data entry task. Confirmation email and nothing else. The Guest arrives cold, with generic expectations, and the operation’s window to shape the experience shrinks before the door opens. | Elevated ○ Static ○ |
| 4. **Arrival.** The Guest is physically at or approaching the building. Parking, walking up, exterior impression, front door. | The exterior is treated as the opening line of the experience. Lit well, clean, intentional. Landscaping, signage, curb all read as on-purpose. The Guest’s first operating opinion is shaped by design, not accident. | The outside of the building is not treated as the operator’s problem. Landscaping, lighting, signage, curb left static. The Guest forms a first operating opinion before anyone has said a word. | Elevated ○ Static ○ |
| 5. **Entry.** The Guest crosses the threshold. First three seconds inside. Sight, smell, sound, temperature, energy. | Every sense calibrated in the first three seconds to tell the Guest they chose correctly. Light level, sound level, scent, temperature, and the energy of the room are engineered — not accidental. | Entry is left to chance. Whoever happens to be near the door handles it. Background music is whatever was on yesterday. The Guest reads the room in three seconds and most of what they read is unplanned. | Elevated ○ Static ○ |
| 6. **Greeting.** First contact with a human who works for the operation. Host, hostess, manager, whoever is closest to the door. | The greeting is welcome, not intake. Eye contact, name if known, presence. The Guest is seen as a person before they are sorted into a table count. | “Welcome to [restaurant]. How many?” Scripted, transactional, processing. The Guest learns in eight seconds that they are a reservation, not a person. | Elevated ○ Static ○ |
| 7. **Seating.** Host walks the Guest to a table. The walk itself and the placement. | The walk and the table are staged. The Guest gets the best seat available, best angle, best first impression of the room. The seating decision is the operation’s statement about who this Guest is to the house. | Nearest open table that fits the party. Efficiency over experience. The Guest ends up near the service station, in the high-traffic lane, or facing a wall. | Elevated ○ Static ○ |
| 8. **Order.** The Guest is given the menu, considers it, asks questions, decides. Server interaction begins. | The server is a guide, not a note-taker. Steers with confidence. Knows the menu. Makes the Guest feel smart for the choices they make. The order is a conversation the Guest wins. | “Can I start you with drinks?” Transactional rhythm. Server is order-taking. The Guest makes buying decisions with no guide, surrounded by choices they do not know how to rank. | Elevated ○ Static ○ |
| 9. **Service.** Ongoing presence of the staff throughout the meal. Refills, check-ins, pace, attentiveness. | Service is invisible when it is right. Staff reads the table — when to appear, when to stay away, when to speed up, when to slow down. The Guest is never waiting and never watched. | Service is presence and scripts. “How is everything?” delivered in the middle of a bite. The Guest is managed, not served. Staff performs attentiveness without reading the table. | Elevated ○ Static ○ |
| 10. **Meal.** The food and drink itself. What is on the plate and in the glass. | At least one moment on the plate or in the glass the Guest will repeat to someone tomorrow. The meal earns the story. Temperature, accuracy, pace, and craft all land as intended. | The kitchen executes what the menu promises at the level the brand has trained the Guest to expect. Sameness wins. The Guest remembers the meal as “fine.” Nothing to say about it later. | Elevated ○ Static ○ |
| 11. **Resolution.** The close of the experience from the table side. Check delivery, payment, tip, final words. | The close is a memory-making moment. Splits handled cleanly. Thanks delivered specifically. The table feels cared for right up to the last second. The last impression is made on purpose. | The check is treated as a billing problem. One check, run the card, move the table. Twenty minutes of fumbling overwrites two hours of goodwill. | Elevated ○ Static ○ |
| 12. **Departure.** The Guest leaves. Walking out, last contact, exterior exit, car, goodbye. | Someone is by the door. Real goodbye. Name if known. The last human contact is as warm as the first. The Guest exits held, not released. | Nobody notices the Guest is leaving. No farewell. Staff is already flipping the table. The Guest exits the building feeling transacted, not hosted. | Elevated ○ Static ○ |
| 13. **Post-visit.** After the Guest leaves. Follow-up, review window, social mention, a text to a friend. | Post-visit is owned. Thank-you where appropriate. Earned ask for a review, not a demanded one. A reason to come back is lodged before the memory dims. | Post-visit is not a touchpoint to the operator. The Guest is gone; attention resets to the next cover. The experience fades inside 48 hours. Review prompts get ignored because the moment to ask has already passed. | Elevated ○ Static ○ |
| 14. **Re-contemplation.** The next time this Guest thinks about going out. Loops back to Row 1, but with this experience now on their mental map. | Every touchpoint upstream was built to earn this moment. The Guest comes back because the experience left a specific, repeatable reason to return. The loop is the system. | The operator assumes last time was enough. Hopes the Guest remembers. The Guest does not automatically return. The operation is now one of many options, and the question at Contemplation restarts from zero. | Elevated ○ Static ○ |

The Ideal and the Miasma are a choice at every touchpoint. Mark your experience.

**The loop, not the line.** Every visit is either earning the next visit or losing it — there’s no neutral touchpoint in the loop. Post-visit feeds Re-contemplation, and Re-contemplation feeds the next Contemplation. The operator who thinks the journey starts at the reservation or the door has already missed the first and most decisive touchpoint, and the operator who thinks it ends at the check has missed the two that decide whether the Guest comes back. Every touchpoint upstream was built to earn Re-contemplation. If the experience did not leave a specific, repeatable reason to return, the question at Contemplation restarts from zero.

**Columns two and three are a choice, not a description.** The Ideal and the [Miasma] are not two possible outcomes the operator watches for. They are the two options the operator picks between at every touchpoint, and column four is where the choice gets recorded. The [Miasma] is not a bad move. It is the absence of a move — the operator who simply did not show up to a touchpoint that was always going to get decided, with or without him. Nothing breaks. Nothing shows up as an event. The touchpoint just runs on whatever was left there.

**Most operators work three or four touchpoints and leave ten to chance.** The touchpoints operators work are the ones they can see from behind the pass — the Order, the Meal, maybe the Greeting and the Resolution. The touchpoints they leave are the ones that happen outside the building, before the door, or after the Guest is gone: Contemplation, Decision, Pre-arrival, Arrival, Post-visit, Re-contemplation. Those are where the [Miasma] wins by default, because nobody was assigned to them and nothing was designed for them. The operator who works every touchpoint is not doing more work. He is doing the same work with intent at places the [Miasma] was left to win.

**Elevated deposits. Static leaks.** At every touchpoint the operation either compounds the [Guest Contract]’s standing or leaks it. Static is not neutral. Static is the default state the Contract erodes through when no design is holding the standard. The Guest walking out of a fully Static visit did not experience an average meal. They experienced the Contract silently withdrawing across every touchpoint that failed to compound, and the [Trust Arc] closed without a deposit.

**The read runs on three timeframes.** In real time at each touchpoint during the shift. In aggregate at the end-of-shift debrief, when the operator and the cast lead walk the shift’s arrivals and count the parties that were hosted against the parties that were processed. And at period level, where the accumulated Static marks show up in [Relational Compounding] as a curve that flattened or reversed. All three are required. One or two alone will miss the pattern.

**Static marks are the design queue.** The map does not tell the operator what to do. It is a diagnostic map, not a playbook. It names the touchpoints, the Ideal state at each, and the [Miasma] pressing against it. The moves are the operator’s to build. Every Static mark becomes a line in next period’s design queue — one touchpoint per period, with a named observable standard, a trained cast, and the standard enforced on the worst shift. That is how the map turns the GX from a slogan into an operable Product the operator can design against.

## Load-Bearing Distinction

**Not the [Guest Experience].** The GX is the aggregate — every touchpoint between operator and Guest, from first awareness to long after the visit, as the Guest lived it. The Guest does not experience touchpoints. The Guest experiences the aggregate. The map is the instrument the operator reads the aggregate with; it is not the Product. Operators who chase individual touchpoint scores — greeting time, food timing, check speed — optimize the moments while the arc goes uncomposed, and produce operations that score well on touchpoint audits and produce forgettable GXs. The touchpoint is a diagnostic instrument; the aggregate is the Product.

**Not the [Experiential Loop].** The [Experiential Loop] is the designed in-room arc — opened by the host at the door, run by the server and bartender at the table and bar, closed by the host at the goodbye, held together by handoffs. It is the operating shape the visit runs on. The map is wider: it starts at Contemplation, before the Guest has decided anything, and runs past Departure through Post-visit and Re-contemplation. The Loop is how the cast runs the middle of the journey. The map is how the operator reads the whole of it.

**Not [Point Of Experience].** A [Point Of Experience] is the literal moment a specific cast member faces a specific decision and the interaction either executes the designed GX or defaults to transactional behavior. Points of experience happen inside touchpoints, many times a shift. The map names the fourteen places the journey runs through; the [Point Of Experience] names the fork inside any one of them where the Elevated or Static mark actually gets earned.

**Not [Miasma].** [Miasma] is the failure state at any touchpoint where the operator is simply absent. It is one column of the map. The map holds the [Miasma] next to the Ideal it is defeating, at every touchpoint, so the operator cannot read the failure without also reading what it is failing to reach.

**Not a mystery shopper report or a satisfaction score.** A score aggregates the visit into a number the operator cannot act on, and it is read after the fact by someone outside the operation. The map is read by the operator, at the touchpoint, against an Ideal he wrote himself. Instruments that rate the visit measure it. The map makes the operator choose at it.

**Not a service-steps checklist.** Service is technical delivery of f&b; hospitality is the produced experience the Guest came for. A steps-of-service checklist confirms the steps were executed. The map asks whether the touchpoint was Elevated or left to the [Miasma], and a touchpoint can run every step on the checklist and still be Static. Rigid adherence to service steps cannot compensate for a poor GX.

The term is load-bearing because without it the operator reads the visit from behind the pass, works the three or four touchpoints he can see, and leaves the rest to whatever happens to be there. The map is what makes the other ten visible, and what makes the Static mark impossible to stop seeing once it is written down.

## Diagnostic Tests

**Test One — The Count Test.** List the fourteen touchpoints. Next to each one, write the name of the person in the operation responsible for it and the observable standard they are held to. Count the touchpoints with both a name and a standard. Three or four is the industry default. Every touchpoint without a name and a standard is a touchpoint the [Miasma] is running.

**Test Two — The Real-Time Touchpoint Test.** During one shift, walk the operation through every touchpoint on the map from the door forward. At each one, ask one question: did the Guest at this touchpoint get hosted, or processed? Mark each touchpoint Elevated or Static. The number of Static marks is the real-time read for that shift. If the operator cannot answer the question at any touchpoint, the touchpoint has no designed standard — the read is undefined there, which is a different failure from a Static mark.

**Test Three — The Guest’s Position Test.** Pick one shift and read the operation from the Guest’s position through every touchpoint — not from the operator’s position behind the pass. From the parking lot, through the front door, to the host stand, to the table, through the meal, to the check, to the door, to the car. Mark each touchpoint. The marks the operator gives from the Guest’s position and the marks he would have given from behind the pass are rarely the same. The difference is how much of the operation he has been reading from the wrong place.

**Test Four — The Elevated-Or-Static Test.** Instrument one specific Guest’s visit against the map. A visit with mostly Elevated marks is a [Guest Contract] that compounded. A visit with mostly Static marks is a Contract that leaked. A visit with an Elevated middle and a Static open and close is a Contract with structural gaps at the entry and exit that no middle-arc excellence can compensate for.

**Test Five — The Outside-The-Building Test.** Read the six touchpoints that happen before the door or after the Guest leaves: Contemplation, Decision, Pre-arrival, Arrival, Post-visit, Re-contemplation. For each one, name what the operation did on purpose this period. If the answer is nothing, or a confirmation email and nothing else, those touchpoints are running the [Miasma] by default, and the operation is competing on menu, price and proximity against the mirror across the street.

**Test Six — The Post-Visit Read Test.** For one recent Guest, read whether the operation did anything at Post-visit — a thank-you where appropriate, an earned ask, a reason to come back lodged before the memory dimmed — or whether attention reset to the next cover the moment the Guest walked out. The [Guest Contract] does not close at the check. It closes at the Guest’s post-visit read. Operations that leave Post-visit Static are closing every Contract blind.

**Test Seven — The Write-It-Down Test.** Take the earliest Static mark on the map and write two things in observable terms: what the Ideal looks like at that touchpoint in this operation, and what the [Miasma] looks like there right now. If the operator cannot write the Ideal, the touchpoint has never been designed. If he cannot write the [Miasma], he has never looked at it. Either way, the gap between the two lines is the architecture he has to build next period.

## Family Position

Product instrument. Sits under the [Guest Experience] as its instrumentation — the GX is the Product, the [Experiential Loop] is its in-room shape, the [Connection Floor] is its minimum, the [Trust Arc] is its deposit ledger, and [Guest Touchpoint Map] is how the operator reads it. Its column three is [Miasma], and its first touchpoint is [Contemplation], both locked terms. Every [Guest Contract] is co-signed across the touchpoints the map names. Cross-Fundamental: the map is a Product instrument, but every Fundamental reads it differently, and all five reads have to agree for the GX to hold.

**Perspective read.** The map changes where the operator stands when he reads his own operation. The default posture reads the visit from behind the pass, from the moment the party is seated to the moment the check is paid, because that is the part of the journey the operator can see and the part the reports are built around. The map moves the read to the Guest’s position and widens it from the dining room to the full loop, starting at the first thought of going out and ending at the next one. The operator who adopts it stops reading component by component — the food was good, the service was fine, the room was clean — and starts reading the arc. The Perspective failure shows up as an operator who can describe his Order, Meal and Resolution in detail and has nothing to say about Contemplation, Pre-arrival or Post-visit. The response is to run the Count Test and the Guest’s Position Test until the touchpoints he cannot see stop being invisible to him.

**Product read.** The GX is the Product, and the map is where the Product gets designed. Each row is a specification: the Ideal names what the Product is supposed to produce at that touchpoint, the [Miasma] names what it produces when nobody designed it, and the mark names which one the operation is actually producing. Operators who read the food as the Product design the kitchen; operators who read the GX as the Product design the arc, and the map is what makes the arc designable one touchpoint at a time. Product failure shows up as a Meal row marked Elevated sitting in a column of Static marks — the kitchen executes, and nobody designed the other thirteen touchpoints the Guest lived through. The response is the design queue: the earliest Static touchpoint, designed in observable terms, one per period.

**People read.** The cast is the medium through which every touchpoint inside the building is executed. The Greeting, the Seating, the Order, the Service, the Resolution and the Departure are each run by a specific cast member on a specific shift, and every handoff between them is a moment where the Guest is either held or dropped. A Static mark at a cast-run touchpoint is an architecture readout, not a cast performance issue: it names a touchpoint the operator never designed, never trained the cast on in observable terms, or never enforced on the pressured shift. Reading the Static mark as a cast problem leads to the wrong intervention — pressure the cast harder — and produces more theater, not more hosting. The People response is to give each touchpoint an owner, a standard, and the training to hold it with the least experienced cast on the worst shift.

**Performance read.** The map is the leading indicator the operator reads during the shift. Ticket time, table turn and check average are lagging readings of what already happened; the Guest’s engagement at each touchpoint is the leading reading of what the operation is producing right now. Performance shows up in the marks: a shift that runs Elevated at the Greeting and Static at Departure because the cast was already flipping the table is a shift that executed its throughput and lost the close. The response is the three-timeframe read — the touchpoint read on the stage, the end-of-shift debrief with the cast lead, and the period read — run every shift long enough for the pattern to show.

**Profit read.** The map is where the money architecture of a Road 2 operation starts. Elevated touchpoints deposit into the [Guest Contract] and the [Trust Arc]; closed trust starts [Relational Compounding] — Guests who return more often, spend more freely and recommend without needing a bribe. Static touchpoints leak, and the leak never appears on the P&L as an event. It appears as a Guest who did not come back, a Re-contemplation that restarted from zero, and a [Lost Opportunity Tax] on every visit that could have been earned and was not. The operator who works three or four touchpoints is paying that tax on the other ten every shift. The Profit response is to read the map against return behavior, not against the check, because the check closes the transaction and the map closes the Contract.

## Cross-References To Locked IP

Parent:

- [Guest Experience] — the Product the map instruments; every touchpoint is a place the GX either compounds or leaks

Related:

- [Miasma] — column three of the map; the failure state at any touchpoint where the operator is absent
- [Contemplation] — the first touchpoint on the map and the one most operators never know they are competing at
- [Experiential Loop] — the designed in-room arc the cast runs through the touchpoints from Greeting to Departure
- [Point Of Experience] — the moment inside a touchpoint where the Elevated or Static mark is actually earned
- [Connection Floor] — the minimum every human touchpoint on the map produces before anything is added
- [Guest Contract] — the per-visit Contract co-signed across the touchpoints; Elevated deposits, Static leaks
- [Trust Arc] — the deposit ledger the map’s marks write to across visits
- [Customer-Guest Gap] — read in real time at each touchpoint of the map during the shift
- [Relational Compounding] — where accumulated Static marks show up at period level as a curve that flattened or reversed
- [The Hospitality Contract] — the Contract form the Ideal column is written against

Opposing patterns:

- [The Service Contract] — the Contract the operation defaults to when the touchpoints run the [Miasma]
- [Substrate Seduction] — mistaking the room, the food or the tools for the Product while the arc goes uncomposed
- [Hacksterism] — hospitality-shaped moments run on top of a transactional system, touchpoint by touchpoint
- [Lost Opportunity Tax] — the tax paid on every touchpoint left to chance
- [Static Decline] — the operator condition that reads a Static mark as holding steady

## Why This Matters

The instrument earned a name because operators read the visit from where they stand, and where they stand is behind the pass. From there the journey starts when the party sits down and ends when the card is run. Everything before the door and everything after it belongs to nobody, and the [Miasma] fills every space nobody owns. The operator can be excellent at the four touchpoints he sees and still lose the Guest at the ten he doesn’t, and he will never know which one it was because none of them show up as an event.

The map does one thing a report cannot do. It puts the Ideal and the [Miasma] side by side at every touchpoint and makes the operator write down which one is happening. An operator can read what Elevated looks like for years without changing anything. He cannot write Static next to an Ideal he wrote himself and keep pretending the touchpoint is fine.

The map is how the [Guest Experience] becomes something an operator can design instead of something he hopes for. Every Product discipline in the framework resolves against it — the [Experiential Loop] runs through it, the [Connection Floor] sets its minimum, the [Guest Contract] is signed across it, the [Trust Arc] records it, and [Relational Compounding] is what it pays out when the marks are Elevated long enough. The loop is the system, and the map is how the operator reads the loop.

## Operating Consequence

**Read the full loop, not the visit.** The operator stops treating the journey as door to check. Every read, every debrief and every design conversation runs Contemplation through Re-contemplation. A touchpoint outside the building is still a touchpoint, and the operator owns it.

**Assign every touchpoint.** Every one of the fourteen touchpoints gets a named owner and an observable standard. A touchpoint with no owner is a touchpoint the [Miasma] is running, and the operator says so out loud.

**Mark, don’t rate.** The operator retires scores and averages as the read of the visit. Each touchpoint gets one honest mark — Elevated or Static — against the Ideal written for it. There is no third mark. Static is not neutral, and the operator refuses to call a Static touchpoint fine.

**Read Static marks as architecture, not effort.** A Static mark at a cast-run touchpoint sends the operator to the design, the training and the enforcement, not to the cast member. The operator refuses the reflex to push the cast harder at a touchpoint he never designed.

**Run the three timeframes.** The touchpoint read happens on the stage during the shift, the debrief happens with the cast lead at the end of it, and the period read happens against return behavior. All three run, every shift, long enough for the pattern to show.

**Work the queue one touchpoint per period.** Static marks become next period’s design queue. One touchpoint per period, a named observable standard, a trained cast, enforced on the worst shift. The operator does not try to fix all fourteen at once, and he does not let the queue sit.

## What Changes Tomorrow

Print the map. Before tomorrow’s shift, write the name of the person responsible for each of the fourteen touchpoints next to it. Leave the line blank where there is nobody. Count the blanks.

During the shift, walk one party’s visit from the Guest’s position, from the parking lot to the car, and mark every touchpoint inside the building Elevated or Static. After the shift, sit down with the cast lead and mark the six that happen outside it: what did the operation do on purpose at Contemplation, Decision, Pre-arrival, Arrival, Post-visit and Re-contemplation this period?

Take the earliest Static mark on the map. Write what the Ideal looks like at that touchpoint in your operation, in observable terms, and write what the [Miasma] looks like there right now. That touchpoint is next period’s design. Name the owner, write the standard, train the cast on it, and enforce it on the worst shift. Mark it again at the end of the period. If it reads Elevated, take the next Static mark. If it still reads Static, the standard was not observable enough or was not enforced, and that is the read.

The Ideal and the [Miasma] are a choice at every touchpoint. The map is where the operator stops leaving the choice to chance.

Three attachments accompany this entry: the Guest Touchpoint Map document, a color graph of the fourteen touchpoints for viewing and a black-and-white version for printing.