Service standards written as actions, not values

Most restaurants have service standards somewhere. Often they are a list of values on the wall of the staff room: warm, attentive, professional, genuine. Every word is right, and almost none of them tell a new server what to do when they approach their first table on a busy Friday night.

Values describe how service should feel. Actions describe what to do. A new server can be told to be attentive and still not know how often to check a table; they can be told to be warm and still not know what to say when guests sit down. Standards written as actions can be learned in a day, followed under pressure and checked by anyone.

This guide covers how to turn service values into actions, the moments of a meal that need a standard, how to keep the whole thing to one page, and how to train and check it. Every venue and figure in it is an example.

Values are useful as a statement of intent. They tell the team what the venue cares about. But under pressure, people do not consult values; they follow habits. And a habit has to be an action: something you do, at a certain moment, in a certain way.

"Be attentive" leaves the server to decide what attentive means. One checks every table every two minutes; another checks once per course. Both believe they are attentive. "Check back within two minutes of the food arriving" leaves no room for doubt.

Writing standards as actions does not remove the warmth from hospitality. It gives every server a floor to stand on, from which their own personality can add the rest.

A good service standard names a moment, an action and, where it helps, a time. "When guests sit down, greet them within a minute, even if you are busy." "Offer water within two minutes of seating." "When the food arrives, check back within two bites."

It is short enough to remember and specific enough to check. A manager watching a table can see whether it happened. A new server can learn it in seconds and do it on their first night.

It also explains itself where the reason is not obvious. "Check back within two bites, so a problem can be fixed before the guest has eaten half the dish."

Start by mapping the moments of a meal from the guest's point of view: arriving at the door, being seated, the greeting, water and drinks, the order, the food arriving, checking back, clearing, dessert, the bill and leaving. Each moment is a chance to get service right or wrong.

Write one or two standards for each moment, no more. The aim is not a manual covering every situation, but a short list of the actions that matter most at each step.

Keep the list in the order the meal happens. That makes it easy to learn, because it follows the server's own evening.

The first standard belongs at the door, before the guest has sat down. "Acknowledge every guest within thirty seconds of their arrival, even if you cannot seat them yet." A guest who is seen and welcomed will wait happily; one who is ignored starts the evening annoyed.

Add one for the walk to the table: "Walk guests to their table at their pace, and offer to take coats." Small actions, but they tell the guest the evening has begun well.

The host stand has its own moments: answering the phone, taking a booking, greeting guests at the door, managing the waiting list and seating each table. Each deserves a standard or two.

"Answer the phone within four rings, with the venue's name and your own." "Repeat every booking back to the caller: name, date, time, party size." "Tell walk-ins an honest wait, and check on them every ten minutes." Simple actions, but they shape the guest's first impression before they reach the table.

Many guests' first contact with a venue is a phone call or a message. Write standards for those too: how quickly messages are answered, how bookings by phone are confirmed and how questions about allergies or accessibility are handled.

A guest whose message is answered within an hour, politely and accurately, arrives already feeling looked after. One who waits two days for a reply may not arrive at all.

Greeting a table is the moment that sets the tone for the whole meal. Write it as actions: "Greet the table within a minute of seating. Look at the guests, smile, introduce yourself if that is our style, and ask if anyone has been here before."

Add the questions that belong in the greeting: "Ask if anyone has allergies or dietary needs before taking any order." Asking early, as part of the greeting, makes it routine rather than awkward.

Keep any device out of sight for the greeting. Our guide to tableside ordering: eyes up, not on a screen covers why.

Write a standard for how menus and specials are presented. "Present the menu open, with a brief word about how it works." "Describe the specials with their prices before the guest asks." "Tell guests about any dish that has run out before they choose."

Mentioning prices with the specials avoids one of the most common awkward moments in restaurants: a guest surprised by the cost of a special they did not ask about. A standard removes the guesswork for the server.

Water service is a small standard with a large effect. "Offer water within two minutes of seating: still, sparkling or tap. Refill glasses when they are below half, without being asked." A table that never has to ask for water feels looked after.

The standard is easy to check: a manager can glance at the room and see empty glasses. It is also easy to forget on a busy night, which is exactly why it needs writing down.

Write standards for the drinks and the food order. "Take the drinks order within three minutes of the greeting, and send it at once." "Mention the specials, with their prices, before taking the food order." "Read the order back before leaving the table, including every change and allergy."

Each is an action with a reason: drinks arrive while guests read the menu, specials are offered without surprising anyone with the price, and the read-back catches mistakes before they reach the kitchen.

Some standards are about timing rather than words. "Take the food order within ten minutes of the greeting, unless the table asks for more time." "Hold mains until the starters are nearly finished, then fire them." "Tell the table if a dish will take longer than usual."

Timing standards help the kitchen as well as the guest. Orders that arrive at a steady pace, with courses fired at the right moment, keep the kitchen working smoothly and the food arriving when it should.

When the food arrives, a few actions make the difference. "Serve each dish to the right guest without asking who ordered what." "Name each dish as you place it." "Check back within two bites."

Serving without asking depends on recording seats when the order is taken. Naming each dish reassures the guest it is what they ordered. Checking back within two bites gives the guest a chance to say something is wrong while it can still be fixed.

Clearing has its own standards. "Clear plates when everyone at the table has finished, not while someone is still eating." "Offer the dessert menu after clearing, not before." "Brush the table if needed before dessert."

Clearing too early rushes guests; clearing too late leaves them sitting with dirty plates. A clear standard removes the guesswork.

The end of the meal shapes how guests remember it. "Bring the bill within two minutes of being asked." "Check the bill is correct before presenting it." "Thank every table as they leave, and invite them back."

A slow bill is one of the most common complaints in restaurants, and one of the easiest to fix with a clear standard. Our guide to faster payment, measured in actual seconds covers the payment side.

Service recovery needs standards too, because problems are stressful and people forget what to do. "When a guest complains, stop, listen without interrupting and apologise for the experience." "Tell the manager about every complaint at once." "Offer a fix that fits the problem, and check back afterwards."

Standards for service recovery give servers confidence in the hardest moments. Our guide to service recovery: putting a bad night right covers the approach in detail.

Regulars deserve standards of their own. "Greet regulars by name where you know it." "Remember their usual drink, or note it on their record." "Thank them for coming back."

Small actions make regulars feel recognised, and recognition is one of the main reasons guests return. A standard makes sure every server does it, not only the ones who happen to remember.

Service standards also cover the end of a shift: how sections are handed over, how tables are reset for the next service and how the team leaves the floor. "Hand over every open table to a named colleague before leaving." "Reset each table to the standard layout before the end of the shift."

Clear handover standards prevent tables being forgotten and guests left without a server when shifts change.

The bar needs its own standards: how quickly a guest at the bar is acknowledged, how drinks are recommended, how tabs are opened and closed, and how drinks orders from the floor are made and sent. "Acknowledge every guest at the bar within thirty seconds, even if you are busy." "Make floor orders in the order they arrived."

A bar with clear standards keeps the floor's drinks flowing and the bar's own guests happy at the same time.

Some guests need more help: a guest using a wheelchair, a guest with a visual impairment, a parent with a pram, an older guest who finds stairs hard. Write standards that make them welcome: offer an accessible table, read the menu aloud if asked, clear a route through the room, and ask rather than assume what help is wanted.

Standards like these make the venue welcoming to everyone, and they are easy to forget without being written down.

Keep the standards to one page. A server can learn one page; nobody learns a binder. If the list grows beyond a page, cut the standards that matter least, or combine them.

Write each standard as a single line, in plain words, starting with a verb: greet, offer, take, read back, check, clear, bring, thank. Group them by the moment of the meal. Put the page where staff will see it: in the staff room, by the pass and in the training pack.

Some standards cover how the team works together, not just how it treats guests. "Tell the kitchen about every allergy in person as well as on the ticket." "Pass on guests' compliments to the kitchen the same night." "Help a colleague's table when you are free."

These standards build a team that supports itself. They are as important to the guest's evening as any greeting, because a team that works together serves better. Our guide to front of house and back of house, same side covers the handover between floor and kitchen.

Standards should reflect your venue, not a generic list. A casual café's greeting is different from a fine dining restaurant's; a busy bar's water service is different from a tasting menu's. Write the actions that fit your style, your guests and your pace.

Involve the team. Ask experienced servers what they do that makes guests happy, and turn their habits into standards. A standard the team helped write is one the team follows.

Use the one page as the backbone of staff training. Walk new staff through it on their first day, moment by moment, explaining why each standard matters. Then let them shadow an experienced server, watching each standard in action.

Practise the harder moments: a complaint, an allergy, a table that wants the bill in a hurry. Role-play is quick and effective. Our guide to staff training that fits around service covers how to fit training into the week.

Standards written as actions can be checked. A manager can watch a few tables each shift and note whether each moment was handled: greeting within a minute, water within two, check back within two bites, bill within two of being asked.

Give feedback the same day, kindly and specifically. Praise what went well; point out one thing to improve. Over time, the standards become habits, and the checking becomes lighter.

New staff learn standards fastest when they see them in action. Pair each new server with an experienced one for their first shifts, and ask the experienced server to point out each standard as it happens: the greeting, the water, the read-back, the check back.

Give new staff the one page on their first day and ask them to learn one section at a time. By the end of their first week, most will know the whole page. Our guide to onboarding staff so night one is not chaos covers the wider first week.

Review the page every few months. Are there standards nobody follows, because they do not fit the venue? Are there problems that keep happening that a new standard would prevent? Has the menu, the room or the service style changed?

Change the page when it needs changing, and tell the team why. A page that stays current stays useful.

An invented bistro has a list of values on the staff room wall: welcoming, attentive, knowledgeable, genuine. Reviews praise the food but mention slow water, long waits for the bill and servers who disappear after the food arrives.

The manager turns the values into one page of actions, grouped by the moments of a meal: greet within a minute, water within two, specials with prices, read back the order, check back within two bites, bill within two minutes of being asked, thank every table at the door. New staff learn the page on their first day; the manager checks a few tables each shift.

Within two months, reviews start to mention attentive service, and the complaints about water and the bill fade. A new server, asked about her first week, says the page told her exactly what to do.

servearound does not hold a standards manual, but it carries much of the information the standards depend on. A guest's allergies show as a flag on the reservation list, on the table they sit at and at the head of the kitchen ticket, so the allergy question at the greeting is backed by a record the kitchen sees. Dishes are rung in by seat if the server likes, which is what lets each plate reach the right guest without asking.

The menu guests open with the table's QR code lets them call a server at any time and ask for the bill once they have ordered, and settling the bill sends the guest a feedback email. Each venue's team chat in Messages can carry the written standards as a shared file, where every member of the team can find them. See Order Fulfillment.

Specific actions the team takes at each moment of a meal, written so a new server can follow them on their first night.

Values describe how service should feel; actions tell people what to do, and can be learned and checked.

A moment, an action and, where it helps, a time: greet the table within a minute of seating.

One page. A server can learn one page; nobody learns a binder.

Greet within a minute, look at the guests, and ask about allergies before taking any order.

They should. Service recovery is when people most need to know what to do.

Walk through the page on day one, let new staff shadow, and practise the hard moments with role-play.

Watch a few tables each shift, note whether each moment was handled, and give kind, specific feedback the same day.

Service standards written as values tell people how service should feel; written as actions, they tell people what to do. Map the moments of a meal, from the door to the goodbye, and write one or two actions for each: greet within a minute, water within two, read back the order, check back within two bites, bring the bill within two minutes of being asked.

Keep it to one page, add standards for complaints and for the handover to the kitchen, make it fit your venue, train it on the first day, check it during service and review it every few months.