The Floor Manager Handover
Two managers, one venue, and forty seconds of conversation at the door. What actually has to move between shifts, why verbal handovers fail on the busy nights, and the six-line format that survives a Saturday.
The night manager arrives at nine. The evening manager leaves at ten. In between there are sixty minutes in which everything one of them knows has to reach the other, and on a quiet Tuesday it does.
On a Saturday it does not. On a Saturday the outgoing manager is on the floor solving something, the incoming manager is already being pulled into the door queue, and the handover happens in about forty seconds near the coat rail. The information that survives that forty seconds is whatever was most recent — not whatever was most important.
This is not a discipline problem. It is a format problem.
What actually needs to cross the shift
Most venues, asked to list what a handover should cover, produce something with eleven items on it. Eleven items is a document nobody writes on a busy night. The list that survives contact with a Saturday has six.
1 Who is short — which section or station is a person down
2 Who is watched — a guest, a member of staff, a table
3 What is broken — anything that changes what you can sell
4 What is promised — a comp, a table hold, a callback
5 What is money — the float, a large tab, a disputed bill
6 What is open — anything the next manager has to close
Everything else is either already in the system or does not need to travel.
Why "what is promised" is the one that hurts
Of those six, the item that causes the most damage when it is dropped is number four.
A guest is told the manager will sort something out. The manager leaves. The guest asks the next manager, who knows nothing about it, and now the venue has two problems: the original one, and the fact that the guest was told something that did not happen.
⚠️ The guest does not experience this as a handover failure. They experience it as being lied to.
⇒ Related: The Complaint That Never Reached You
Why "what is watched" is the one that gets forgotten
A member of staff who has been having a bad night. A guest who has been warned once. A table that has been loud but not yet a problem.
None of these are incidents yet. That is exactly why they do not get written down — and exactly why they need to travel. The next manager will meet the second incident without knowing there was a first.
⇒ The Incident Log You Do Not Keep
Why verbal handovers fail on the nights they matter
The paradox of the verbal handover is that it works perfectly on the nights when nothing needs to be handed over.
Quiet Tuesday — 15 minutes free, nothing to report, excellent handover
Busy Saturday — 40 seconds, six things to report, one gets through
The handover quality is inversely correlated with the need for it. Any process with that property will fail exactly when you are counting on it.
The three things that get through
When it collapses to forty seconds, what survives is:
- Whatever happened in the last twenty minutes (recency)
- Whatever the outgoing manager found personally annoying (salience)
- Whatever the incoming manager happened to ask about (luck)
Note that "important" is not on that list.
The format that survives a Saturday
The fix is not a longer handover. It is a handover that has already been written before the busy hour starts.
Write it at the point the information appears
The outgoing manager does not sit down at 9:45 and try to remember six things from a five-hour shift. They add one line at the moment each thing happens.
21:10 Section 3 down one — Maria covering, needs relief by 23:00
22:40 Table 12 comped two drinks — approved by me, spillage
23:05 Card reader 2 intermittent — using 1 and 3 only
Three lines, written in about nine seconds total, across two hours.
⭕ The handover is then a thing that is read, not a thing that is recalled.
⇒ The First Fifteen Minutes Of A Shift
Where it lives matters more than what it says
⛔ A phone note belonging to one manager — leaves the building with them
⛔ A group chat — scrolls away, nobody reads back
⛔ A paper pad behind the bar — gets wet, gets lost, gets binned
⭕ The same place the shift record lives
If the handover lives somewhere other than the operational record, two things happen: it gets written less often, and it cannot be looked at three weeks later when someone asks what happened.
⇒ The Board In The Dressing Room
The handover in the other direction
Almost every venue treats handover as one-directional: outgoing tells incoming. The reverse direction is thinner but not empty.
Incoming manager knows:
- What the bookings look like for the rest of the night
- Who called in sick for tomorrow
- What the owner asked for this afternoon
The outgoing manager, walking out, is the last person who can act on the first of those cheaply. If the bookings for the next two hours are heavier than the current staffing, the outgoing manager can still make a call on the way out. Thirty minutes later that call costs a lot more.
What this looks like when it is working
Test one: ask the incoming manager at midnight
Two hours into the shift, ask the incoming manager what the outgoing manager was worried about.
Working — they name two things and both are real
Not working — they name the most recent thing, or nothing
Test two: look for the second incident
Pull any incident from the last month that involved a guest or a member of staff who had also been involved in something earlier the same week.
Working — the manager who handled the second one knew about the first
Not working — they found out afterwards
⚠️ Most venues fail test two and do not know it, because the failure is invisible unless you go looking.
Test three: count the promises
Over one week, count how many times a guest was told a manager would do something, and how many of those were actually done.
⇒ This is usually the number that convinces an owner the format is worth the nine seconds.
The parts nobody hands over
Three categories reliably fall through, in every venue, regardless of format.
Suppliers and deliveries
Something arrived short. Something did not arrive. Nobody tells the night side, because the night side does not order — but the night side is the one who runs out at one in the morning.
⇒ Par Levels And The Money Sitting In Your Store
The float and the till
Money is handed over more carefully than anything else, and still gets handed over as a number rather than as a state. "Float is right" is not the same as "float is right and the second drawer has not been counted since eight."
Anything involving the owner
The owner comes in at eight, asks for something, and leaves. The evening manager remembers. The night manager does not, because nobody told them, because the request was made to a person rather than to the venue.
⚠️ Requests made to a person do not survive that person going home.
Handover at the other boundaries
The manager change is the visible boundary. There are three quieter ones in the same night, and each drops a different category.
Door to floor
The door knows things the floor never hears: who was turned away, who came in with someone who was turned away last week, which group has already been drinking elsewhere.
⇒ The Door Count That Tells You Nothing
Bar to floor
The bar knows which table is running a large tab and which one has been ordering rounds it may not be able to settle. That is money information, and it usually travels only when it has already become a problem.
Floor to close
The last hour produces the highest concentration of things somebody has to remember: unpaid tabs, lost property, a guest who left something, a member of staff who left early.
What to do this week
Day one to three: write it, do not design it
Ask the two managers to add one line whenever any of the six things happens. Do not build a form yet. Three days of real lines will tell you what the form needs.
Day four: read the lines back
Sit with both managers and read what got written. Two things become obvious immediately: which of the six never gets used, and which category keeps appearing in a form nobody anticipated.
Day five onward: fix the storage, not the format
If lines are being written and still not read, the problem is where they live. Move them to the shift record before you touch the wording.
⚠️ Most venues do this in the wrong order — they redesign the format three times and never move it out of the group chat.
Three to hold
1 Six items, not eleven — a long handover is not written on a busy night
2 Written when it happens, not recalled at the end
3 Stored where the shift record lives, not on a phone
Where the record has to sit
A handover that lives in the same place as the shift record can be read later. A handover that lives in a chat cannot. The difference matters twice: once at ten o'clock when the next manager reads it, and once three weeks later when someone asks why a guest was told something.
⇒ The Month End That Takes Two Weeks
Read next
Related articles
The Split Check At A Big Table
Twelve people, one bill, and twenty minutes at the terminal while the queue builds. Why splitting is a floor-plan problem rather than a payment problem, and the four decisions that make it fast.
The Run Of Show For A Busy Night
A one-page timeline of what happens when, who owns it, and what has to be true before it starts. Why the venues that run smoothly are not the ones with better staff, and how to write one in twenty minutes.
The Float You Start The Night With
Three people, three answers about what the float is. Why an uncertain starting number makes every closing number uncertain, how much change a busy Saturday actually needs, and the five rules that end float arguments.
Map out your operations in 5 minutes
Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.
Your answers are not stored. The assessment runs entirely in your browser.
Try tasteck free for 30 days
No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.
- No card required
- Free data migration support
- All features unlocked for 30 days