A hotel is one of the very few businesses that genuinely never closes. There is no last customer, no register pulled, no lights out. The doors stay unlocked, the phones stay live, and the operation keeps running twenty four hours a day, every day. The only thing that changes is which team is holding it. That single fact shapes everything about how a front office works, because it means the building is really running one endless shift, passed from hand to hand three times a day. The moments when it changes hands are the shift handover, and they are where a well run operation quietly succeeds or quietly comes apart.
I have worked most seats on that clock, from night audit at a resort in Waikiki to leading rooms operations in San Francisco, and I have learned that the handover is not a courtesy you extend to the next shift when you have time. It is a discipline, and it is load bearing. The difference between a property that feels seamless to guests and one that feels like it forgets things is very often nothing more than the quality of what gets passed between shifts at the seams.
What is a shift handover, and why does it carry so much weight?
A shift handover is the structured transfer of the operation when one team clocks out and the next clocks in. On a front desk that usually means three of them a day: the AM team hands off to the PM team, the PM team hands off to overnight, and overnight hands the building back to the AM lead in the morning. Each handoff carries the live state of the operation from one set of hands to the next.
The term itself is worth stating cleanly.
Because the building never resets, that transfer is the one thing keeping three teams from starting over three times a day.
The reason it carries so much weight is that a hotel has no reset. In a business that closes, the end of the day wipes the slate. Whatever was half finished either gets done before closing or waits neatly until tomorrow. A hotel has no such mercy. The guest who was promised a callback at nine is still expecting it at nine whether or not the person who promised it is still on shift. The room held for a late arrival is still held. The service recovery in progress on the fourth floor is still in progress. All of it keeps moving, and if the outgoing team does not deliberately hand it over, it does not pause politely. It simply gets dropped, and the guest is the one who discovers the gap.
The handover is the connective tissue
I think of the three shifts as three sections of a relay, and the handover as the baton. A relay is not won by the fastest runner. It is lost by the dropped baton. You can have a brilliant AM shift and a sharp PM team, and if the exchange between them is fumbled, the guest experiences the fumble, not the brilliance. This is why, when I talk about how a front office actually runs, I keep coming back to the seams. The shifts get the attention. The seams do the quiet work of making three teams behave like one.
A relay is never won by the fastest runner. It is lost by the dropped baton, and the guest is the one who watches it fall.
What makes this hard is that the information a handover has to carry is exactly the information that lives most easily in one person's head. The routine state of the building is in the system, and anyone can read it. What the system does not hold well is the context: the promise made verbally to a guest, the reason a particular room is being held, the history of a complaint that is halfway to resolution, the reservation you already know is going to be a problem at nine because of something the guest said at four. That soft, situational knowledge is the whole value of a handover, and it is precisely the part that evaporates the moment the person carrying it walks out the door.
What actually belongs in the pass-down?
A good pass-down is not a diary of the shift. Nobody needs a play by play of a quiet Tuesday. It is a transfer of everything still in motion, the open loops the next team is going to have to carry or close. When I hand off, I am asking myself one question about every item: is this finished, or does it land on the next person? If it lands on them, it goes in the handover, with enough context that they can act on it without coming to find me at home.
In practice that means a short list of specific, current things. The pending arrivals still out and the rooms being held for them, so nobody releases a room a late guest is coming for. Any service recovery in progress, what happened, what was promised, and what is still owed. Out of order rooms and maintenance issues that affect what the desk can sell or assign. VIP and group notes, the arrivals that need special handling on the incoming shift. Anything financial left open on a folio. And, above all, the one or two situations I already know are going to become a problem, flagged clearly, because a problem seen coming is a problem the next team can get ahead of instead of getting hit by.
What a clean handover always carries
- Pending arrivals and held rooms. Who is still due, and which rooms are spoken for, so nothing gets released by accident.
- Service recovery in progress. What happened, what was promised, what is still owed. The next team should be able to keep the promise you made.
- Out of order rooms and maintenance. Whatever changes what the desk can actually sell or assign.
- VIP, group, and special handling notes. The arrivals that cannot be treated as routine.
- The known problems. The one or two situations you can already see coming, named plainly so the next shift meets them ready.
Most of that also belongs in writing, not only in conversation, because a spoken handover on a busy evening is easy to half hear and impossible to reread at two in the morning. A living pass-down log gives the verbal handover a spine, so the next team has both the human context and a record they can return to when the night gets strange.
A worked example: two ways to hand off the same guest
Let me make the difference concrete with one item. Same situation, handed off two ways. A guest in room 812 complained that his room was not ready at checkin and waited forty minutes in the lobby. The PM lead comped his parking, apologized, and promised the front office manager would follow up personally in the morning.
The weak handover sounds like this: "Oh, and 812 was upset earlier, but I took care of it." That is a landmine dressed as a resolution. The incoming lead has no idea a promise was made, so when the guest comes down at nine expecting the manager, nobody is ready, the recovery unravels, and the guest is now twice as angry because the hotel broke a second promise on top of the first.
The clean handover sounds like this: "Room 812, Mr. and Mrs. Alvarez, waited forty minutes at checkin because their room slipped. I comped tonight's parking and promised them the front office manager would call or come by before ten tomorrow. It's in the log with the folio note. Please make sure the AM lead flags it for the manager first thing." Same event, thirty seconds longer, and now the promise survives the shift change. The guest gets the followup he was told to expect, and a bad first impression turns into a story about a hotel that keeps its word. That gap, between "I took care of it" and the specifics, is the entire craft of a handover.
Why do handovers fail?
Handovers rarely fail because someone lacked information. They fail on two things: vagueness and assumption. Vagueness is the pass-down that says the shift was fine and everything is handled, when three things are actually still open and just were not mentioned because the outgoing person was tired and the line was long. Assumption is the outgoing lead believing the incoming lead already knows something, the promise, the held room, the history, because it is so vivid in their own head that it feels like shared knowledge. It is not shared until it is said.
The antidote to both is specificity, and a small amount of humility about memory. I do not trust my own recall at the end of a long shift, and I do not ask the next person to trust theirs. If a guest was promised a callback, that goes down in words, with the room number and what was promised, not as a mental note I intend to mention. The moment an open commitment to a guest lives only in the memory of someone who is about to go home, the handover has already failed. The guest just does not find out until the callback never comes.
How do you actually run the handover?
The mechanics are simpler than people make them. A handover is a short, deliberate overlap where the outgoing lead walks the incoming lead through the open loops, backed by something written the incoming team can return to later. I keep it structured so it does not drift, and the structure is easy to hold in your head as five moves in order:
- Where the house stands. Occupancy, the count, anything tight about tonight's inventory.
- What is still out. Pending arrivals and the rooms being held for them, so nothing gets released by mistake.
- What is in progress. Service recovery underway, what was promised, and what is still owed.
- What is broken. Out of order rooms and maintenance issues that change what the desk can sell.
- What you are worried about. The one or two situations you can see coming, said last so they land clearly and are the thing the next lead walks in remembering.
The overlap matters. A handover shouted across a busy counter as one person is putting on their coat is not a handover, it is a hope. I want a few real minutes where the outgoing person is still present and the incoming person can ask questions, because the value is often in the followup question, the detail that only surfaces when someone asks why a particular room is being held. That short overlap is cheap insurance against a long night spent reconstructing something that could have been said in thirty seconds.
I also try to hand off calm, not just information. How the outgoing lead frames the shift shapes how the incoming lead walks into it. If I dump a pile of half explained problems and leave, I have handed over anxiety instead of a plan. If I walk them through what is open, what is handled, and what to watch, I have handed them a shift they can actually run. The tone of a handover is part of its content, and on a hard night it is a real part of whether the next team steadies or spirals.
The overnight seam is the sharpest one
Every handover matters, but the seam around overnight is the one I watch most closely, because overnight is the quietest shift and carries the strangest weight. It takes the late arrivals, handles the problems no one else is awake to see, and runs the night audit that closes the day's books and rolls the system into the next date. The PM team hands overnight a building that is still winding down, and overnight hands the AM lead a building that is about to wake up. Both of those exchanges happen when energy is lowest and the temptation to cut the pass-down short is highest.
That is exactly why they deserve the most care. A problem handed cleanly from PM to overnight gets solved in the quiet hours instead of exploding at the morning rush. A tight handover from overnight to the AM lead means the person opening the day inherits a clear picture, the audit done, the exceptions flagged, the morning's known issues named, rather than spending the first hour reconstructing a night they were not there for. The whole of the AM shift is built on the quality of that one early morning exchange.
What separates a strong handover from a weak one
If you want a quick test of whether a pass-down is any good, hold it against a few markers. A strong handover is specific where a weak one is general. It names the guest and the room number where a weak one says "someone was upset." It states what was promised where a weak one says "handled." It puts open commitments in writing where a weak one keeps them in memory. It ends on the known worry where a weak one ends on relief. And it happens as an overlap where a weak one happens as an exit. None of those differences take talent. They take the decision to treat the next shift as a colleague you are setting up to win, rather than a shift you are finally free of.
Held against a few markers, the two kinds of handover separate cleanly.
| Marker | Weak handover | Strong handover |
|---|---|---|
| Detail | "The shift was fine" | Names the guest and the room number |
| Recovery | "I handled it" | States what was promised and what is owed |
| Open commitments | Kept in memory | Written in the log |
| How it ends | On relief | On the known worry |
| How it happens | As an exit | As an overlap |
None of the strong-side moves take talent; they take treating the next shift as a colleague you are setting up to win.
None of this is complicated, and that is rather the point. A clean handover does not require a special talent. It requires treating the next shift the way you would want the previous one to treat you: honestly, specifically, and without leaving anything important stranded in your own head. Do that three times a day, every day, and three separate teams start to behave like one continuous operation. Skip it, and the guest is the one who feels the seam, in a callback that never came, a room that was released, or a promise that walked out the door at the end of somebody else's shift.