The Front Office Pass-Down Log

Most hotels have a logbook, and most logbooks are close to useless. They fill up with entries like "see PM about 412" and "guest in 908 was upset, handled it" and "watch the group on 6." Each of those was clear to the person who wrote it and means almost nothing to the person who reads it four hours later. The information that mattered lived in the writer's head, and the note was just a reminder to a memory the next shift does not have.

I care about the front office pass-down log more than almost any other tool on the desk, because it is the one thing that lets a twenty-four hour operation remember itself. A hotel does not close. There is no moment when everyone goes home, the doors lock, and the day resets. The operation runs continuously, handed from AM to PM to overnight and back, and every one of those handoffs is a chance to lose something. The log is the connective tissue that keeps information from falling into the gaps between shifts. When it is written well, nothing gets rediscovered by the next team, or worse, by the guest.

What the log is actually for

Before going further, it helps to pin down what this record actually is.

That definition is narrow on purpose, and most of what follows is really just working out what it leaves out.

The purpose of the pass-down log is narrow and specific: to carry the things the next shift needs to act on that they cannot see for themselves. That last part is the key. The system already knows who is arriving, which rooms are occupied, and what the house count is. Nobody needs a log entry to repeat what the screen shows. The log exists for everything the screen cannot tell you: the context, the promises, the in-progress situations, the judgment calls that are still open.

A guest in 908 was upset about a noise issue, we moved her to 1104, comped nothing but promised the manager would call her in the morning to follow up. That is a log entry, because none of it is visible in the system and all of it has to happen. The system shows a room change. It does not show the promise. If the morning shift does not know about that call, the guest waits by the phone, nobody rings, and a situation we had handled becomes a situation we broke. The log is where the promise lives until it is kept.

What belongs in it, and what does not

The most common failure of a logbook is not too little information. It is too much. When people write down everything, the log becomes a wall of noise, and the incoming shift stops reading it because the signal is buried. A log nobody reads is worse than no log at all, because it creates the illusion that things were passed down when they were not.

So the discipline is subtraction. The log holds only what the next shift must act on or know to avoid a mistake.

• Open guest issues. Anything unresolved: a complaint in progress, a promise made, a service recovery that is not finished.
• Held and blocked rooms. Rooms held for late arrivals, rooms set aside for a VIP, rooms out of order, with the reason attached.
• Followups with a time. The call due at nine, the guest expecting a callback, the delivery that has to reach a room by a certain hour.
• Anything unusual about the house. A large group with special handling, a floor with a maintenance issue, an oversell that needs watching.
• Judgment calls still open. A decision you started but could not finish, with enough context that the next person can finish it your way.

Notice what is not on that list. Routine transactions, completed and closed items, anything the system already displays. If it is done, it does not go in the log except to confirm it is done. If the screen shows it, the log stays quiet. The log carries what the system cannot, and nothing else.

A log entry is a message to someone who was not there. If they need to call you to understand it, you did not write it, you just reminded yourself.

How do you write an entry the next shift can use?

The test I hold every entry to is this: could someone who was not there act on this correctly, right now, without asking me a single question? If the answer is no, the entry is not finished. That single standard fixes most bad logs, because it forces you to write for the reader instead of for yourself.

A usable entry has four parts, and they are quick to write once you know them. State the subject, the room or the guest. State what happened, factually. State what has already been done. State what still needs to happen, and when. Here is the template I teach, four fields in one line:

1. SubjectRoom 412, or the guest name and room together.
2. What happenedThe AC would not cool, reported at 8pm.
3. What was doneEngineering assessed, parts needed, guest moved to 418 for the night, 412 set out of order.
4. What is next, and whenEngineering followup in the morning; do not sell 412 until cleared. Status OPEN.

Run together, that reads: "Room 412, guest reported the AC not cooling at 8pm, engineering assessed and parts needed, guest moved to 418 for the night, 412 now out of order, needs engineering followup in the morning and should not be sold. OPEN." That entry closes itself. Anyone can read it and know exactly the state of things and the next action, with no phone call required.

Compare that to "412 AC broken, moved guest, see engineering." Same facts, useless delivery. Is 412 sellable? Where is the guest now? What does engineering need to do? The reader has to reconstruct all of it, which usually means finding the person who wrote it, which defeats the entire purpose of writing it down. The log is not a personal note. It is a message to a stranger, and the discipline is to write it that way even when you are tired and the shift is ending.

The two habits that make a log trustworthy

Two small habits separate a log people trust from one they ignore. The first is marking status plainly. Every item is either open or closed, and the reader should never have to guess which. An entry that trails off without saying whether it is resolved is worse than useless, because it makes the next shift do detective work to find out if a problem is still live. I want open items to announce themselves and closed ones to confirm they are done, so a lead can scan the log and instantly see what still needs hands on it. On a digital log I flag open items so they carry forward until someone closes them; on paper I keep a running open list at the top of each shift so nothing quietly ages out.

The second habit is timestamping. When something happened matters, because a complaint logged at nine and a complaint logged at midnight call for different responses. A log without times flattens the night into one undated blur, and the incoming shift loses the sequence that would have told them what to prioritize. A followup marked "call the guest" is a wish; a followup marked "call the guest by 9am" is an instruction the morning can act on and be held to.

Common mistakes that quietly break a log

When I audit a struggling logbook, the same failures show up again and again. Knowing them by name is half of fixing them.

• The private shorthand. "See me about 6" means nothing to a stranger. Write for the reader, not for your own memory.
• The open item with no owner or time. "Guest wants a callback" without who, or by when, is an item that will never get done.
• Logging the obvious. Repeating what the arrivals report already shows buries the two entries that actually matter.
• The trailing-off entry. Notes that describe a problem but never say whether it was resolved force the next shift into detective work.
• The emotional dump. "908 was a nightmare, do not deal with them" tells the next shift how you felt, not what they need to do.

The log and the verbal handover

The written log does not stand alone. It works together with the face-to-face handover, and the two do different jobs. The log is the durable record, the thing that stays and can be checked at three in the morning when a guest calls about something from yesterday. The verbal handover is the emphasis, the "the one thing you really need to watch tonight is the group on six." Neither replaces the other. A log without a conversation misses the human weight of what matters most; a conversation without a log loses everything the moment the incoming lead gets pulled away.

The strongest handovers use both deliberately. The written entries capture the full picture so nothing is lost, and the spoken pass-down points at the two or three things that deserve real attention. That pairing is the heart of running a clean shift handover, and the log is the half that survives after the conversation ends. When I train new leads, I tell them the log is what protects the guest from your memory, because your memory clocks out and the guest's problem does not.

The log also protects the property in a way people do not think about until they need it. When a guest calls three days later disputing something, or a manager needs to understand how a situation was handled, the log is the record of what actually happened and when. It settles arguments that would otherwise come down to one person's recollection against another's. I have seen a clear entry resolve a complaint in thirty seconds because the whole history was right there, timestamped and factual, and I have seen a missing entry turn a simple question into an hour of asking around. A good log is not just an operational tool for the next shift. It is the institutional memory of the desk, and in a business where the same guests and the same issues recur, that memory has real value beyond the single handover it was written for.

Paper book or digital log?

People ask which format is right, and the honest answer is that the format matters far less than the discipline. That said, the tradeoffs are real. A digital log, whether a field inside the property management system or a shared shift note, has three advantages: it timestamps itself, it is searchable when you need to reconstruct a week-old incident, and it cannot be left in a drawer or walk out the door. Its risk is that it can become a dumping ground, because typing is cheap and the wall of noise creeps back in. A paper book forces brevity by the physical effort of writing, and it sits open on the desk where nobody can pretend they did not see it, but it cannot be searched, it is easy to lose, and a bad handwriting habit can make an entry as useless as bad shorthand.

Laid side by side, those tradeoffs get easier to weigh.

The grid does not decide it for you, since the discipline still does, but it shows why searchability and permanence tip me toward digital on most desks.

For most properties I default to digital, because the searchability and the permanence outweigh the discipline cost, and because open items can be flagged to carry forward automatically instead of relying on someone to recopy them. For a small operation with three people who all read every shift, a clean paper book is completely fine. What is never fine is the split log, half in the system, half in a notebook, half in someone's head, because then no single place is the truth and every reader has to check three of them.

The overnight log is a special case

The pass-down log matters on every shift, but it does something particular overnight. The graveyard shift catches the problems no one else is awake to see: the late arrival with no room, the two a.m. maintenance call, the folio discrepancy caught during the audit. Those things happen in the quiet hours and would vanish by morning if the overnight team did not write them down. The log is how the night hands the day a clean starting point instead of a set of mysteries.

I spent enough time on overnight to know how much of what I logged at three in the morning shaped someone else's eight o'clock. A room I found occupied with no registered guest, a charge that did not reconcile, a guest who came in furious about a booking error and needed a manager in the morning: none of that is visible in the daylight unless the night writes it forward. That closeout is part of the larger work of the overnight, which is why the log sits right alongside the reconciliation in what the night audit really does. The audit squares the numbers. The log squares the story.

From log to the start of the shift

A well kept log has one more payoff: it feeds the start of the next shift. The incoming lead who reads a clean log knows, before the doors even get busy, exactly what is open, what is held, and what to watch. That reading is what turns into the morning briefing where the whole desk gets aligned. The log is the raw material, and the huddle is where it becomes a shared plan, which is the link between the pass-down and the daily stand-up that sets the shift. A vague log produces a vague briefing. A precise one lets the lead walk in already knowing the day.

None of this is complicated, which is exactly why it gets neglected. Writing a good log entry takes maybe thirty extra seconds over a lazy one, and those thirty seconds are the difference between a promise kept and a guest let down, between a room correctly held and a double-booked mess at ten p.m. The log is unglamorous, and it is one of the truest tests of whether a desk is professional or just busy. The team that writes for the next shift is the team that trusts the operation more than its own memory, and in a building that never closes, that trust is the only thing that holds the twenty-four hours together.