A private event crosses two shifts. What do you hand the incoming team?

A lunch-into-dinner private event, or a double-seating in the same room, almost always crosses a shift change. The team that opened the room is not the team that closes it. Somewhere in the middle, an hour of overlap or a rushed line-up has to carry everything the first team learned about this one event to the team walking in cold.

Most restaurants have a shift-change habit already: a verbal rundown, maybe a written pre-shift note. For a normal night that is usually enough. For a private event that has been running for hours, it is not, because the pre-shift note was written before doors and the room has moved since then. The outgoing team knows things the note never captured.

This is a short, concrete list for that handoff — what to say, what to show, and what to point at instead of describing from memory.

What does the outgoing team owe beyond the pre-shift note?

The current state of the room, not the state it was in at doors. A pre-shift note is drafted against the venue's live menu, the day's 86 list, and the finalized BEOs for that service day — it is a summary written before service starts, not a log of what happened during it. Over a long private event, seats get reassigned, courses run behind, a guest leaves early, someone raises an allergy that nobody knew about at doors. None of that is in the note. It has to come from the people who were in the room.

Shift handover guidance in the industry is plain about this: a handover should document ongoing issues and special requirements in writing, not rely on memory. For a private event specifically, that means the outgoing captain owes the incoming team three things, said directly rather than relayed through a third person: where the party actually sits right now, what has already come up about any VIP or allergen tonight, and anything agreed with the host that has not yet made it onto paper.

Who needs the floorplan, and who just needs to be told?

Anyone touching the room for the rest of the event needs the floorplan itself, not a verbal description of where things ended up. Event seating is assigned against the event and the elements on its floorplan, and changing the room after a BEO is final does not require re-finalizing the document. That is useful: nobody has to wait on paperwork to move a table. But it also means the floorplan the outgoing team is looking at, and only that floorplan, reflects where the party actually sits at the moment of handoff. A runner or back server coming on for the second half should look at the current seating, not hear it described secondhand.

VIP flags and allergen notes already surfaced are a different kind of fact, and they travel differently. A VIP star on the guest list is one record; what made it into tonight's pre-shift note is another, and the two are not guaranteed to say the same thing — that gap is worth reading about on its own in a guest list has a VIP star. What matters here: if a guest's allergy or a host's special request came up for the first time during the first shift, it did not retroactively appear in a note that was drafted before service began. The outgoing team has to say it out loud, and ideally get it written somewhere the incoming team will check before the first course goes out for shift two.

What still has to come from the finalized BEO itself?

Anything the pre-shift note deliberately left out, because the note is a summary, not the document. The note draws on the BEO's front-of-house view, already stripped of detail the floor is assumed not to need for an ordinary shift — and a long or complex private event is not an ordinary shift. If the second-shift captain has a question about timing, course order, room setup, or anything the note's summary glosses over, the answer is to pull the finalized document, not to ask the outgoing captain to reconstruct it from memory. Isn't the pre-shift note enough? covers the general version of this rule; a shift change is one of the clearest cases where it applies, because the person who read the BEO at the start of the night is about to leave the building.

What if something changed and never made it onto anything official?

Then it is genuinely at risk, and the handoff is the last chance to catch it before it becomes a guess. Industry guidance on BEOs puts this sharply: if a change is agreed in an email thread or a conversation but never lands on the document itself, it did not happen as far as the kitchen is concerned. The same is true for a verbal agreement with a host during a shift — if it never reaches the note or the floorplan, the next team has no way to know about it except being told, right now, out loud. This is the single most common shift-change failure for a private event: a real agreement that exists only in one outgoing server's memory.

This is also where verbal-only notice earns its reputation for being unreliable. In food-allergy incident data, more than half of reactions in US restaurants happened even after the guest told staff about the allergy verbally, and the reaction rate was markedly lower when the allergen was also written down somewhere rather than only spoken. A shift change is exactly the kind of gap where a verbal-only allergen note can quietly disappear between one team and the next.

A short handoff checklist that holds up

A plain list to run through at the overlap, in order:

• Pull up the current floorplan. Walk the incoming lead through where the party sits right now, not where the BEO originally seated them.
• Say the VIP and allergen notes out loud, specifically. Name the guest, name the detail. Don't assume the pre-shift note already covers it — if it surfaced after doors, it doesn't.
• Point at the finalized BEO for anything beyond the summary. If a question is about timing, course sequence, or setup detail, open the document itself rather than answer from memory.
• Flag anything agreed with the host that isn't written anywhere yet. Get it onto the floorplan note or the pre-shift note before you leave, not after.
• Do the overlap in person if you can. A short window where outgoing and incoming staff are both in the room, handing off specific tables, catches far more than a note passed at the door.

The short version

The pre-shift note tells the incoming team what was planned before doors. It does not tell them what happened during the first half of a long private event. The floorplan, checked live, carries the current seating. The finalized BEO carries anything beyond the note's summary. And anything agreed with the host that only lives in one person's memory needs to be said out loud, specifically, before that person leaves. See how pre-shift notes draft to see what the note already pulls in automatically, and what it is built to leave out rather than invent.