There is a moment I love watching happen to a returning guest. They walk into the room braced to ask for the same thing they always ask for, the high floor away from the elevator, the extra pillow, the early breakfast, and they find it already done. Nobody made a show of it. The room is simply set the way they like, and for a second you can see it land on their face, the small surprise of being remembered. That moment feels like magic to the guest. It is not. It is a note somebody wrote on a previous stay and a note somebody else actually read before this one.
Guest preference notes are one of the most underrated tools in a hotel, because they are quiet and unglamorous and they live inside the property management system where guests never see them. But they are the mechanism behind almost everything that makes service feel personal at scale. No agent can personally remember a thousand guests. The notes remember for them. Written well and used consistently, they let a hotel do the thing every guest secretly wants, which is to be treated like someone the place was expecting rather than a stranger who happens to have a reservation.
I have spent years across the front desk and rooms operations watching the difference between properties that treat notes as a chore and properties that treat them as a craft, and the gap in how the guest feels is enormous. This is the operational engine underneath a bigger idea I care about, that anticipation is the real luxury. You cannot anticipate a returning guest's needs from memory alone. The note is how the anticipation survives from one stay to the next, and from one agent to the one who takes over tomorrow.
What actually makes a good guest note?
Most notes are useless, and it is worth being honest about why. A note that says "great guest, very friendly" does nothing for the next agent, because it is a feeling, not an instruction. It cannot be acted on. The next person reads it, nods, and serves the guest exactly the way they would have anyway. A good note is different in three specific ways. It is specific, it is actionable, and it is about the guest rather than the transaction. Get those three right and the note earns its place.
Before the tests, here is the plain definition I start new hires with.
Everything that follows is really just three tests for whether a line clears that bar.
Specific means it names a real preference, not a vibe. Not "likes a good room" but "high floor, quiet side, away from the elevator." Actionable means the next agent can do something with it before the guest speaks. "Prefers a firm pillow and asks for a late checkout" tells the desk exactly what to arrange. About the guest means it records who they are and what they need, not what happened at the desk that day. "Checked in at 11pm off a delayed flight" is a fact about one night. "Usually arrives late and appreciates a quiet, quick checkin" is a preference you can serve every time. The first is a log entry. The second is a note that makes a guest feel known.
Weak note versus strong note
The three tests are easiest to feel when you rewrite a lazy note into a useful one. Same guest, same stay, very different value to the next agent.
| Scenario | Weak note | Strong note |
|---|---|---|
| A returning couple | "Nice couple, easy to deal with." | "Anniversary trip, took the corner king last time and loved it, appreciated the quiet floor." |
| Room setup | "Picky about the room." | "High floor, quiet side, firm pillow, extra towels, keeps the room cool." |
| Arrival | "Late arrival." | "Usually lands after 10pm off a long flight and wants a fast, quiet checkin." |
| Checkout | "Had an issue at checkout." | "Values speed at checkout, so pre-print the folio and have it ready." |
The left column is a diary. The right column is a set of instructions the next shift can act on before the guest reaches the counter. Only one of them makes a guest feel remembered.
A note that only you can understand helps only you. A note the next shift can act on is the one that makes a guest feel remembered.
What you should never write down
The rule I give every associate is simple and it never fails them: never write anything in a guest profile you would not be comfortable with the guest reading over your shoulder. Guests have the right to see what a company records about them, and beyond the legal reality, it is just the right way to work. A profile is not a diary and it is not a place to vent. It is a service tool, and the moment it fills up with opinions it stops being a tool and becomes a liability.
So keep out the judgments. "Difficult" tells the next agent nothing useful and primes them to expect a fight, which they will then help create. If a guest was frustrated last time, the useful note is the service fact, not the label. "Had a slow checkout last stay, values speed" is helpful. "Impatient and rude" is gossip that will make the next interaction worse. Keep out sensitive personal details that are not service preferences, keep out anything about a guest's appearance or relationships or anything you overheard, and keep out speculation. The test is always the same. Does this help someone serve the guest better on the next stay, or is it just an opinion wearing the costume of a note?
Notes worth writing, and notes to skip
- Write: room preferences a guest returns to, like high floor, quiet side, firm pillow, extra towels.
- Write: rhythm of the stay, like arrives late, leaves early, takes breakfast at open, travels with a small child.
- Write: a genuine occasion the guest shared, like celebrating an anniversary, so the team can acknowledge it lightly.
- Skip: any label about personality or mood that a colleague cannot act on.
- Skip: sensitive details, gossip, or anything you would not say to the guest's face.
A note is only as good as the shift that reads it
Here is where most systems quietly fail. The note gets written, carefully and well, and then it dies, because nobody reads it before the guest arrives. A preference note that sits unread in a profile is worse than no note at all, because someone spent the effort to capture it and the guest still had to repeat themselves, which makes the whole exercise feel like theater. The value of a note is realized only at the moment of the next arrival, when an agent pulls up the reservation, sees the preference, and acts on it before the guest reaches the desk.
That means notes are not really a writing problem. They are a reading problem, and reading is a habit you build into the operation. The strongest desks I have run made checking notes part of the arrival prep, not an afterthought. When you pre-block rooms for the day, you read the notes and assign accordingly, so the guest who likes a high floor is already in one before they walk in. The note does its work in the pre-block, hours before the guest appears, which is exactly when anticipation is supposed to happen. By the time the guest is standing at the counter, the win is already banked.
Here is the loop I teach, because a note only earns its keep when the whole cycle runs:
- Capture it while it is fresh. When a guest mentions a preference or you notice one, write the single specific line before the shift swallows the memory.
- Read it at pre-block. Before arrivals, scan the notes on the day's returning guests and assign rooms to match.
- Act on it before the guest asks. Set the room, stage the crib, ready the late checkout, so the preference is handled on arrival.
- Carry it across the handoff. Pass what matters to the next shift so a preference acted on today is still alive tomorrow.
That last step connects directly to how information moves between the people working a property. A note is a message from a past agent to a future one, and it lives or dies on whether the handoff between shifts carries it forward. A guest should never have to explain themselves twice, once to the person who wrote the note and again to the person who never read it. That continuity is a discipline in its own right, which is why I treat notes and handoffs as two halves of the same craft, and why a clean warm handoff between shifts is what keeps a preference alive long enough to matter.
How notes turn a stranger into a regular
The reason I care about this so much is that notes are how a hotel builds a relationship that outlasts a single visit. A first stay is a transaction with a stranger. Every returning stay is a chance to be a little less strange, to know the guest a little better, and notes are the memory that makes that accumulation possible. Without them, every stay resets to zero and the guest is a stranger forever, no matter how many times they come back. With them, the third stay can feel warmer than the first, because the hotel has been quietly learning the guest the whole time.
What makes this powerful is that the guest does not experience it as data. They experience it as being cared for. They do not think, "the property management system retained my pillow preference." They think, "this place gets me," and that feeling is stickier than any loyalty points program, because it is emotional rather than transactional. A guest can earn points anywhere. Being known is rarer, and it is the thing that makes someone drive past three other hotels to come back to yours. It is a core part of what I mean by real hotel service, the kind that turns a first-time guest into someone who keeps coming back.
I saw the raw version of this on the night shift, working audit at a Waikiki resort, where the returning guests and the regulars were often the ones I got to know best, because nights are quiet enough to actually talk. Someone would mention in passing that they always take the same corner room, or that they come every year for the same week, and I learned early to write it down while it was fresh, because the person on the desk next month would have no way to know it otherwise. The regulars taught me that the small facts are the whole game. Remember the corner room, and you have given them a reason to keep coming that has nothing to do with price.
Building a team that writes and reads
Getting a whole team to keep good notes is harder than it sounds, because note-taking is invisible work that pays off later and usually for someone else. The agent who writes the careful note rarely gets the credit, because the payoff lands on the next agent's shift when the guest lights up. That structure means people quietly stop doing it unless leadership makes the value visible. Running rooms operations across teams of sixty to ninety and more, I have learned you have to celebrate the note out loud, to point at the moment a returning guest felt known and trace it back to whoever wrote the note that made it possible, so the invisible work gets seen.
I also keep the standard for a good note simple enough that people will actually meet it, because a complicated profile system that demands ten fields per guest does not get filled in during a busy arrival rush. One specific, actionable, guest-focused line is worth more than a form nobody completes. The most common mistake I see is a property that mandates long profiles and then wonders why the fields are blank. Ask for less and you get more. Teach the three tests, keep the friction low, make reading the notes part of the pre-block, and celebrate the payoff when it lands. Do that and the notes become a living memory the whole team feeds and draws from, rather than a graveyard of good intentions in a system nobody opens.
So if you want service that feels personal without pretending your agents have superhuman memory, start with the notes. Write them specific, keep them clean, read them before every arrival, and carry them faithfully across every shift change. The magic the guest feels when the room is already right is not really magic. It is a team that decided to remember, one honest line at a time. Write the note as if the next guest's sense of being known depends on it, because it does.