The Handover That Happens In A Corridor
One manager leaves as the next arrives, and everything the first one knows is transferred in ninety seconds while both are walking. What gets lost, and the four-line handover that fixes it.
The day manager is leaving. The night manager is arriving. They pass each other, exchange about ninety seconds, and that is the handover.
Everything the first one learned in eight hours either fits into that ninety seconds or does not transfer at all.
What does not survive
The ninety seconds covers what is urgent. It reliably loses:
The thing that is about to become a problem. Not urgent yet, so it does not make the cut — and it lands on the night manager with no warning.
What a guest was promised. ⚠️ The most expensive omission. A guest arrives expecting something agreed at 16:00, and the person in front of them has never heard of it.
Why something was decided. The decision transfers; the reasoning does not. The next manager reverses it, reasonably, because they were not told what it was for.
Small observations. Someone seemed off, a supplier said something, a fitting is loose. Individually trivial and collectively how a venue is actually understood.
Why it stays a corridor conversation
Both people are at their worst moment for it. One is finishing, one is starting.
There is no format. With no structure, what gets said is whatever is most recent in the outgoing manager's mind — ⚠️ which is not the same as what is most important.
Nobody has said it is part of the job. It happens in the gap between two shifts, and gaps belong to nobody.
The four lines
Written, not spoken. It takes three minutes and it survives the shift.
What happened that the next person needs to know. Incidents, changes, anything unusual.
What was promised to whom. ⚠️ The single highest-value line. Every commitment made to a guest or a member of staff during the shift.
What is outstanding. Started and not finished, ordered and not arrived, raised and not resolved.
What to watch. The thing that is not a problem yet.
Four lines. Frequently three are empty, and the discipline is writing it even then — because "nothing to report" is itself information, and a handover that only happens on eventful days is not a handover.
Where it has to live
Not a message. Not a notebook that lives in someone's bag.
⚠️ Somewhere the next person will look without being told to — which in practice means wherever they already open at the start of their shift.
A handover in a chat thread is read once and scrolls away. The question "what was outstanding on Tuesday" needs to be answerable on Friday.
The overlap that would fix it
Fifteen minutes of paid overlap is cheaper than one missed guest commitment.
⚠️ Most venues will not do this, and the written version is the fallback — but it is worth calculating once. One escalated complaint from a broken promise costs more than a month of overlap.
Reading it back
The half nobody does.
The incoming manager confirms they read it. ⚠️ Not as bureaucracy — because an unread handover is worse than none, since the outgoing manager believes the information transferred.
And the outgoing manager checks the previous one was actioned. Otherwise items accumulate as "outstanding" forever and the list stops being read.
Walking loses numbers and names
Survives the shape of the story
Lost amounts, table numbers, people's names
⚠️ And the loss is discovered at the moment the detail is needed, which is always later and always worse.
It is a corridor conversation because there is no other place
No agreed place to stop people talk while moving
An agreed place they stop
⚠️ This is not carelessness; it is the absence of a location. ⇒ Fix the place, not the attitude. In front of a screen, at the office desk — anywhere, as long as it is decided.
Four lines, and do not add a fifth
Wanting to add a fifth means it belongs in writing, not in speech
⚠️ What is spoken stays at four. Everything else goes where it can be read.
The person receiving writes it down
The person leaving writes it they are going home
The person arriving writes it and finds out immediately whether they got it
⚠️ Ninety seconds of speech survives about ninety seconds. ⇒ Having the receiver write it converts the handover into something checkable, at no extra cost in time.
Overlapping shifts, but not every day
Fifteen minutes of overlap removes the corridor entirely
It also costs two people's fifteen minutes
⚠️ Overlap only on the changeovers that are actually difficult. ⇒ Applying it every day is what makes it get cut, and once cut it does not come back.
Read it back
"Tell me the four things you just took" thirty seconds
⚠️ This is the only way to know the handover happened. ⇒ The gap surfaces there, rather than at eleven o'clock, or the following morning when nobody can reconstruct it.
Three to hold
Handovers written, as a share of shifts. ⚠️ If it is only the eventful days, the quiet-day observations are being lost — and those are where the early warnings live.
Guest commitments that were not honoured. Frequently traceable to exactly this gap.
Items outstanding for more than a week. A growing list means the handover is being written and not read.
Where the record has to sit
A handover belongs against the shift, where the next person opens their day. If it lives in a message thread or a personal notebook, it is available to whoever was in the conversation and to nobody else, ever again.
tasteck keeps notes and tasks on the shift records staff already open, so what happened on Tuesday is still there on Friday.
Nothing was withheld. Eight hours of knowing what was going on was compressed into ninety seconds in a corridor, and most of it did not fit.
Read next
Related articles
Who Should Be Able To See Your Client List?
Client phone numbers and notes leave with whoever could see them. Here is how to decide who sees what — manager, desk staff, part-timers, entertainers and drivers — why bulk export and delete should be manager-only, and what to do on someone's last day.
Choosing Client Management Software For Your Venue — Five Checks Before You Compare
Comparing client management systems by counting features rarely settles anything. Map your own day first, then check five things against it: the phone, do-not-book lists, multiple venues, dispatch or rooms, and how easily your existing records move in — and out.
"Same Girl As Last Time" — Answering In Three Seconds
When a regular rings and asks for whoever he saw last, a desk that has to flip through booking sheets loses him. Here is what to look up — last entertainer, last date, usual request — how to check she's working today, and what to offer when she isn't.
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