A guest list has a VIP star. Does the pre-shift note actually say so?

Say a host adds a name to the event guest list two days before a private dinner and marks it VIP. Say, separately, the floor gets its pre-shift note an hour before doors. It is worth asking plainly whether those two things are connected, because on a busy night, assuming they are is how a server ends up waiting a VIP table with no idea who is sitting in it.

They are not the same record. They are built from different sources, at different times, for different purposes. Knowing exactly what each one contains is the only way to know whether the fact you care about is actually in front of the person carrying plates.

What is a VIP star on the guest list, exactly?

It is a flag on a named attendee, stored on the event itself. Excellent's event guest list holds named attendees on an event — each one optionally linked to a Party, optionally seated at a table on the floorplan, and marked with a meal choice and, if it applies, a VIP star. That is a row in the guest list. It says who is coming, where they might sit, what they are eating, and that someone marked them as a VIP.

It is a record, not a briefing. Nothing about storing the flag says anything about who reads it before service.

Does the pre-shift note pick up that VIP star automatically?

No — the note is drafted from a different set of inputs. The pre-shift note draws on the venue's live menu, the day's 86 list, whatever the operator adds by hand, and the finalized BEOs for that service day. Of a BEO's audience views, the note reads the floor-facing one, and folds in that view's guest count, run of show, and allergens. The event guest list — named attendees, meals, VIP stars, seats — is a separate structure the note's draft does not pull from.

This is the same shape of gap the allergen side of this problem runs into: a detail attached to a named guest and a detail summarized in the finalized document are stored in different places, drawn into the note through different paths. A shellfish allergy added two days out works through that exact seam for allergens; the VIP star sits in the same structural gap, for a different kind of flag.

This lines up with a broader pattern in how restaurants brief staff before a shift: pre-shift meetings commonly surface VIPs and special requests, but doing so depends on someone actively pulling that information out of the reservation or guest-list system and into the briefing — it is a named step, not something that happens on its own.

Where does the VIP star actually converge with the table and the meal?

On the seating chart, at the plate tally — that is the one place all three facts sit in the same document. The event guest list carries the VIP star and the meal, and once a guest is seated at a floorplan element, the table too. Excellent derives a per-meal plate tally on the shared seating chart that also feeds the BEO and the kitchen's prep sheet, with VIP-starred names shown against their tables. That chart is where a name, a seat, and a meal actually line up.

This matches how banquet teams commonly close the same gap: giving the floor a seating chart annotated with each named guest's table, seat, and meal is a standard way to bring identity, need, and location together in one document. The plate tally works the same way.

Why does a flag without context tend to get lost anyway?

Because naming someone as a VIP without saying what that actually means rarely sticks. A recurring observation about pre-shift briefings is that mentioning a VIP without explaining why they matter or what they prefer means the detail goes in one ear and out the other. "VIP at table six" is a label; it is not something a server can act on. The detail that travels is specific: what the guest ordered before, what they asked for, why tonight matters to them.

Does adding a VIP mid-week require anyone to re-sign the BEO?

No. Event seating is assigned against the event and the elements on its floorplan, and it is not locked to a finalized BEO. That is convenient for scheduling, but it also means a VIP star will never surface through a re-signed BEO. It stays a guest-list fact and a seating-chart fact; it does not migrate into the signed document on its own. Which channel carries each day of change covers the broader sorting logic for day-of details like this one.

What should an operator actually check?

A short list worth keeping by the host stand:

• Star the guest list the moment you know. That is the correct place to record it, and it is what the seating chart's plate tally reads from.
• Check the seating chart before service, not the guest list alone, to see VIP, meal, and table together.
• Look for the specific detail, not just the label, wherever the VIP is mentioned — a name attached to why they matter is more useful than a star by itself.
• Treat the pre-shift note and the guest list as separate documents that answer separate questions, not two views of the same fact.

Groups training staff to work from the pre-shift note night after night may want to see how the pre-shift note drafts — what it pulls in from the finalized BEO and the 86 list, and what it leaves out rather than guess at.

In short

A VIP star on the event guest list is a fact recorded on a named attendee. The pre-shift note is drafted from the finalized BEO, the 86 list, and whatever an operator adds by hand — a separate set of sources that does not include guest-list VIP flags. The one place VIP, meal, and table converge in a single document is the seating chart's plate tally.