Three sources feed the pre-shift note. What happens when they disagree?

A line cook pulls the last rack of lamb forty minutes before doors. The chef 86s it on the spot. Nobody has touched tonight's BEO — it was finalized two days ago and still lists lamb in the entree section, because a finalized BEO does not change after signature. Now there are two facts about lamb in the building, and they do not agree.

This is not a rare glitch. It is what happens every time a kitchen reality moves faster than a signed document, and it is worth knowing exactly what the drafted note does with that gap before you are standing at line-up holding two different pieces of paper.

The same shape of problem shows up with allergies. A guest mentions a shellfish allergy on Tuesday. The BEO was finalized on Monday. The allergen summary on that snapshot does not know about Tuesday's news, because it is frozen at the moment the document was finalized.

What does the note actually say about the lamb?

It says both things, because the draft reads the 86 list and the finalized BEO as two separate sources and states what each one says. The pre-shift note draft pulls the venue's live 86 list on its own, apart from the finalized BEO's menu section — it does not read one through the other. The BEO's lamb line is a record of what was ordered and agreed to at finalization; the 86 list is today's floor reality. The note carries both rather than silently picking one.

This also matches how a floor already runs day to day. A pre-shift meeting normally reviews the current stop list as of that moment — what has run out, what is running low, what the substitution is — and the chef or sous chef is expected to pass every 86 to the floor directly, both at that briefing and live during service, not leave it sitting on a document from two days back.

What happens to an allergy the BEO never saw?

It does not appear in the note's allergen summary, because that summary is built from the finalized BEO's snapshot and nothing else. The note folds in the allergens present in that finalized document's floor-facing view, drawn from a closed vocabulary already baked into the frozen render — not a live lookup against whatever a host just typed into a guest profile. A shellfish allergy that arrived after finalization lives outside that document until a new BEO version is published and finalized. We have covered that specific gap — a new allergy landing after the BEO is final — in a separate post about who has to hear it before service; the short version is that storing the detail and getting it in front of the person plating are two different jobs, and the pre-shift note's allergen summary is not the second one.

This matters because the note reads like a complete allergen picture at a glance. It is complete for what the finalized BEO contains. It is not a live feed of every allergy anyone has mentioned since finalization.

Why does the engine drop a conflict instead of guessing at an answer?

Because a BEO that does not resolve to a real, current record is treated as missing information, not as a question to patch over with a guess. If a BEO referenced for that service day cannot be matched back to an actual event and its finalized snapshot, it is dropped from the draft entirely rather than filled in with an assumption. A service day with no finalized BEO at all simply produces the note it always would, without one. The same posture holds for the kind of conflict in this post: the draft states what the 86 list says and states what the finalized BEO's menu section says, because those are two facts it can source with confidence. It does not merge them into one invented verdict about whether the lamb is actually on the table tonight — that judgment stays with the people at line-up, who have both facts in front of them instead of one smoothed-over answer.

This same discipline — read what a live source says, read what a frozen one says, and state both rather than blend them into a guess — is the backbone of how the engine drafts a pre-shift note at all. A kitchen running a complex private event that night still has reason to pull the BEO itself rather than trust the note alone; the note is a briefing, not a replacement for the signed document.

In short

The 86 list is read live. The finalized BEO is read from its frozen snapshot, including its allergen summary. The note states what each one says rather than merging them. When a reference does not resolve at all — a BEO that cannot be matched to a real record, or a service day with no finalized BEO — the drafted note says so instead of inventing an answer.