Hand your newest server your service standards on day one. Could they tell you what a good greeting is at your restaurant, without looking it up? Could their trainer?
If the answer is “sort of,” the problem is rarely the person. Restaurant standards fail on the page long before they fail on the floor.
This blog gives you a plain definition, a six-part anatomy, two illustrative table-service examples, and a one-page template you can copy straight from the page. It is not gated.
01What a standard is?
A standard is an observable, teachable description of good for one moment on the floor.
Take the three parts one at a time. Observable: someone standing in the room could see or hear whether it happened. Teachable: a new hire can learn it in one sitting, and a trainer can coach it. One moment: the greeting, the table reset, opening the room. Not “excellent service.”
A policy paragraph tells people what the company values. A standard shows them what to do, what it looks like when it is done, and how they will be coached on it. When a standard fits on one page, whoever has ten minutes teaches the same thing. That matters when people keep leaving.
02Why written restaurant standards fail?
Written standards tend to fail in four ways. This is an observation, not a statistic.
“Provide warm, attentive service.” Warm how? A new hire cannot copy an adjective.
A standard buried in a binder is a standard nobody opens at 5:15 before a Friday shift.
“Understands the menu” cannot be seen. “Describes tonight’s specials without reading the card” can.
The page says what good is and stops. Each manager then corrects in their own way, and the standard drifts from one location to the next.
Notice what the four have in common. Each one leaves the reader to guess. A new hire guesses one way, a trainer guesses another, and a manager corrects against a third picture in their head. Nobody is careless. The page simply never gave them anything to agree on.
Fix all four and you have a standard. Skip one and you have a policy.
03The anatomy of a standard
Here is how to write restaurant standards for employees in six fields. Each field has one job and one test it has to pass.
| Field | What goes in it | The test |
|---|---|---|
| Name | The moment, in the words your floor already uses. | Would a server say this word out loud? |
| Why it matters to the guest | One sentence from the guest’s side of the table. | Is it about the guest, not the company? |
| What good looks like (observable) | Two to four things someone could see or hear. | Could a manager across the room say yes or no? |
| Common slips | The two or three ways it usually goes wrong. | Have you seen them on your own floor? |
| How a manager coaches it | What to say and what to show, in the moment. | Could a new shift lead do it without you? |
| How the team will know it was met | Who observes, when, and what happens with what they see. | Is it a route, not a feeling? |
The last field is the easiest to leave out. It is the knowing gap in miniature: how you would learn the standard was met on a given shift.
04Two worked examples
Both are illustrative examples, not benchmarks. Anything that needs a number is a placeholder for you to set. Here are two restaurant SOP examples, written as standards.
Example 1: The greeting (illustrative, not a benchmark)
| Name | The greeting |
| Why it matters to the guest | It tells them they have been seen and that someone is looking after the table. |
| What good looks like | 1. Someone acknowledges the table within [X seconds] of seating. 2. The server stops at the table, makes eye contact, and says hello and their own name. 3. Drinks are offered in the first sentence, not after a speech. |
| Common slips | A nod in passing and “be right with you.” A greeting delivered mid-stride with plates in hand. A recited script that sounds recited. |
| How a manager coaches it | Stand with the server at the pass before the next seating. Name one thing done well. Show the slip once, then the better version. Ask them to try it on the next table. |
| How the team will know it was met | The shift lead watches [N] seatings per section in the rush and notes yes or no against the three items. The GM reviews the notes with the team once a week. |
Example 2: Dining room ready to open (illustrative, not a benchmark)
| Name | Dining room ready to open |
| Why it matters to the guest | The first guest walks into a room that looks ready, not half set. |
| What good looks like | 1. Every table is set to the house layout, with nothing missing and nothing different from its neighbor. 2. Menus, specials sheet and host stand are in place, and the reservation list is open. 3. Lighting and music are at the opening setting, and restrooms are stocked and presentable. 4. The room is ready [X minutes] before doors. |
| Common slips | Closers set tables in different ways. The specials sheet still shows yesterday’s. Lighting or music left at the closing setting. A scramble as the first guests arrives. |
| How a manager coaches it | [X minutes] before doors, walk the room with the opener, table by table. Point to what is right. Fix one slip together and let the opener fix the rest. |
| How the team will know it was met | The opener and the shift lead walk the room at [time] and agree on a yes or no against the four items. The answer goes in the shift notes the GM reads. |
Look at what the examples do. They name things you can see. They leave the numbers to you. They give the manager a move to make in the moment. And they are short enough for a new hire to read before a shift. They are not scripts. Your best server will say it better than the page does, and that is fine, as long as the observable items are met.
05A one-page template you can copy
Copy this straight from the page. There is no form, no download and no email address to give. If your version runs past one page, you are writing a policy.
| Field | Write here |
|---|---|
| Standard name | [the moment, in your floor’s words] |
| Owner and date | [who keeps this page current] [date of this version] |
| Why it matters to the guest | [one sentence, from the guest’s side] |
| What good looks like (observable) | 1. [something someone could see or hear] 2. [something someone could see or hear] 3. [something someone could see or hear] |
| Common slips | [the two or three ways it usually goes wrong] |
| How a manager coaches it | Say: […] Show: […] Ask them to try: […] |
| How the team will know it was met | Who observes: […] When: […] What happens with what they see: […] |
06Roll out one standard in one location
Start small. One standard, one location, one stretch of shifts.
- Pick the moment and the location. Choose a moment guests notice and staff handle every shift, like the greeting. Choose a location where the GM wants to try it.
- Write it with your best server. Watch them do it. Write what you saw, in their words, on the template.
- Test the words. Hand the page to someone who has never seen it and ask them to say what good looks like out loud. If they cannot, rewrite it.
- Teach it at pre-shift. Read it, show it, and have each person try it once.
- Coach for [N] shifts. Use the coaching field as written, and hold every shift lead to the same words.
- Learn whether it was met. Run the last field, then ask how you would have known last Thursday.
- Revise once, then add the next standard. Change the words that tripped people up. Then pick the second moment.
Pick the one moment on your floor that guests notice most. Write its standard on one page using the template above, with your best server in the room. Hand it to one new hire and ask them to say, in their own words, what good looks like.
If you could write only one standard first, which moment on your floor would it cover? Tell us in the comments.
07Leave a comment
08FAQ
What is a restaurant standard?
A restaurant standard is an observable, teachable description of good for one moment on the floor, such as the greeting or opening the dining room. Someone standing in the room can see whether it happened, a new hire can learn it quickly, and a manager can coach it. It is not a paragraph about company values.
What is the difference between a standard and an SOP?
The terms are used loosely. In this post, a standard describes what good looks like for one moment, while an SOP often lays out a longer process in steps. What matters is that either one is observable, teachable and has a coaching step. Use whichever word your team already uses and write it to that test.
How do you write restaurant standards for employees?
Use six fields: a name, why it matters to the guest, what good looks like in observable terms, common slips, how a manager coaches it, and how the team will know it was met. Write it with your best server, keep it to one page, then ask someone new to say it back before you roll it out.
How long should a restaurant standard be?
One page at most, and often less. If it runs longer, it has probably turned into a policy or tried to cover several moments at once. Split it so each standard covers a single moment. A new hire should be able to read it before a shift and explain it back in their own words.
How do you know whether a standard is being met?
Decide in advance who observes it, when, and what happens with what they see. A shift lead watching a few seatings, or an opener and a lead walking the room together, gives you a yes or no against the written items. A route you can name beats a feeling, and it shortens the time before you find out.


