YMMEHotels
Bring your hotel
Insights · Operations

What the night shift knew and the morning shift didn't

By the YMME team·5 min read·September 2026

A guest in room 12 tells the night receptionist at 23:40 that the shower runs cold after two minutes. The receptionist writes it in the logbook, posts it in the staff chat and goes home at seven. The morning receptionist reads the chat on the bus, walks into a check-out queue, and by ten the message is under forty others. Housekeeping does room 12 at eleven, runs the tap for thirty seconds, finds nothing wrong. The guest comes back at six and reports the fault a second time, to a third person. Nobody in this story was careless. The fault was handed over three times and owned by no one.

Quick answer. In a hotel of 15 to 40 rooms the shift handover is where operational information goes missing: not because staff are careless, but because a handover is a message, and a message has no owner once it has been sent. A stricter logbook or a rule about the chat does not change that. What changes it is a task that exists as a record: created once where the problem was noticed, assigned to one person, visible to the next shift without being retold, and closed only by the person who did the work.

A handover is a message. A task is a record.

The logbook, the group chat, the note taped to the monitor: each is a message addressed to whoever is on next. Messages get read. They do not get done, because reading one creates no obligation. The reader can reasonably assume somebody else saw it too, and in a small team that assumption is usually right, which is exactly why nothing happens.

A record is different in one way that matters. It has a state. It is open or it is closed, it belongs to someone or it belongs to nobody yet, and it stays exactly where it is until somebody changes that state. Nobody has to repeat it at the next shift change. It is simply still there.

Why the handover is harder in a small hotel

A larger hotel has somewhere for the fault to go: a duty manager, an engineering desk, a maintenance module in the property system that somebody was trained on. The fault in room 12 has a department.

At 15 to 40 rooms the same person runs reception, answers the phone and is the maintenance desk. The team is small enough that everyone does everything, and the consequence is that nothing has a single owner. The information is all there, in the logbook, in the chat, in the housekeeper's memory. The ownership is not. A hotel running three shifts a day has twenty-one handovers a week, and each one is a place where an open item can quietly become nobody's.

What survives a shift change

The measure of a handover system is what is still visible, and still owned, the morning after.

  • The issue is logged where it was noticed: room, what, who reported it, when. One line, written once.
  • It is routed, not broadcast. It goes to the person who will fix it, not to everyone who might.
  • The next shift sees it without anybody retelling it. The record does the handover.
  • It is closed by the person who did the work, with a time, so "done" means something.
  • If it was not done, it is still open, and the open list is the first thing the next shift reads.

None of this needs a new department. It needs a place where an open item can sit without being retold, and one person whose name is on it.

The list the morning shift reads first

A morning in a small hotel should not begin with scrolling back through last night's chat. It should begin with what is open: the tasks carried over from the night, the maintenance issues nobody has closed, the arrivals with a note against them. If that list is empty, the day starts clean. If it is not, the morning shift knows what it inherited before the first guest reaches the desk.

A message is read. A task is done. The difference is who owns it at seven in the morning.

What this has to do with reviews

The guest in room 12 does not write a review about a cold shower. Faults happen and guests know it. The review is about the second report: about telling the hotel twice and being asked, the second time, what room they are in. The damage in that sentence is the handover that failed between the two reports, and the guest is the only person who saw both ends of it.

Fix the handover and the same fault becomes a different story: reported once, fixed by the afternoon, mentioned by the receptionist at check-out before the guest can. It starts from the same cold shower. It ends somewhere else.

Where YMME fits. YMME Baton is the operations module of the YMME platform. Staff and shift management with schedules and handover, tasks that do not slip, a maintenance tracker where issues are logged and routed, and real-time P&L and USALI 12th-edition reporting sit in the same window. It comes with the hotel, with no separate login or site, and is included from the Solo tier. The figures on the Baton page are modelled: designed performance, not results.

Make the handover arrive.

Talk to us
Related Baton · Operations The hotel SOP checklist The Peak-End rule
We use only essential local storage to remember your language and view. No tracking, no ads. Details