In a hotel, the shift change is where it breaks

Three o'clock

Here is the test I use. At eleven in the morning, a guest mentions at breakfast that it is their anniversary, and that they are tired of the room being hot at night. By three the shift has changed. By seven, does anything exist?

In most hotels, no. The morning server told the morning supervisor, who meant to tell housekeeping, and the evening team starts the day blank. The guest finds out that mentioning something was pointless, and quietly stops mentioning things. That is the moment a hotel loses the chance to be remembered.

A handover is two minutes per section, written. The teams that do it badly aren't lazy; they were never told what belongs in it.

• What is still open from this shift, and who the guest is expecting to hear from.
• Anything a guest mentioned that was not a request: an anniversary, a bad night's sleep, a child who doesn't eat fish.
• Anything broken, and whether the guest already knows it is being dealt with.

Two guests, two answers

Ask four of your own staff what time the pool closes, whether a late checkout is possible, and what to do when a guest asks for a doctor. If you get four answers, your guests are getting four answers, and one of them is making a promise the next shift has to break.

The fix is not a manual. It is a single page of the fifteen things guests actually ask, with the real answer and who decides when the answer is "it depends". Fifteen, not a hundred and fifty: the hundred and fifty version lives in a drawer, and the team keeps guessing.

And write down what staff may decide on their own. Most inconsistency I see is not people inventing rules; it is people with no authority improvising under pressure, because nobody ever told them they could move a table, waive a small charge, or send something up without asking a supervisor who is busy.

The complaint that goes quiet

A guest reports something. Reception passes it to maintenance. Maintenance deals with it that afternoon. Nobody tells the guest. From the guest's side, that is identical to being ignored, and it is the version that ends up in the review.

So the rule I give teams is simple: whoever takes it, owns it. You can hand the work to someone else, but you cannot hand away the guest. You go back, you tell them what happened, and you ask whether it is actually resolved. If it will take two days, say two days rather than nothing.

Feedback that nobody adds up

Most hotels read reviews individually and answer them individually, which feels like diligence and is actually the opposite. Eleven separate mentions of breakfast being slow between 8:15 and 9:00 get eleven polite replies, and nobody ever changes the rota.

Put every piece of feedback into five or six buckets, read them once a month with the heads of department, and pick two things to change. Then check the following month whether the same bucket is still filling. That single meeting is the cheapest quality system a hotel can run.

One thing worth adding, once the basics hold

When arrival, handover and follow-up are steady, a hotel can afford something with character: an arrival ritual built on something local rather than a welcome drink that could be anywhere, a short walk into the neighbourhood with someone who actually lives there, a sunset half hour with quiet music in a space you already have.

I would not start here, though, and I usually say so in the first meeting. A memorable ritual on top of a shaky handover just gives guests a better story about a hotel that forgot their anniversary.