The dropped ball I remember most was not a big dramatic failure. It was a promise. A guest had been told, on an afternoon shift, that a bottle of wine would be in their room to make up for a rough arrival. The person who made that promise wrote nothing down, told the next shift nothing, and went home. The wine never came. The next morning that guest was not just still upset about the arrival. They were upset that the property had looked them in the eye, promised to make it right, and then quietly forgotten. That is a worse failure than the original one, and it happened for a single reason. The handover did not hold.
A hotel never stops, but the people running the desk do. Every shift change is a moment where the property could lose its memory of what is open, what was promised, and what needs to happen next. The handover is the thing that prevents that, the deliberate act of passing the live state of the desk from the people leaving to the people arriving. When it works, a guest cannot tell the shift changed at all. When it fails, promises evaporate, arrivals get missed, and problems that were half-solved start over from zero. After years of running desks and leading teams, I have come to think the quality of a property's handovers tells you almost everything about how well it runs.
Why do handovers fail so often?
They fail for one reason above all others. They rely on memory. The classic broken handover is two people at the desk during the overlap, the outgoing agent rattling off a few things they remember while the incoming one half-listens and gets pulled away by a checkin. Whatever was not said in those thirty rushed seconds, or was said but not written down, leaves the building with the person who knew it. Human memory at the end of a long, busy shift is the least reliable system in the entire hotel, and a handover built on it is a handover that will drop things.
The second reason is vagueness. Even when things do get written down, they often get written in a way that helps no one. A note that says the guest in 812 was upset tells the next shift nothing they can act on. Upset about what? Was anything promised? Is it resolved or still open? A handover entry that raises an alarm without giving the next person a next step is almost worse than silence, because it creates worry without direction. What holds is the opposite of both failures. It is written, and it is specific enough that a person who was not there can pick up exactly where you left off.
A promise a guest can remember but your desk cannot is worse than no promise at all.
The three things every entry needs
I give my teams a simple test for any handover item. A good entry answers three questions, and if it is missing any of them, it is not done. What happened, what still needs doing, and who owns the next step. Miss the first and the next person lacks context. Miss the second and they know there is a problem but not the solution. Miss the third and everyone assumes someone else has it, which is how open items die.
- What happened. The facts, briefly. The guest in 812 had a late, dirty room at checkin and was offered a wine amenity in recovery.
- What still needs doing. The concrete next action. Wine has not yet been delivered; needs to reach the room before turndown tonight.
- Who owns it. A name, not a department. Assigned to the evening supervisor to confirm delivery and note it back on the profile.
Put those three together and the wine gets delivered no matter who is standing at the desk when the time comes, because the item carries its own instructions. That is the whole design goal of a handover. Every open thing should be able to survive the person who created it going home.
A pass-down entry, written well and written badly
The difference is easiest to see side by side. Here is the same situation logged two ways.
- Weak: "812 upset, comped something." Nobody can act on this. Upset about what, comped what, is it done?
- Strong: "812 (Nakamura, checkin 3pm) got a late, dirty room. Offered wine amenity in recovery. NOT yet delivered. Evening supervisor to send before turndown and note on profile. Guest back from dinner ~9pm." Any agent can finish it without finding you.
Notice what the strong entry carries: the room and guest name, so the next person can find the reservation fast; the facts, so they have context; the open action with a deadline; and a named owner. That is roughly forty words, and it makes a promise portable across three shifts. The weak entry is six words and portable across zero.
Broken into the parts that matter, the two versions do not even belong in the same column.
| Element | Weak entry | Strong entry |
|---|---|---|
| Room and guest | "812" only | 812, Nakamura, so the next agent finds the reservation fast |
| What happened | "upset" | Late, dirty room at a 3pm checkin |
| Open action | "comped something" | Wine amenity offered, not yet delivered |
| Deadline | None | Before turndown; guest back from dinner around 9pm |
| Owner | None | Evening supervisor to send and note the profile |
The strong column is what makes the promise portable across three shifts; the weak column is what makes it evaporate at the first handoff.
The logbook and the pass-down
The workhorse of the handover is the logbook, the running record of what is open and what happened. Some properties keep it in a system, some in a shared document, some still in a physical book, and honestly the format matters less than the discipline. What matters is that it is the single agreed place where the state of the shift lives, and that everyone reads it at the start of their shift and writes to it during. A logbook nobody reads is just a diary. A logbook the whole team treats as the source of truth is the memory of the desk.
When I set a logbook standard for a team, I want every shift to close with the same categories covered, so nothing structural goes unmentioned. The running order I use is simple enough to keep in your head:
- Open service recoveries. Any guest situation still in progress, with the recovery offered and whether it landed.
- VIPs and special-request arrivals. Loyalty tier, the request, and whether the room is already blocked for it.
- Room moves and out-of-order rooms. What moved, why, and which rooms engineering still owns.
- High balances and folio flags. Anything the next shift or the night audit needs to watch before it posts.
- House state. Sold-out night, a large group departing, a fire panel test at six, anything unusual about the building.
A log that hits those five every shift is one the incoming team can trust on sight, because they learn it always tells the whole story rather than whatever the outgoing agent happened to remember.
The pass-down is the live conversation on top of the log, the few minutes at shift change where the outgoing lead walks the incoming one through anything that needs a human voice. The mistake is treating the pass-down as the handover. It is not. It is the highlight reel that points the incoming shift at the important entries in a log that already contains everything. If the pass-down is carrying information that exists nowhere else, you are one distraction away from losing it. The verbal handoff should add color and emphasis to a written record, never replace it. I get into how to structure that conversation and the rest of the desk's rhythm in the systems that run a modern hotel.
Where traces make the handover hold
Here is the piece that separates a handover that holds for one shift from one that holds across days. The logbook is good at the present. It tells the next shift what is open right now. But a lot of what gets promised at a desk is not for right now. It is for tomorrow, or for the guest's next stay, or for a specific date three weeks out. A logbook is the wrong tool for that, because by the time the date arrives, the entry has scrolled off into history and no one is looking at it.
That is what traces are for. A trace is a scheduled reminder inside the PMS that resurfaces an item on the exact day it matters, attached to the reservation or the guest profile so it appears in front of whoever is working then. The wine that needs to arrive tonight can be a logbook item. The connecting rooms a returning family needs on their reservation next month has to be a trace, because no logbook entry survives that long. I get into the full machinery of this in trace and task systems guests never see, and it is the tool that turns a shift handover into something that holds across time, not just across the eight o'clock overlap.
The rule I use is straightforward. If it needs to happen during this shift or the next, it goes in the log. If it needs to happen on a future date, it goes in a trace. The best desks use both together, and the handover pass-down explicitly checks that anything future-dated has been traced, not just logged. That belt-and-suspenders habit is what stops a promise made today from vanishing before its day comes.
The handover into the overnight
Every handover matters, but the one into the overnight shift carries a special weight, because the night team is small, the property is quiet, and the next set of eyes on many issues will not arrive until morning. Anything dropped at the evening-to-night handover has hours to grow before anyone catches it. The night auditor is also about to run the daily close, so anything that affects the books, an open balance, a comp that needs posting, a room status that is wrong, needs to reach them before they start balancing. I spent enough overnight shifts to know how much easier the audit goes when the evening team handed it over clean, and how much harder it gets when they did not. I get into that close itself in how night audit actually works.
So the evening handover into the overnight deserves extra care. Walk the night team through the open items, confirm the arrivals still expected late, flag any guest situation that could escalate while the building is quiet, and make sure anything touching the folios is visible before the audit runs. A clean handover into the night is a gift to two shifts at once, the overnight team who runs the close and the morning team who inherits its output.
Building the habit across a team
A handover process is only as strong as the weakest person practicing it, which means this is a leadership job, not a template job. You can hand a team the perfect logbook format and still get dropped balls if the culture treats writing things down as optional busywork for after the guest leaves. The standard has to be visible, modeled, and reinforced until it is simply how the desk operates.
- Model it yourself. When you close a shift, write the entries the way you want the team to write them. People copy what their lead actually does.
- Read the log out loud at pass-down. Making the log the center of the handover conversation trains everyone to trust it and keep it current.
- Close the loop visibly. When an item gets handled, note the resolution so the next shift sees the story finished, not just opened.
- Coach the weak entries. When a handover note is vague, rewrite it with the person, so they learn what specific looks like.
The reason this is worth the effort is that a handover that holds is invisible when it works and catastrophic when it fails, and guests only ever feel the failures. The bottle of wine that arrives on time gets no notice. The one that never comes turns a recoverable mistake into a story the guest tells about a hotel that forgets its own promises. Every entry your team writes well is a small insurance policy against exactly that outcome.
The habit also protects the team from something subtler than dropped balls, which is blame. When a handover is weak and something falls through, the property spends the next morning arguing about who was supposed to catch it, and that finger-pointing corrodes a team faster than the mistake itself. A written, owned handover ends that argument before it starts, because the record shows plainly what was passed and to whom. I would rather my team spend that energy on guests than on defending themselves, and a clean pass-down is what buys that. It turns handover from a moment of risk into a moment of clarity, where everyone leaving and everyone arriving knows exactly where things stand.
Nothing gets dropped when the people change
That is the whole standard, stated plainly. A guest should never be able to tell that the person who promised them something has gone home. The wine arrives. The VIP is recognized. The service recovery in progress keeps progressing. The connecting rooms are ready next month. None of that depends on any one person remembering, because the property remembers through its logbook and its traces, and the handover is the discipline that keeps that memory intact across every shift change.
So build the handover like it matters, because it does. Write every open item with what happened, what is next, and who owns it. Keep the log as the source of truth and let the pass-down point at it rather than replace it. Trace anything future-dated so it resurfaces on its day. Give the overnight handover the extra care it deserves. Do that consistently and the seams between shifts disappear, which is exactly what a guest should experience of a property that runs around the clock. The people change all day and all night. The care does not.
Questions from the desk
What is a shift handover at a hotel front desk?
It is the structured pass-down from one shift to the next, covering open issues, pending arrivals and VIPs, service recoveries in progress, and anything the incoming team needs to act on. A good handover means nothing that was live at the desk gets dropped when the people change.
What should a front desk pass-down log include?
Open items with an owner and a next step, VIP and special-request arrivals, service recoveries in progress, room moves and out-of-order rooms, high balances, and anything unusual about the house. Each entry should tell the next person what happened and what still needs doing.
Why do handovers fail?
Because they rely on memory and verbal handoff alone. When a busy shift ends, details that were never written down leave with the person who knew them. A handover holds when it is written, specific, and tied to a system that resurfaces the item on the right day.
What is the difference between a logbook and a trace?
A logbook records what happened and what is open right now. A trace is a scheduled reminder inside the PMS that resurfaces an item on a future date. The logbook holds the shift; the trace makes sure a future task does not get forgotten between now and then.
How long should a shift pass-down take?
Five to ten minutes for a normal day, longer on a heavy one. The written log carries the detail, so the verbal pass-down only needs to point the incoming lead at the live items, confirm late arrivals and VIPs, and flag anything that could escalate. If the conversation runs long because nothing was written down, that is a sign the log is being skipped.
What makes a handover into the overnight shift different?
The night team is small and the next set of eyes will not arrive until morning, so anything dropped has hours to grow. The night auditor is also about to run the daily close, so open balances, comps that need posting, and wrong room statuses have to be visible before the audit runs. Walk the night lead through open items, late arrivals, and any folio issue by name.