The First Fifteen Minutes Of A Shift

The late shift arrives at 21:00. The early shift is busy. Nobody hands anything over.

For the next hour the new arrivals are working out what is happening from what they can see — which means they are working out the wrong things, because the important information is not visible.

The four things a shift change has to carry

One — what is already in motion. A table waiting on something, a guest who has been promised a call back, a delivery that has not arrived. Anything with a promise attached to it.

Two — who is in the room that matters. A regular in the corner, a group that has already been spoken to, someone who should not be served more.

Three — what is different tonight. A section closed, a change in pricing, someone new working, a booking that needs the good table.

Four — where the pinch will be. One sentence about the next three hours.

⚠️ Every one of these is invisible to someone walking in, and every one of them causes a specific, expensive failure when it is missing.

What actually happens instead

The new person asks "anything I should know?" and gets "no, all fine" — because the person answering is holding four things in their head and cannot enumerate them on demand while carrying drinks.

"All fine" is not a report. It is the shape of the question being wrong.

The fix is the format, not the effort

Nobody needs to try harder. The handover needs to be four specific questions instead of one open one, because specific questions retrieve what open ones cannot.

"Anything promised to anyone?" "Anyone in I should know about?" "Anything different tonight?" "Where does it get heavy?"

Thirty seconds. ⚠️ The difference between this and "anything I should know?" is enormous and costs nothing.

Where to write it down

Only the first one needs writing: promises.

The other three are situational and survive being spoken. A promise — a call back, a table held, a drink comped later — does not survive a shift change in anyone's memory, and it is the one where failure is visible to the guest.

One line, one place, cleared when done. That is the whole system.

The pattern worth noticing

If the same thing keeps failing at shift change, it is not the handover — it is that the thing crosses shifts by design.

A promise made at 20:00 to be delivered at 23:00 will fail regularly no matter how good the handover is. The fix there is to change what gets promised, or to make the promise belong to the venue rather than to a person.

⚠️ Handover discipline cannot compensate for a process that requires a memory to cross a boundary.

The cost of getting it wrong

Rarely dramatic. It accumulates:

A guest asked twice for the same thing. A regular not recognised by the second shift. A promise nobody knew about, discovered when the guest asks. Each one small, all of them avoidable, and together they are most of the difference between a room that feels looked after and one that does not.

Three to hold

Share of shift changes with an actual handover. If nobody knows, it is not happening.

Open promises at the end of the night. Should be zero; frequently is not, and nobody is looking.

Repeat failures at the same boundary. Tells you the problem is the process, not the people.

Where the record has to sit

A promise written on a pad behind the bar does not reach the person who takes over, and a promise in someone's head leaves when they do.

tasteck keeps notes against the guest and the visit, so something promised at 20:00 is in front of whoever is looking at that guest at 23:00.

The late shift is not less attentive. They were handed a room and no idea what was already owed in it.