Team and Training

Server Training Manual: What to Put In and What to Cut

Most server training manuals I have seen run to forty pages: the founding story, the mission statement, a paragraph on every wine region, the full employee handbook. New servers sign the last page and go back to learning the job from whoever trains them that night. I think a useful manual is short. It holds the service standards that are not up for debate, the steps of a table from seated to departed, how allergies and celebrations move between people, and a shadow-shift plan a manager can check off.

I'm Richard Yu. I have more than 15 years of startup and go-to-market experience, much of it in customer success and solutions engineering, where I built onboarding programs for enterprise customers. Today I'm a co-founder and the Managing Partner for marketing and operations at the restaurant I co-founded in San Francisco, where I help train our front-of-house team, and I built Regular inside that restaurant, one service at a time. Here is what I put in a manual and what I cut.

Why Most Server Training Manuals Go Unread

A long manual fails for a simple reason: it tries to teach everything at once, so it teaches very little. A new server on their first shift needs to know where the water is, how to greet a table and what to do when a guest mentions a nut allergy. They do not need the history of the building.

In customer success I learned that new customers tend to adopt the few things they use in their first week and ignore the rest of the documentation. Training staff works the same way in my experience. What gets used early sticks. What sits in an appendix gets skipped.

So I cut hard. Here is what I move out of the server training manual:

Company history and values statements. Tell the story in person at orientation. Deep menu and wine detail. Put it in a separate menu guide that changes with the menu. HR policies. They belong in the employee handbook. Aspirational language. "Deliver memorable experiences" teaches nothing on a busy Friday.

What remains should be readable in one sitting before a first shift. If a section would not change what a server does tonight, it goes somewhere else.

The Non-Negotiable Standards That Belong on Page One

Page one is the short list of restaurant service standards that hold on every shift, no matter how busy it gets or who is managing. I keep it to a handful, written as behaviour, not attitude. A standard you cannot observe is a wish.

The kind of standards I put there look like this. Greet within a set time. Pick a number your team can hit, for example within a minute of seating, even if it is only "I'll be right with you." Repeat back every allergy and tell the kitchen before the order fires. Never auction food. The runner knows which seat ordered what. Clear only when the whole table is finished, unless a guest asks. Present the check when asked or when the table signals, not to free the seat. Tell a manager about any complaint before the guest leaves.

Each line should be something a manager can watch for and coach. If a new server reads only page one, they should still avoid the mistakes that cost you a guest.

The test I use: could two different managers look at the same table and agree whether the standard was met? If not, rewrite it until they could.

Walking Through a Table From Seated to Departed

The middle of the manual is the life of one table, written in order. I break it into stages: seated, greeted, drinks ordered, food ordered, first course down, mains down, cleared, dessert offered, check presented, paid, departed. For each stage I write two or three lines: what the server does, what they say, and what they check before moving on.

Writing it this way does two things. It gives a new server a sequence they can follow when they are nervous, and it gives a manager shared language. "Your table stalled between cleared and dessert" is coaching. "Pick up the pace" is not.

Pacing is where new servers struggle most, often by rushing the start and drifting at the end. I wrote more about that in pacing service without rushing guests, and the short version is to teach the stages, then show servers where their own tables slow down.

That last part is where software can help. Regular's Server Performance app splits each table turn into stages from seated to departed, so a manager can see which stage is running long for a given server and add a coaching note. What it should not do is replace the conversation. The data points to the stage; the manager still explains what to do differently.

Allergies, Regulars and Celebrations: The Handoffs That Matter

Most service failures I worry about happen in handoffs: the host knew, the server did not; the server knew, the kitchen did not. The manual should say exactly how information moves.

Allergies. The server asks, repeats it back, writes it on the ticket in the agreed format and tells the kitchen directly. If the reservation already notes an allergy, the server confirms it at the table rather than assuming. Check your local allergen rules and build the steps around them.

Regulars. New servers often do not know who has been in ten times. Before service, the manager or host should point out returning guests and anything worth knowing about them. Regular's Today's Guests app lists tonight's reservations with visit history, VIPs, allergies and seating notes, which makes that pre-shift briefing faster.

Celebrations. A birthday in the reservation notes should never be a surprise to the server. Decide who acknowledges it and when. I covered the details in birthdays and anniversaries guests remember.

Technology should put this information in front of staff before the door opens. It should not stand in for the server looking the guest in the eye and asking.

A Five-Shift Shadow Plan You Can Use Next Week

The last section of the manual is a server onboarding checklist the manager signs off shift by shift. Five shifts is enough for many experienced hires; adjust for someone new to the industry. Each shift has one goal and one sign-off.

  1. Shift one: watch. Shadow the host stand for the first hour, then follow a trainer. Sign-off: the new server can describe the stages of a table and find every station.
  2. Shift two: run and support. Run food, clear and refill water alongside the trainer. Sign-off: no auctioned plates, correct allergy handoffs observed.
  3. Shift three: one table. Take one table from greeting to check while the trainer handles the rest of the section. Sign-off: greeting within the standard, order entered correctly.
  4. Shift four: a small section. Run two or three tables with the trainer watching and stepping in only if asked. Sign-off: pacing stays on track through dessert and check.
  5. Shift five: full section. Work a normal section with a manager check-in mid-shift. Sign-off: page-one standards met, plus a short conversation about what felt hard.

Keep the checklist on paper or in a shared doc, initialled each night. If a sign-off is missed, repeat that shift rather than moving on.

Coaching After Training: Keeping Standards Alive

Training ends on shift five. Standards decay after that unless someone keeps them in view. Among front of house manager duties, I think this one is easiest to let slide and most expensive to lose.

What works for me is small and regular. At pre-shift, pick one standard from page one and talk about it for two minutes. During service, the manager watches for that standard specifically. After service, one short note per server: one thing done well, one thing to adjust. Notes that arrive the same night or the next morning seem to land better than a quarterly review.

Revisit the manual itself every few months. When the same mistake shows up across several servers, the manual is usually unclear, not the team. Rewrite the line and retrain at pre-shift.

If you want to see how Regular connects reservations, the point of sale and the staff schedule to support this kind of coaching, you can book a demo. Either way, start with one page of standards and the five-shift plan, and let the rest of the forty pages go. You can find me on Instagram if you want to compare manuals.

Frequently Asked Questions

What should a server training manual include?

A useful server training manual includes a short page of non-negotiable service standards, the steps of a table from seated to departed, clear procedures for allergies, regulars and celebrations, and a shift-by-shift shadow plan with manager sign-offs. Menu details, company history and HR policies are better kept in separate documents so the manual stays short enough to read before a first shift.

How long should restaurant server training take?

Many restaurants train experienced servers over about five shifts: one watching, one running food and supporting, one taking a single table, one handling a small section, and one working a full section with a manager check-in. Someone new to the industry often needs more. The point is to move on only when each shift's sign-off is met, not on a fixed calendar.

What are examples of restaurant service standards?

Good restaurant service standards describe observable behaviour. Examples include greeting a table within a set time, repeating back allergies and telling the kitchen directly, not auctioning food, clearing only when the whole table has finished, presenting the check when the table asks, and reporting any complaint to a manager before the guest leaves. Two managers should be able to agree whether each was met.

How do you keep servers following standards after training?

Keep standards visible with small, regular habits. Pick one standard to discuss at each pre-shift, have the manager watch for it during service, and give each server a short note afterward with one strength and one adjustment. When the same mistake appears across several servers, rewrite that part of the manual, because it is often unclear rather than ignored.

Regular

Run the Night Your Regulars Remember

One suite of apps that connects your reservations, POS and schedule, from before the meal to the next visit.