Steps of service on one page: counter, table and the hybrid in between

This is part 1 of our 7-part series Guest experience at a café or restaurant.

"Steps of service" is the order of everything a guest goes through, from the door to the goodbye, with a name next to each step. Every team already has one. Usually it lives in the owner's head and in the habits of the two people who've been there longest, which is why it changes with every shift.

Writing it down doesn't make service stiff. It makes it predictable for the guest and teachable for a new hire. And it shows you the gaps: the step nobody owns, or the one that two people both think is somebody else's job.

This post is about the whole visit and who owns each part of it. For the three moments at a café counter (greeting, taking the order and the handoff), with the words to use, see our post on café service standards. Here we cover table service, the counter, and the hybrid where guests order at the counter and the food comes to them.

Pick your service model first

Most of the confusion starts here. A team that half does table service and half does counter service gives guests half of each: nobody greets them at the door, and nobody tells them to order at the counter.

If you're a hybrid, say so on the door and at the counter. A guest who sits down and waits for a menu that's never coming has a bad visit before anyone did anything wrong.

The steps, with an owner and a timing

A good step has three parts: what happens, who owns it, and when. The timing is a promise you choose, not an industry number. Pick what your kitchen and your room can actually do, write it down, and change it when you learn more.

Table service

Counter and hybrid

Two rows deserve extra care in both models. Allergies are asked about and handled the same way every time: our allergy order procedure has the steps and our allergen matrix has the reference. And if you serve anything raw or undercooked, the consumer advisory belongs on the menu, not on a server's memory: see our consumer advisory template.

The handoffs are where service breaks

Look at your table again and circle every place where one person hands a guest to another: host to server, server to kitchen, kitchen to runner, runner back to server. Guests rarely complain about a single step. They complain about the gap between two of them.

• Host to server. The host tells the server a table was seated, or the server checks the section after every seating. Pick one. "They'll notice" is how a table waits ten minutes for water.
• Server to kitchen. Anything unusual (an allergy, a swap, a split plate) is on the ticket, not said in passing at the pass.
• Kitchen to runner. Food goes out with the table number and seat, so the runner can put each plate in front of the right guest without asking "who had the salmon?"
• Runner to server. If a guest asks the runner for something, the runner owns it until it's done or until they've told the server face to face.
• Counter to table (hybrid). The number or name on the ticket matches what the guest was given. A tent number with no ticket number is a guess.

Write one line under each handoff in your page: who tells whom, and how.

When it's busy: what can bend and what can't

Every step of service bends on a full Saturday. Decide in advance which ones can, so the team isn't deciding under pressure.

• Can bend: the timing on the check-back, the pre-bussing on every pass, the dessert offer.
• Can't bend: the greeting (even "I'll be right with you"), the allergy question, reading back an unusual order, and the goodbye.

Put that list at the bottom of the page. It's the part people remember during a rush.

How to write the page

1. Walk the visit yourself. Come in through the front door at a quiet time and write down every moment a guest meets the team.
2. Fill in the owner for each step by role, not by name. "Server", not "Maria". Names change; roles stay.
3. Choose your timings with the team. The people working the floor know what's realistic. A promise they don't believe won't be kept.
4. Add the handoff lines and the busy-day list.
5. Cut it to one page. If it doesn't fit, it's too detailed. Move the detail (how to carry three plates, how to present a bottle) into station training.

Then test it: give the page to someone who has never worked a shift with you and ask them to explain a table's visit back to you. Where they hesitate, the page is unclear.

Train it and check it

The page is the start of training, not the end of it. Our one-week training plan has the structure, and our training sign-off sheet has a place for each step. A short daily reminder in the pre-shift huddle (coming Nov 3) keeps it alive: one step, the one that slipped yesterday.

To check it, watch the floor for ten minutes during a busy stretch with the page in your hand and mark which steps happened. Coach the gaps quietly, after the guest has left: our post on feedback on the floor covers how. Update the page when the menu, the layout or the team changes, and date it, so everyone knows it's current.

Where Mays fits

• The page, on every phone: write your steps of service as a Knowledge Base article. Staff can read it in the Mays app as well as on the web. See Knowledge base basics.
• A quiz built from it: in Learning, an admin creates a module, adds questions from real situations ("A runner is asked for more water. Who owns it?") as multiple choice or true/false, with an explanation the learner sees after answering, and sets a passing score. See Creating learning modules.
• Assigned to the right people: a published module can be assigned by location, role, department or person, and you can see who has passed. See Assigning training.
• The sign-off as a task: give a trainer a one-off task, "Sign off: steps of service, table section", for each new hire. See One-off tasks.

Mays doesn't seat guests, time tables or take orders: your POS and your floor do that. What it holds is the page, the quiz and the record of who has been trained on it.

Your steps-of-service checklist

• One service model, and guests told which one it is
• Every step written down with an owner (a role) and a timing you chose
• One line under every handoff: who tells whom, and how
• A short "can bend / can't bend" list for busy days
• One page, dated, tested on someone new
• Trained, signed off and checked for ten minutes a week

Put your steps of service where the team can find them

Write the page once, turn it into a short quiz, and see who has passed it before they work a section alone.

Start your free trial: 30 days, every module, no card needed. Next in this series: the first 30 seconds, from the greeting to quoting a wait time you can keep.