Shift handover best practices that actually hold

The worst nights I have run did not start on my shift. They started at the handoff, in the ninety seconds when the person leaving was already halfway out the door and the person arriving was still hanging up their coat. Somewhere in that gap a promise to a guest went unspoken, a room that was almost ready got recorded as ready, or a simmering complaint got left off the log because it had gone quiet for an hour. None of it looked like a problem at 3 p.m. All of it became mine by 7.

I learned to treat the shift change handover as one of the most important things a front desk manager does, not one of the least. It looks like paperwork. It is actually a leadership act. In the span of a few minutes you are handing another person a live floor, with guests midway through their stays and problems midway through their arcs, and asking them to carry it as if they had been there all day. Do that well and the night holds. Do it carelessly and you have set the next shift up to chase a night they never saw begin. Below is what I hand over, in what order, and the handful of habits that separate a handoff that holds from one that quietly falls apart at 9 p.m.

What a shift change handover at the front desk is actually transferring

Most weak handovers fail because they move the wrong thing. They move facts. Occupancy is at 92 percent, we have eleven arrivals left, room 1204 is a maintenance hold. All true, all necessary, and all of it available on a report the incoming manager can pull in thirty seconds without me. If that is my whole handoff, I have not led anything. I have read the screen out loud.

The thing worth transferring is state. State is the story behind the numbers. It is the fact that room 1204 is a hold because a guest reported a smell that housekeeping could not find, that the guest is a loyalty member who was gracious about it, and that I promised to call them personally by 6 with an answer. That is not on any report. It lives in my head, and if it does not make the jump to the next manager's head, the guest gets a broken promise and the incoming manager gets an angry call they cannot explain. When I ran rooms operations at the Marriott in Union Square, coordinating teams of sixty to ninety across a shift, the reports were flawless and the handoffs were still where nights lived or died. The system tells you the state of the building. Only a person tells you the state of the night.

A handoff is not a list of room numbers. It is a transfer of judgment.

So I built my handoffs around a single question: what does the next person need to know that they cannot look up? That question strips out the noise fast. It leaves the live threads, the things still in motion, the promises still owed, and the quiet worries I have not been able to shake. Those are the things that break a shift when they go unsaid, and they are exactly the things a report will never show. Everything else, the occupancy figure and the arrivals count, I let the screen carry, because the screen carries it better than my memory does.

The three things I hand over every time

Over the years the handoff settled into three buckets in my head. I do not read them off a card, but they are always there underneath, and they are the frame I would teach any new manager first.

• What is unresolved. Every open thread that has not landed yet: the guest waiting on a callback, the room change promised for when a suite opens, the group rooming list that is still short. If it is going to need someone's attention after I leave, it gets named, with a name and a number attached, not left as a vague "there was a thing with a group."
• What is likely to go wrong. The part that separates a real handoff from a status update. The arrivals stacked between 5 and 7, the agent who is having a rough day and might need a lighter section, the two connecting rooms I am holding that could get squeezed if a walkin comes in. I am handing over my read of the night, not just its current state.
• What has been promised. Anything a guest has been told to expect. A late checkout granted, an amenity sent, a rate adjustment agreed to at the desk, an upgrade held for an arrival. A promise the next shift does not know about is a promise the guest experiences as a lie.

When those three are across, the incoming manager is not inheriting a snapshot. They are inheriting the momentum of the night, which is the only thing that lets them get ahead of it instead of chasing it. This is really an extension of everything I believe about frontline hospitality leadership: the job is judgment under pressure, and a handoff is how you lend your judgment to the person taking your place.

A handoff, start to finish

Frameworks are easy to nod at and hard to use, so here is how a real change actually runs. Say I am closing an afternoon shift into evening on a near-sold-out night. This is the order I move in, and why each step sits where it does.

1. Read the log before I speak. Two minutes before the change, I scan my own written notes so the spoken handoff is organized, not a memory dump. I want the live threads at the top of my head before the next manager walks up.
2. Lead with what is unresolved. I start with the open guest issues, because those are the things that will ring a phone. "Room 1204, loyalty guest, smell complaint, callback owed by 6, housekeeping found nothing." One line, but it carries the whole promise.
3. Hand over my read of the next few hours. Then the forecast: where the arrivals stack, which agent is stretched, which held rooms are fragile. This is the part no report gives them.
4. Name every promise out loud. Late checkouts, comped amenities, rate adjustments, upgrades held. Each one gets said and, if it is not already, written down where the next three shifts can find it.
5. Cover the operational floor. Bank and cash status, out-of-order rooms, open incident numbers, anything pending with engineering. Short, but skipped at your peril.
6. Invite the questions. I stop and let the incoming manager push back. The followups they ask are usually the tell that something in my handoff was thinner than I thought.

The whole thing takes three minutes on a quiet night and closer to twelve on a hard one. What it never does is get skipped because the desk is busy. On a slammed change, one of us steps back and holds the line while the other runs the handoff, then we swap. The busier the floor, the more that state is worth transferring, because a busy floor is precisely the thing a report cannot reconstruct after the fact.

Written and spoken do different jobs

People ask whether a handoff should be a log or a conversation, as if you have to pick. You do not. They carry different loads, and dropping either one leaves a hole.

The written log is the memory. It holds the facts that must survive no matter how rushed the change gets: the maintenance holds, the VIP arrivals, the open incidents with their reference numbers, the bank count. Writing forces precision, and it leaves a record you can trace back to when something surfaces three days later. I learned that discipline on night audit at the Alohilani, where the whole job is a written account that has to survive to morning without me there to explain it. If it matters, it gets written down where the next three shifts can find it, in language a stranger could follow.

The spoken handoff carries what the log cannot. Tone. Worry. The context that makes a fact make sense. I can write "1204 on hold, guest notified" in a log. What I cannot write easily is that the guest was kind about it and I do not want them to feel forgotten, so please make that callback happen even if the smell was never found. That nuance is the difference between a guest who feels handled and one who feels handed off. It moves person to person, in a real exchange, or it does not move at all.

Laid against each other, the two channels carry different loads, and the gap in each is exactly what the other covers.

Neither column is optional, which is why I do both every change and treat dropping either one as leaving a hole the next shift falls into.

The handoff is a conversation, not a broadcast

The best incoming managers do not just receive a handoff. They interrogate it, gently. They ask the followup question I did not think to answer. Have we heard back from engineering? Is the group leader easy or anxious? What did the walkin situation look like an hour ago? That back and forth is where the real transfer happens, because it surfaces the things I stopped noticing after staring at them all day. A handoff delivered as a monologue, with the outgoing person talking at a nodding listener, almost always leaves something behind.

This is also why I never do a serious handoff while both of us are also working the desk. If the floor is busy at the change, one of us steps back for the two or three minutes it takes to do it properly. A handoff done over our shoulders while we both clear a line is a handoff half done, and the half that gets dropped is always the part that mattered.

Why the shift change is really about the guest

It is easy to think of the handoff as an internal thing, a courtesy between two managers. It is not. The guest does not experience two shifts. They experience one hotel that is supposed to remember them. When a guest has to explain their problem twice because the second manager never heard about it, the property has told them something true and unflattering: you are not being tracked, you are being processed.

The whole point of a strong handoff is to make the seam invisible. A guest should never be able to feel the moment one manager left and another arrived. The late checkout still stands. The callback still comes. The apology from the afternoon is still remembered at night. That continuity is a form of respect, and it is built entirely in the few minutes most people treat as throat-clearing before the real shift starts. The same logic held at the desk in Waikiki, where I ran an upselling program that added thirty to forty thousand dollars a month in room revenue. Every one of those upgrades was a promise stretched across shifts, and if a checkin agent on the next shift did not know a guest had paid to move rooms, the sale became a complaint. Continuity was not a nicety there. It was the revenue.

The reverse is true too, and it is why the handoff connects so directly to the start of a shift. A manager who receives a real handoff can spend the first hour of their shift setting the night up instead of decoding what they walked into. The quality of your first hour is largely decided by the quality of the handoff you were given. The two are the same joint, seen from either side.

Where handoffs quietly break: the common mistakes

After enough shift changes you learn the patterns of failure, and they are almost never dramatic. They are small omissions that compound. These four are the ones I watch for hardest, in myself first.

The first is the resolved-enough problem. Something flared earlier, got calmed, and by the change it feels handled, so it goes unmentioned. Then it flares again at 9 p.m. for a manager who has no idea it has a history. If it happened, it goes on the log, even if it seems over. Handoffs are the wrong place to be optimistic.

The second is the assumed knowledge. The outgoing manager knows the group in the ballroom is difficult, assumes everyone knows, and never says it. The incoming manager finds out the hard way. I try never to assume the next person carries the context I do. It costs ten seconds to say it and a ruined evening to skip it.

The third is the rushed change. Someone is late, or the desk is slammed, or the outgoing manager has somewhere to be, so the whole thing gets compressed into a wave and a "you're good, quiet night." Nights are rarely as quiet as the person leaving wants them to be. The rush is exactly when the handoff matters most, because a busy floor is precisely the state that is hardest to reconstruct from a report.

The fourth is the buried lede, the handoff that is technically complete but badly ordered, so the one thing that will define the night gets mentioned last, after the routine, when the incoming manager has already half stopped listening. Sequence is not decoration. Lead with the thing most likely to go wrong, and the rest can follow in any order.

All four come down to the same discipline, which is the same discipline behind reading the floor: paying attention to what is actually in motion instead of what is comfortable to say. A handoff is a reading of the shift, compressed and handed to someone else. If you cannot read your own floor, you cannot hand it over.

Who owns it when it breaks

There is one more reason to take the handoff seriously, and it is the one people least like to talk about. A clean handoff draws a clear line of accountability. When something goes wrong later, a good handoff makes it obvious where the responsibility sits. The outgoing manager owns what they knew and failed to pass on. The incoming manager owns what they were told and did not act on. That line is not about blame. It is about honesty, and about a team that can look at a failure clearly instead of arguing about who should have known what.

Vague handoffs blur that line on purpose, usually without anyone meaning to. When nobody quite handed anything over, nobody quite owns the miss, and the whole team learns that the seam between shifts is a place where responsibility goes to disappear. I would rather be the manager who over-communicates at the change, who names the awkward open thread even when it makes my shift look less finished, because that clarity is a gift to the person taking the floor from me. It says, plainly: here is everything I know, so that what happens next is yours to run and not yours to reconstruct.

If you want to get better at this, do one thing on your next change. Before you hand off, ask yourself the question: could this person run the next hour without calling me? If the answer is no, you are not done. Fill the gap, say the awkward part out loud, write down the thing you were tempted to leave off. The handoff that holds is not the tidy one. It is the honest one, delivered to someone you have decided to set up well.