Blog

Field notes

How high-end groups sell private dining, run events, and train their teams — written plainly, by the people building Excellent.

EventsFeatured

Why a signed BEO won't budge but the floorplan will

Seating changes without a new signature. The banquet order doesn't. Here is the design boundary to check for when you evaluate event software.

Read the note

Events

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

A VIP star on the event guest list and a line in tonight's pre-shift note are two different records — here is what each one actually contains.

Read the note

Events

Who signs off on a change to a finalized BEO

A finalized BEO is never edited in place. Here is what forces a new signed version, and what does not.

Read the note

Events

You comp a course or upgrade a room mid-service. Which record has to change?

A comped course, a bumped table, an added bottle: which record owns it — the invoice, the BEO, or a word at line-up.

Read the note

Training

Isn't the pre-shift note enough? When to pull the BEO instead

A plain rule for telling a normal shift from a private event that needs the signed document in hand, not just the briefing.

Read the note

Training

What the AI actually puts in a pre-shift note, and when it refuses to guess

How the pre-shift note draft reads the finalized BEO and the 86 list, and what it leaves out rather than invent.

Read the note

Events

Two chairs get added to a table. Does the note's allergen tally still hold?

The pre-shift note's allergen summary comes from the finalized BEO. A seating add afterward changes the table, not the note.

Read the note

Training

The BEO cover page and the pre-shift note: a printable chart for new hires

A side-by-side reference a trainer can hand a new server on day one: audience, source, lifespan, and who can change each document.

Read the note

Training

After the BEO is final

One party across two rooms: where does the signed document stop?

A private event books a reception space and a dinner room. The client swaps which room holds the bar two days out — here is what that touches, and what it doesn't.

Read the note

Operations

Do you need one system for events and training, or is Tripleseat plus a separate LMS fine?

What actually breaks when the BEO lives in one tool and the pre-shift briefing lives in another, and what changes when they share one spine.

Read the note

Operations

After the BEO is final

Amendment, pre-shift note, or a word at line-up: which one carries this change?

The sorting logic itself. Three channels carry day-of changes, they do different jobs, and treating them as interchangeable is how a server plates for the wrong number.

Read the note

Training

A 72-hour checklist for training banquet servers before a big private event

What to assign 72, 24, and 2 hours before a large private event, using the BEO itself as the training material.

Read the note

Events

After the BEO is final

The private-event day-of playbook: what changes between doors-open and dessert

Doors to dessert, in order: the changes a private event throws at you during service, who owns each one, and the one nobody is watching for.

Read the note

Migration

Switching off Tripleseat: a migration checklist for restaurant groups

What to export, what to clean, and how to change event systems between peak seasons — without losing a booking.

Read the note

Events

After the BEO is final

A VIP cancels at four and the count drops to thirty-two. What does the note say?

The signed document stays exactly as signed. Here is the wording the pre-shift note picks up instead, and why the operator never reopens the page.

Read the note

Sales

The private-dining proposal that closes

Guests say yes to clarity. What belongs in a private-dining proposal, in what order, and what to leave out.

Read the note

Events

After the BEO is final

A table gets added two days out. Does anyone have to re-sign?

Seating sits outside the signed BEO, so nothing is re-signed. Knowing exactly where that boundary falls is what keeps the wrong chart off the host stand.

Read the note

Operations

What a great BEO actually contains

The banquet event order is the contract between sales and service. What belongs on it, section by section.

Read the note

Events

After the BEO is final

A shellfish allergy arrives two days out. Who has to hear it before service?

Named guests and their allergen tags live outside the finalized document. Storing the detail and getting it to the person plating are two different jobs.

Read the note

Training

Training a fine-dining floor team across locations

How restaurant groups keep service standards identical across locations — without flying trainers between cities.

Read the note

Events

After the BEO is final

The pre-shift note vs. the BEO: why servers need both

A pre-shift note summarizes tonight's finalized BEOs, but it deliberately leaves out detail the floor still needs for a private or complex event.

Read the note

Training

After the BEO is final

An hour before doors, the party grows and the room changes. What happens now?

Same-day headcount and seating are floor logistics, not a new document — but a fast, direct re-brief has to reach the team before line-up.

Read the note

Training

After the BEO is final

From a signed BEO to tonight's pre-shift note

How a finalized BEO's kitchen and floor view becomes the pre-shift briefing, and why a seating change afterward does not require re-finalizing anything.

Read the note

Feed

New notes, as they land

No inbox required — follow the feed and read each note the day it publishes.

Subscribe by RSS