Key takeaways
- There is no universal number; section size depends on service style, menu, support staff, layout and technology.
- Calculate it from your own data: covers per server hour on your smoothest busy nights and your average turn time.
- Runners, bussers and handhelds let a server carry more tables, but only if the time saved goes back to the guest.
- Watch the warning signs: missed greet times, late check drops and finished plates on tables mean the section is too big.
Why the answer depends on your restaurant
About 2.27 million people worked as waiters and waitresses in the US in May 2025[1], and almost all of them have worked a section that was too big. Owners ask how many tables one server should have because labor is expensive: food and labor each take roughly 33 cents of every sales dollar[2]. But the right section size is not a single number. A server in a steakhouse with tableside service, a sommelier and runners does very different work from a server in a casual café who also runs drinks, bus tables and takes payment.
The useful question is how many covers one server can look after well in an hour, given everything else in your service model. Answer that from your own data and the section size follows. Guess, and you will either waste labor on quiet sections or burn out servers on crowded ones.
Calculate section size from your own data
Pick your best busy shifts
Choose four to six recent busy shifts where service went smoothly: few complaints, good ticket times, servers not visibly drowning.
Count covers per server hour
For the peak hour of each shift, divide the covers seated by the number of servers on the floor. Average the results. This is your service standard.
Measure your turn time
Find the average time a table is occupied at peak, from seating to leaving, for two-tops and four-tops.
Convert to tables
Divide covers per server hour by your average party size, then multiply by the turn time in hours. That gives the number of tables a server can hold at once.
Test and adjust
Try the section size for two weeks, checking greet times, check drops and guest feedback, then adjust by one table up or down.
For example, if your smooth busy shifts show about 10 covers per server per hour, your average party is 2.5 guests and tables turn in about 1.5 hours, a server can hold roughly six tables at once (10 divided by 2.5, multiplied by 1.5). If the turn time is two hours, it rises to eight. That is why the same restaurant often needs different section sizes for lunch and dinner.
Example starting points by service style
The ranges below are illustrative starting points to compare against your own calculation, not industry standards. Use them to sanity-check your numbers, then trust your data.
| Service style | Example tables per server | What drives it |
|---|---|---|
| Fine dining with multiple courses | 3 to 4 | Long, detailed service, wine, tableside steps; usually with captains, runners and bussers |
| Upscale casual | 4 to 5 | Full sequence of service, wine and cocktails, moderate support |
| Casual full-service | 5 to 7 | Shorter menu, faster turns, runners at peak |
| Family dining and diners | 6 to 8 | Quick turns, simple menu, server often runs own food |
| Bar dining | Seats along the bar plus a few high-tops | Bartender also makes drinks; depends on bar layout and barback support |
| Banquets and private events | Set by guests per server for plated or buffet service | Fixed timing; staffing set at booking |
Adjust for support roles
A server's section can grow when other people take part of the work, and should shrink when they do not. List every task in your sequence of service and note who does it on a busy night.
- Food runners take plates from the pass, so servers spend less time walking and more time at tables.
- Bussers clear, reset and refill water, which shortens turn time and keeps tables looking cared for.
- A service bartender makes all drinks; without one, servers who make their own drinks need smaller sections.
- Hosts who seat in rotation and warn servers about large parties protect the greeting time.
- Managers who touch tables and handle complaints save servers several minutes per problem.
When a runner or busser calls out, shrink sections for that shift. Keeping the same section size without the support staff is the fastest way to lose a busy night.
Adjust for handhelds and pay at the table
Handheld ordering and payment devices remove trips to the terminal and shorten the wait for the check. Guests are comfortable with 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], and a majority of full-service customers are comfortable using a smartphone app to order (63%) or pay (55%)[4].
Handhelds can justify an extra table per server, but only after you measure the time saved. Run two weeks with the devices and the current section size, check greet, check-back and check-drop times, then add a table if the targets hold. If you add tables on day one, the minutes saved disappear into a bigger section and guests feel no difference.
Lunch, dinner and weekend differences
Section size should change with the shift, because the work changes. Lunch guests often want to be in and out quickly, so tables turn fast and the server spends more of each hour greeting, ordering and dropping checks. That usually means a smaller section than the turn time alone suggests, because the start and end of the meal are the busiest parts of the sequence. Dinner guests stay longer and order more courses and drinks, so each table needs more visits but they are spread across a longer stay.
Weekends add large parties, celebrations and a heavier bar. Treat a party of eight or more as two or three tables when planning sections, and avoid giving one server two large parties seated within half an hour of each other. Brunch is its own case: fast drink orders, lots of coffee refills and families with children make it feel busier than the cover count suggests. Calculate a separate standard for each shift type rather than applying the dinner number everywhere.
Design sections, not just sizes
- Keep each section contiguous so the server can see all their tables from one spot.
- Balance each section's distance from the kitchen, the service station and the bar.
- Mix table sizes, so no section is all large tops that seat at once.
- Balance desirable and less desirable tables across sections, such as the patio, booths and the table by the door.
- Draw a separate section plan for quiet and busy shifts, and for large-party nights.
Sections and fairness between servers
Because servers earn much of their income from tips, section assignments feel personal. A server repeatedly given the slow corner or the tables by the kitchen door will assume favoritism. Rotate the best and worst sections across servers who meet the performance standard, and explain the rotation openly. When a strong server gets a larger section on a busy night, say why, and make sure newer servers get busy shifts too, with a trainer nearby, so they can build the skills to carry more.
- Publish the section plan with the schedule where you can, so servers know what to expect.
- Record who had which section on busy nights and check the rotation monthly.
- Change section sizes for everyone at once, with a short explanation at pre-shift, rather than quietly for one person.
- Ask servers after a trial which sections felt unbalanced, and adjust the floor plan.
Warning signs a section is the wrong size
| Sign | Likely problem |
|---|---|
| Tables wait well past the greet target | Section too big, or seating not in rotation |
| Finished plates sit on tables | Section too big or no busser support |
| Guests flag down other servers for the check | Section too big at the end of the meal |
| Servers standing idle during peak | Section too small or seating uneven |
| One section always has the complaints | Section layout or table mix is unbalanced |
Walk the floor at peak with the steps of service in mind. Where steps are slipping, the section is usually the cause, not the server.
Example: resizing sections for a busier dinner
Example (fictional): a 110-seat casual restaurant runs six-table sections at dinner. Guests complain about slow check drops on Saturdays. The manager reviews five smooth busy shifts and finds about 9 covers per server hour, an average party of 2.8 and a Saturday turn time of 1.6 hours, which gives about five tables per server.
She moves Saturdays to five-table sections, adds one server and a runner from 7 to 9 p.m., and keeps six-table sections on weeknights, where turns are faster. After a month, check-drop complaints have stopped and servers' Saturday tips per shift are steady, because they turn their tables more reliably. The extra labor is partly offset by faster turns on the busiest nights.
Frequently asked questions
How many tables should a server have?
It depends on service style, support staff, menu and turn times. Calculate it from covers per server hour on your smooth busy nights, your average party size and your turn time.
How many servers do I need for 100 seats?
Work from covers, not seats: forecast peak covers per hour, divide by your covers-per-server-hour standard and add servers for staggered starts and closing.
Do handhelds mean servers can take more tables?
Often, but measure first. Run two weeks with the same sections, check service timing, then add a table only if the targets hold.
What happens when a runner or busser calls out?
Shrink sections for that shift. The section size you set assumed that support, so keep the same size only if someone else covers the work.
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 (2026). Restaurants remain resilient despite challenging business conditions (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) ↑