A Shift Handover Note a Night Manager Can Use

Most handovers fail because they are written for the person leaving, not the person arriving. Four columns fix that.

Last updated: October 30, 2026

A handover note is the cheapest control a small property has. It costs eight minutes and it catches the things nobody remembered to say out loud. Most of them fail for a boring reason: the outgoing shift writes down what it did, and the incoming shift needed to know what's still unfinished.

Key Takeaways

• Write for the reader, not the record. A handover is a briefing, not a diary of the shift that ended.
• Four columns are enough. Still open, changed, lands tonight, watch. Anything that doesn't fit one of them doesn't belong in the note.
• Every line needs a room and a time. "Guest unhappy" is not a handover. "Room 4, 22:10, asked about the boiler" is.
• Leave resolved items out. A note that lists everything gets skimmed, and skimming is how the one live item gets missed.
• Keep the notes. A week of them shows patterns a single shift can't see.

Four columns and nothing else

Free-form handovers fail in a predictable way. They start with the weather of the shift — how busy it was, who was on, what almost happened — and the actionable line ends up in the fourth paragraph, where nobody reads.

It usually looks like this. A guest messages at 23:40 about a shower that won't drain. The night manager logs it, sends maintenance a message, and writes two lines at the end of the shift. The morning person reads "busy night, shower issue handled" and moves on. Nobody calls maintenance, because "handled" meant the message went out. The complaint lands at checkout, and it's about the shower rather than about the message.

Four columns remove that choice. Each one asks a question the incoming shift will ask anyway, and each answer is short by construction: what's still open, what changed since the last note, what lands in the next shift, and what to watch.

The constraint is the point. A column that can hold anything holds nothing, because the reader has to read all of it to find the one line that matters. A column with a narrow question forces you to decide, at 06:50, whether an item is genuinely live or whether you're just reluctant to close it.

Nothing else goes in the note. No policy reminders, no rota commentary, no notes about how the shift felt. Those belong in a different document, and putting them here is how a handover grows to two pages and stops being read.

What belongs in each column

Still open. Anything you started and couldn't finish, and anything a guest is waiting on. A broken lamp reported at 20:00 that maintenance hasn't answered. A late check-out request nobody has confirmed. One line each, addressed to whoever picks it up next.

Changed. What moved since the previous note: a new booking, a cancellation, a rate you adjusted, dates you blocked, a room taken out of service. This is the column that stops the next shift working from a stale picture of the building.

Lands tonight. The arrivals, the guests in house, the departures, and anything about availability that a person would need to know before answering the phone. Names, rooms, times. If you're pulling this from four channels on one calendar, note where a booking came from when it changes how you'd handle it.

Watch. One thing, sometimes two. The guest who asked three questions about the boiler. The room next to a building site. The arrival whose flight is delayed and who hasn't messaged since. This column is where judgement goes, and it's the one that gets skipped when the shift runs late. A watch line should say what to do if the thing happens, not only that it might.

Two rules keep the columns honest. Every line carries a room and a time, because a line without them can't be acted on. And anything already resolved comes out, even if you spent an hour on it — the note is not where you get credit for the work.

Writing it in eight minutes

The note gets written at the end of the shift, not during it. Writing as you go produces a log, and a log is a different document with a different reader.

Start with the arrivals and departures you can see for the day, because that's the part that has to be right and the part that's easiest to check. Who's arriving, who's in house, who's leaving, and what the availability looks like for anyone who calls. That's a read of the day's state, not a memory exercise.

Then go to Still open and Changed, in that order. Both are short lists if you've kept up with them, and both force a decision: is this finished, or is it someone else's problem now? Write the answer, not the history.

Finish with Watch, and give yourself a limit of two items. If you have five, you don't have a watch list, you have a shift that needs an extra pair of hands, and the note should say that instead.

Eight minutes is realistic for a small property. It's also short enough that it survives a bad night, which matters more than a perfect template that gets abandoned in week two.

Two things will tempt you to skip it. A late arrival at 23:50, and a quiet shift that feels as though it needs no note at all. The quiet shift is the dangerous one, because the next person starts from nothing and spends the first hour asking questions the note would have answered in three lines.

What the next shift does with it

The incoming shift reads the note before it reads anything else. Then it ticks off what it has taken on, adds one line to Still open for anything it can't finish, and passes the note on.

That handover of the handover is where most systems break. A note that gets read and thrown away restarts from zero every day, and the same open item reappears for a week without anyone noticing it's the same item.

Keeping the notes fixes that cheaply. A week of them shows the room that keeps appearing in Watch, the arrival type that always runs late, the maintenance job that gets reported every Friday and closed every Monday. None of that is visible inside a single shift.

When the note and the guest disagree, believe the note first and then check the room. A guest who says nobody warned them about a maintenance visit may well be right, and the note will tell you whether a message went out or whether someone assumed it had.

One caution about the tool. The note is paper or a spreadsheet — it's a method, not a feature. What the software gives you is the raw material: today's arrivals, who's in house, who's leaving, and what's available, read in one place rather than four apps. localsbnb.com holds Airbnb, Booking.com, Agoda and Trip.com on one calendar, which is where those four lists come from before anyone writes them down by hand.

FAQ

How long should a handover note be?

Short enough to read standing up. If it runs past one page, the extra length is usually narrative rather than information, and the live items are buried in it. Cut the history first, then the resolved items, then anything the reader can look up in ten seconds.

Should the handover be on paper or in a shared file?

Either, as long as both shifts can reach it and it carries a date and a time. Paper works in a small property with one desk. A shared file works when people aren't in the same building. What fails in both cases is a verbal handover with no written record.

What if nothing happened during the shift?

Write it anyway, and write "nothing open" in the first column. A blank note and a note that says the building was quiet are different documents: the second one proves someone looked, and it gives the next shift a baseline to compare against.

Four columns won't make a bad night good. They will stop the same problem being discovered twice. localsbnb.com is where the arrivals, the in-house list and the departures are already visible, so the eight minutes go on judgement rather than on finding out what happened.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Working-time rules, record-keeping duties and safety obligations for staffed accommodation differ by jurisdiction; confirm what applies to your property with the competent authority before you change how shifts are run.