Handing over cash is the easy part
Count the float, reconcile cash taken against the system, sign off — almost every hotel does this properly, because missing money shows up immediately. The problem is that many stop here and consider the handover done, while the things that annoy guests live among what cannot be counted.
The work left unfinished
Room 305 asked for an iron and is still waiting. A group of ten will arrive after midnight. Room 210 was promised a room change tomorrow morning because the air conditioning rattles. A VIP told the restaurant about a seafood allergy. This is the information that makes or breaks a stay, and it is the first to fall through when a handover is rushed.
Why the notebook always fails
A handwritten log has three built-in weaknesses: one person's handwriting is unreadable to another; entries are written but never marked done, so the next shift has to ask around from scratch; and looking up something from last week means turning pages. It also lives only at the desk, so a manager who wants to know what happened overnight has to wait until they are physically there.
Every task needs an owner and a state
A handover that works needs three things per item: who is responsible, what state it is in, and when it is due. Without a state, nobody knows whether it is closed. Without an owner, the task belongs to everyone, which means it belongs to no one. This is precisely where a task list with states beats a notebook.
Connect the handover to the guest record
Last night's complaint only has value if the person on duty knows about it when the guest returns. Written in a logbook, that information dies with the book. Written into the guest record, it becomes that person's preference and thing to avoid, visible to whoever is on duty next — including someone who started last week.
Who did what, and when
When something is disputed — a missing item, a cash discrepancy, a guest saying they reported something nobody acted on — what settles it is an activity log tied to individual accounts. That requires each staff member to have their own login, and for that login to be the same person who holds the shift in the roster. Share one account across the desk and every log entry becomes meaningless.