Key takeaways
- Counting covers, not tables, is the fairest basic rotation.
- Size sections to the server and the night, and set a maximum of tables seated at once per server.
- Watch three signals of a slammed section and skip that server until they recover.
- Make the rotation visible, so fairness can be checked instead of argued about.
Why rotation matters to servers and guests
Seating decides how much a server earns and how well a guest is looked after. Waitstaff at full-service restaurants earn a median of $27.00 an hour including tips, with a lower quartile of $19.00 and an upper quartile of $41.50[1]. Part of that gap comes from skill and shifts, and part from which tables a server is given. A host who seats unevenly creates resentment on the floor and slow service at the overloaded tables.
Source: National Restaurant Association, 2022[1]
Show the data
| Item | Value |
|---|---|
| Lower quartile | $19 |
| Median | $27 |
| Upper quartile | $41.5 |
The scale is large: about 2,270,910 people worked as waiters and waitresses in the US in May 2025[2], and about 423,100 openings for the job are projected each year on average over 2025 to 2035, mostly to replace workers who leave[3]. New servers arrive constantly, so the rotation has to be a system anyone can follow, not a host's instinct.
Four rotation methods compared
| Method | How it works | Strength | Weakness |
|---|---|---|---|
| Straight table rotation | Each new table goes to the next server in order | Simple, easy to learn | Ignores party size: a two-top counts the same as an eight-top |
| Cover-based rotation | The next table goes to the server with the fewest covers seated so far | Fairer on earnings and workload | Needs a running count |
| Points by table size | Tables carry points, such as 1 for a two-top and 3 for a six-top; seat the server with fewest points | Balances workload and simple to tally | Points need setting per room |
| Team service | Two or three servers share a larger section and its tips | Absorbs big tables and rushes | Needs trust and a clear tip-sharing rule |
Most full-service rooms do well with cover-based rotation or points by table size. Straight rotation is fine on quiet nights when tables are similar. Team service suits rooms with big tables, but its tip-sharing rule must follow the law: federal law bars employers, including managers and supervisors, from keeping any portion of employees' tips[4].
Setting sections before service
Start from the book
Look at covers by slot and where large parties and requests are seated. Sections should split the expected covers roughly evenly, not just the tables.
Size to the server
Give a newer server a smaller or simpler section, such as fewer tables close to the kitchen. Give experienced servers the large tables.
Set a cap
Decide the maximum tables a server can have seated within, say, ten minutes. Three is common; two for a new server.
Plan the cuts
Decide who leaves first and how their tables will be absorbed, so the rotation does not collapse at 9:00 pm.
Brief it
Tell servers their section, the cap and the cut order in pre-shift.
Employees in food services and drinking places averaged 25.1 hours a week in September 2026[5], which means many servers work short shifts that start and end at different times. Plan sections for the staffing you will have at each hour, not only at the start of service.
A worked rotation using covers
Example: four servers, A, B, C and D, start at 6:00 pm. The host seats by fewest covers so far, skipping anyone at the three-table cap.
- 6:00 pm: a two-top goes to A. Covers: A 2, B 0, C 0, D 0.
- 6:05 pm: a four-top goes to B. Covers: A 2, B 4, C 0, D 0.
- 6:08 pm: a six-top goes to C. Covers: A 2, B 4, C 6, D 0.
- 6:10 pm: a two-top goes to D. Covers: A 2, B 4, C 6, D 2.
- 6:15 pm: a four-top: A and D are tied on 2; A was seated first, so D takes it. Covers: A 2, B 4, C 6, D 6.
- 6:20 pm: a two-top goes to A. Covers: A 4, B 4, C 6, D 6.
Under straight table rotation, C would have been seated again at 6:20 pm after one round, despite carrying a six-top. Counting covers keeps workload and tips closer to even without anyone having to argue the point.
When a section is slammed
Even a fair rotation overloads a server sometimes: a six-top that wants separate checks, a table with a complicated allergy, a server who is simply having a slow night. The host needs to spot it and adjust.
- Signal one: tables in the section waiting for a first greeting more than a few minutes after seating.
- Signal two: several tables in the section at the same stage, such as all ordering at once.
- Signal three: the server tells the host, or the floor manager sees it.
When any signal shows, skip that server in the rotation until they recover, and note the skip so it is made up later. Do not move tables already seated unless the manager decides to; moving a table mid-meal is more disruptive than a short skip. If a server is regularly slammed, the section may be too big for them or the kitchen may be sending food in waves; fix the cause.
Double-seating rule: never seat two tables in the same section within the same few minutes unless the server agrees. If it has to happen at peak, tell the server before you walk the second table over.
Making rotation visible
Fairness arguments happen when servers cannot see the rotation. Put it on the reservation screen if your system supports it, or on a sheet at the stand. Show each server's covers and tables, who is next, and any skips with a reason. At the end of the shift, the host lead checks covers per server. If one server is consistently below the others, find out why: sections, cuts, or requests for other servers by regulars.
- Requests for a server: honor them, but count the covers in that server's total.
- VIP tables: assign by manager decision and count the covers.
- Large parties seated by plan: count them in the rotation for that server, so they do not get a walk-in four-top immediately after.
- Late cuts: once a server is cut, remove them from the rotation and restart fairly.
Scripts for seating conversations
Hosts are often younger and newer than the servers they seat, which makes pushback hard to handle. Give them words that point to the system rather than to themselves.
- Server asks why a colleague got the big table: "The rotation is by covers. You are on 10 and she was on 4, so it went to her. You are next for the following four-top."
- Server asks to skip a table: "I can skip you once and note it, and you will be first back in after. Do you want me to?"
- Server is next but the table does not fit their section: "This six-top only fits in Jess's section, so it goes to her and you stay next for anything that fits yours."
- Host needs to double-seat: "I need to seat a two-top in your section right after this four-top. Is that OK, or would you rather I hold it two minutes?"
When a disagreement goes beyond the rotation, the host passes it to the floor manager. The host's job is to apply the system, not defend it alone.
Example: setting points for a room
Example: a 110-seat restaurant switches from straight rotation to points. The general manager gives a two-top 1 point, a four-top 2 points, a six-top 3 points and any larger table 4 points, and caps each server at 3 points seated in a ten-minute window. Hosts tally points on the reservation screen. After a month, the gap in covers between the busiest and quietest server on a typical Friday narrows, and complaints about seating at pre-shift nearly stop. The general manager reviews the points once a quarter and adjusts if large tables start taking longer than the points suggest.
How the host stand supports the rotation
Rotation depends on the host being at the stand to see it. If phone calls keep pulling hosts away, seating becomes "whoever is closest", and fairness disappears. Assign the phone to someone else at peak, or let Ava answer the restaurant line, handle common questions and take reservation requests, so the host can keep the rotation running. For the rest of the host's night, see host stand setup and shift workflow.
Rotation also changes on peak nights with set seating times, when many tables arrive at once; reservation policies for holidays and peak nights covers pacing. If you use table time limits, the rotation should account for when tables are expected to turn; time-limited reservations explains how to set and communicate them.
Frequently asked questions
What is the fairest way to rotate tables between servers?
Seat the server with the fewest covers seated so far, skipping anyone at their cap of tables seated in the last few minutes. It is fairer than straight table rotation because it accounts for party size.
How many tables should a server have at once?
It depends on the room and the server. Many restaurants cap new seatings at three tables within about ten minutes, and two for newer servers.
What should a host do when a server is slammed?
Skip that server in the rotation until they recover, note the skip, and tell the floor manager. Avoid moving tables already seated.
Can managers share in a team service tip pool?
Federal law bars employers, including managers and supervisors, from keeping any portion of employees' tips[4]. Check state rules too before setting a tip-sharing policy.
References
National Restaurant Association (2022). National Statistics: Restaurant Industry Facts at a Glance (opens in a new tab) ↑
US Bureau of Labor Statistics (2025). Occupational Employment and Wage Statistics, May 2025 national estimate: Waiters and waitresses employment (series OEUN000000000000035303101) (opens in a new tab) ↑
US Bureau of Labor Statistics (2025). Occupational Outlook Handbook: Waiters and Waitresses (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), US Code (2026). 29 U.S. Code § 203 - Definitions (Fair Labor Standards Act) (opens in a new tab) ↑
US Bureau of Labor Statistics (2026). Current Employment Statistics: series CES7072200002 (opens in a new tab) ↑