Training a fine-dining floor team across locations

One restaurant can run on presence. The chef tastes everything, the GM watches the floor, and the standard lives in the people who set it. Then the second location opens, and the standard has to travel without them.

This is the quiet problem of every growing restaurant group: service quality that was never written down cannot be trained, measured, or kept. Here is how groups that stay excellent at five locations actually do it.

Why does training break when a restaurant group grows?

Because most fine-dining training is apprenticeship. New servers shadow good servers, absorb the standard, and pass it on. Apprenticeship is powerful and it does not scale: each location drifts toward its strongest personality, not toward the group's standard. Within a year, "how we do it" means something different in each building — and the guest who loves one location is quietly disappointed by another.

The fix is not more corporate oversight. It is writing the standard down once, teaching it the same way everywhere, and knowing — not hoping — who has learned it.

What should a restaurant group write down first?

Start with the four documents that decide most of a guest's night:

1. Steps of service. Greeting time, water and bread timing, order of service, wine presentation, crumbing, check presentation — as your group does them, with the reasons why. The reasons are what make people follow the steps when no one is watching.
2. Menu knowledge. Every dish: what is in it, how it is made, what to say about it, and what wine goes with it. Reissue it every menu change — stale menu training is worse than none.
3. Allergen handling. Who is told, what is said to the kitchen, how a modified dish is marked and delivered. This one is regulatory as well as reputational; treat it as certification, not reading.
4. Opening and closing standards. The side work that makes the first seating calm. Checklists, not essays.

Resist writing the fifty-page handbook. Four short, current documents beat one long, stale one.

How do you train staff who work in Spanish?

In Spanish. A large share of the American restaurant workforce is more comfortable in Spanish than in English, and a standard someone half understood is a standard that does not exist. Two rules:

• Translate the training properly — write it, do not machine-translate it. Service vocabulary is precise; "86", "on the fly", and "behind" do not survive automatic translation. Write short sentences in plain language and the translation stays faithful.
• Test in the language people learned in. A quiz in English measures English, not service knowledge.

This is a place software genuinely helps: Excellent Craft keeps every lesson in English and Spanish side by side, so each person learns in the language they think in and the standard stays one standard.

How do you know who is actually trained?

"We covered it in onboarding" is not knowing. Knowing looks like this:

• Assignments with due dates. Each role has a defined path — what a new server at any location must complete, and by when.
• A short assessment at the end of each course. Not to punish — to confirm the material landed before the guest tests it live.
• Completions pinned to a version. When the steps of service change, the question is not "did we send the email?" but "who is current on version four, and who needs to recertify?" If your system cannot answer that, you have records, not knowledge.
• One view across locations. The director of operations should see, in one place, that the new opening's team is 80% through certification — without calling anyone.

Where do pre-shift briefings fit?

Pre-shift is for what is different tonight: the VIP at table 12, the soft-launch dish, the private party in the back room and its BEO. Training is for what is true every night. Groups get into trouble when they use pre-shift to deliver training — fifteen minutes cannot carry a curriculum, and half the staff is not there that night.

Keep them connected but distinct: durable standards live in courses staff complete on their own time; tonight's notes live in the briefing.

What does this look like across five locations?

• The group's standards are written once, in both languages, and versioned.
• Every hire, at any location, gets the same path for their role — plus the location's own module for its menu and rooms.
• Managers see one dashboard of who is current, who is in progress, and who is overdue — by location and by course.
• When a standard changes, everyone affected is reassigned automatically, and the group can honestly say every floor was retrained.
• Pre-shift stays short, local, and about tonight.

None of this replaces taste, hiring, or leadership. It replaces the hope that excellence travels on its own.

Excellent Craft was built for exactly this: bilingual lessons drafted from your real menus and SOPs, assignments by role and location, and completions pinned to the version people actually trained on.