Sections are one of the few things in a restaurant that cost nothing to change and materially affect both revenue and how the night feels. They are also usually drawn once, years ago, by whoever was managing then, and never revisited.
Here is what a section is actually doing and how to draw better ones.
What a section has to balance
Four things, and they pull against each other.
Covers per server. Too many and service degrades. Too few and you are overstaffed for the revenue.
Walking distance. A section split across the room costs the server time on every trip, and time is covers.
Desirability. Window tables, the quiet corner, the table by the kitchen door. If one section is consistently worse, whoever has it earns less on tips for the same work, and they know.
Turn rate. Two-tops turn fast and generate more transactions per hour. A section of large tables has fewer, bigger, slower checks. Those are different jobs and different tip patterns.
A section plan that balances covers and nothing else will be quietly resented.
The number to start from
Covers per server, not tables per server.
Tables mislead. Four two-tops and two four-tops are both six tables and 8 versus 20 covers. Count seats.
Working ranges, and they vary a lot by format:
- Quick, casual service: 20 to 30 covers per server is common
- Full service, moderate pace: 14 to 20
- Fine dining with coursing: 8 to 12
Then adjust for how much the server actually does. If runners deliver food, bussers clear, and a sommelier handles wine, a server can take more covers. If they do all of it, they cannot.
Draw them by contiguity, not by fairness
A common mistake: splitting the good tables evenly by giving each server one window table on the other side of the room.
That feels fair and it is worse for everyone. The server walks further, food arrives slower, and the guest at the far table gets less attention.
Better: draw contiguous sections, accept that they are not equally desirable, and handle fairness by rotating who gets which one. Fairness over a month, efficiency every night.
Rotate the seating, and make the rotation visible
Whoever seats guests controls who earns what. That is a lot of power and it is the most common source of resentment on a floor.
So make the rotation explicit — next open table in turn, skipping a server who has just been double-sat. If the host is deviating from it, there should be a reason anyone can hear: a section that just took a twelve, a server closing out a large check, a guest specifically requesting someone.
The guest-request case needs a rule, because regulars asking for their server is good for the restaurant and unfair to the rotation if it is not accounted for.
Open and close sections with the volume
The most common staffing error is running the full floor from the first cover to the last.
Instead, open sections as covers arrive and close them as the night tails off. Two sections at five o'clock, five at seven, two again at ten. Servers cut early go home instead of standing in an empty section earning nothing.
This requires knowing your shape, which means looking at covers by hour rather than by night. Almost every restaurant's real peak is narrower than its staffing assumes, which is also the finding that drives most restaurant staff scheduling improvements.
Handle large parties deliberately
A party of ten dropped into a normal section takes that server out of circulation and slows down everyone in it.
Options that work: a dedicated large-party area, two servers sharing a large table, or taking the section's other tables out of the rotation while the party is in. What does not work is pretending it is one table.
Whichever you choose, decide it in advance. Working it out at the moment the party arrives is how a Saturday goes wrong.
Where the POS earns its keep here
Two reports settle most section arguments.
Sales by server, next to covers by server. This separates a server who was given a weak section from one who is not selling. Without covers alongside, the sales report just rewards whoever got the big tables.
Turn times by table. Which tables actually turn and which are held. A table that consistently sits forty minutes longer than its neighbours is either badly placed or being used as the party table, and either way it changes how you draw the map.
If your sections and your table numbers do not match what the system records, you cannot get either report, which is an argument for setting the table map up properly once.
Revisit it four times a year
Section plans go stale. The menu changes and courses take longer. A wall gets moved. A runner is added. Volume shifts.
Once a quarter, pull covers by hour and sales by server, and redraw. It takes an hour and it is one of the few free improvements available to a restaurant.