Key takeaways
- A written sequence of service makes every table's experience consistent, whoever the server is.
- Set a timing target for each step and train servers to notice when a table falls behind.
- The steps that slip first under pressure are the check-back and the pre-bus; build them into the routine.
- Handhelds change the order of some steps but not the goal: fewer trips to the terminal, more time at the table.
Why a sequence matters to guests and to servers
Waiters and waitresses are one of the largest occupations in the country, with about 2.27 million people employed in May 2025[1]. The National Restaurant Association's tipped employee research puts the median hourly earnings of full-service waitstaff at $27.00 including tips, ranging from $19.00 at the lower quartile to $41.50 at the upper quartile[2]. A large part of that gap comes down to execution: the servers who earn the most tend to run a tight, repeatable sequence that leaves guests feeling looked after without being hovered over.
Source: National Restaurant Association, 2022[2]
Show the data
| Item | Value |
|---|---|
| Lower quartile | $19 |
| Median | $27 |
| Upper quartile | $41.5 |
A written sequence of service does three jobs. It gives new servers a map, it gives managers something specific to coach against, and it makes the guest experience consistent across sections. It also protects the kitchen, because orders arrive in a predictable rhythm.
The ten steps and example timing targets
The targets below are a starting point for a casual full-service restaurant. Adjust them to your concept, check average and kitchen times, then write your own version into the server manual.
| Step | What the server does | Example target |
|---|---|---|
| 1. Greet | Introduce yourself, offer water, mention one drink or special | Within 1 minute of seating |
| 2. Drinks | Take the drink order, ring it, deliver | Drinks on the table within 4 minutes |
| 3. Order | Answer questions, check allergies, take the food order, read it back | Within 8 minutes of seating |
| 4. Appetizers | Deliver, explain shared plates, clear finished plates | Per kitchen time |
| 5. Entrées | Deliver to the right seat without auctioning, replace cutlery | Per kitchen time |
| 6. Check-back | Visit after the first bites: is everything as expected? | Within 2 minutes or two bites |
| 7. Pre-bus | Clear finished plates, refill drinks, crumb if needed | Ongoing |
| 8. Dessert and coffee | Offer dessert and coffee, show the menu | When entrées are cleared |
| 9. Check | Drop the check when asked or when the table signals | Within 2 minutes of the request |
| 10. Farewell | Process payment, thank guests by name if known, invite them back | Payment back within 3 minutes |
Scripts for the moments that matter
Scripts are not meant to be recited. They show the structure of a good interaction so a new server knows what to cover. Encourage each server to put them in their own words.
- Greeting: 'Hi, I am Sam and I will be looking after you tonight. Can I start you with some water? Our bartender has a pear spritz on tonight if you would like something to start.'
- Allergy check: 'Before I put your order in, does anyone at the table have an allergy or anything you do not eat?'
- Read-back: 'So that is one salmon, medium, with no butter on the vegetables, and one chicken. I will get those started.'
- Check-back: 'How is everything tasting? Is the salmon cooked how you like it?'
- Dessert: 'We make the chocolate tart here every morning. Would anyone like to see the dessert menu, or coffee?'
- Farewell: 'Thank you for coming in tonight. I hope we see you again soon.'
Train servers to read allergy notes back word for word and to tell the kitchen in writing on the ticket, never only verbally at the pass.
The first five minutes in detail
The opening of the meal sets the guest's view of everything that follows, so it deserves the most training time. Teach servers to approach the table as soon as it is sat, even if they are busy elsewhere. A brief 'I will be right with you, can I bring some water?' buys several minutes of goodwill. Then return with water, introduce themselves and read the table: a business lunch wants speed, a couple celebrating wants time, a family with small children wants bread and crayons quickly.
Drinks come next. Servers should suggest one or two specific drinks rather than asking an open question, ring the order straight away and tell the bar if a table is in a hurry. While drinks are made, they can mention the specials and any items the kitchen has run out of, so guests do not choose a dish that is no longer available. By the time drinks land, most tables are ready to order, and the server can take the food order in one visit instead of two.
Where the sequence breaks under pressure
On a busy night servers drop the steps that do not produce a ticket. The check-back disappears, finished plates sit on the table, and the check arrives late because the server is triple-sat. Managers can spot this quickly by walking the floor with the sequence in mind.
- Look for tables with finished plates: the pre-bus has slipped.
- Look for guests looking around: the check-back or check drop has slipped.
- Ask the host about seating: a server triple-sat cannot hold the greeting target.
- Check the kitchen screen: orders bunching suggests servers are holding tickets and firing in batches.
- Watch the bar ticket times: if drinks are slow, the drinks target is lost before the server is to blame.
When steps slip, fix the system before blaming the server. Smaller sections, a runner on peak nights or a busser assigned to pre-bus can recover the sequence faster than a lecture. Our guide to section sizing covers how many tables one server can carry.
Adapting the sequence for handhelds
Handheld ordering devices let servers send orders from the table, which cuts trips to the terminal and gets tickets to the kitchen sooner. Guests are increasingly used to technology at the table: 65% of adults say they would be comfortable paying their check at a full-service restaurant with a tablet at the table[3]. A majority of full-service customers are also comfortable using a smartphone app to place an order (63%) or to pay (55%)[4], so servers should expect some tables to want speed and others to want conversation.
Merge order and fire
With a handheld the order goes to the kitchen at the table, so the read-back becomes the last check before sending. Train servers to confirm modifiers on screen before tapping send.
Pace the courses
Because tickets arrive instantly, servers must hold entrées deliberately rather than relying on the walk to the terminal. Use course firing if your system supports it.
Pay at the table
Payment at the table removes the longest wait in the meal. Keep the farewell personal even when the device does the work.
Reinvest the time
Coach servers to spend the minutes saved on check-backs and pre-bus, not on taking a bigger section straight away.
Service recovery inside the sequence
Mistakes will happen: a steak cooked wrong, a missing side, a long wait for the check. Build recovery into the sequence so servers know exactly what to do. The check-back is where most problems surface, which is why it matters so much.
- Listen to the whole complaint without interrupting or explaining.
- Apologize simply and say what you will do: 'I am sorry, let me get that fixed for you right away.'
- Tell the manager on duty and the kitchen, with the seat number and the problem.
- Keep the rest of the table's experience moving so one guest's issue does not hold up the others.
- Follow up once the fix arrives, and let the manager decide on any comp.
Record recovery cases in the shift log. Patterns, such as one dish coming back repeatedly, belong in the next pre-shift and kitchen meeting rather than with the individual server.
Example: coaching one section
Example (fictional): at a 120-seat Italian restaurant, the general manager notices that Friday tables in one section wait well past the dessert step for the check. She shadows the server for an hour and finds he is carrying six tables and running his own drinks from the service bar. She splits the section to five tables on Fridays, assigns a runner to the service bar from 7 to 9 p.m., and reviews the check and farewell steps with him at the next pre-shift.
Two weeks later the section's check drops are on target and the server reports fewer guests flagging him down. The manager adds the change to the floor plan for all Friday sections and updates the server manual so the next new hire learns the same sequence.
Training and testing the sequence
Teach the sequence in a classroom session, then have trainees follow a strong server for a full shift with a copy of the steps in their apron. On their first solo shifts, a manager should time two tables against the targets and talk through the results privately. Repeat the timing check at thirty and ninety days, and include it in reviews so servers know the sequence is the standard, not a suggestion.
Frequently asked questions
What are the steps of service in a restaurant?
A common sequence is greet, drinks, order, appetizers, entrées, check-back, pre-bus, dessert and coffee, check, and farewell. Each restaurant sets its own timing targets.
How fast should a server greet a table?
Set a house target, such as about a minute after seating. Even if the server is busy, a quick hello and water shows the table has been seen.
What is a check-back?
A short visit after guests take their first bites of a course to confirm the food is as expected, so problems are fixed while the meal is still going.
Do handhelds change the steps of service?
They combine ordering and firing at the table and allow payment at the table. The sequence stays the same, but servers must pace courses deliberately.
References
US Bureau of Labor Statistics (2025). Occupational Employment and Wage Statistics, May 2025: Waiters and waitresses employment (opens in a new tab) ↑
National Restaurant Association (2022). National Statistics: Restaurant Industry Facts at a Glance (opens in a new tab) ↑
National Restaurant Association (2024). Serving Up Technology: New Data Shows How Tech Integration is Transforming the Restaurant Experience (opens in a new tab) ↑
National Restaurant Association (2024). Restaurant Technology Landscape Report 2024 (opens in a new tab) ↑