Front of House

Restaurant Section Assignments: Who Takes Which Tables Tonight

Many dining rooms decide restaurant server sections the same way. Around 4 PM, a manager looks at the floor plan, remembers who usually takes the patio, and writes names on a whiteboard. It takes two minutes and feels fine. Then the eight-top lands with the newest server, the strongest closer gets four two-tops by the kitchen door, and the night runs a little worse than it needed to.

I'm Richard Yu. I have more than 15 years of startup and go-to-market experience, much of it in customer success and solutions engineering, and I'm a co-founder and the Managing Partner for marketing and operations at the restaurant I co-founded in San Francisco. I built Regular, the hospitality operating system, inside that restaurant, one service at a time. My argument here is simple: section assignments should come from who is actually working tonight and how each of them does with those tables and party sizes, and doing it that way takes about ten minutes.

Sections Made From Habit

Habit sections usually come from three places: seniority, the last chart that seemed to work, and whoever complained most recently. None of these is wrong on its own. The problem is that they describe last month's team and last month's book, not tonight.

Picture a Friday where the book has three six-tops between 7:00 and 7:45, all in the back room. The habit chart gives the back room to the server who has had it for a year. That server may be excellent with deuces and slower with big parties, something that may never have been checked, because the chart was a copy rather than a decision.

Habit also hides its cost. When a section is wrong, the symptoms show up somewhere else: a long gap between seated and first order, the 8:15 party standing at the host stand, one server in the weeds while the next section over is quiet. Managers tend to fix those in the moment and rarely trace them back to the 4 PM chart.

I treat the section chart as the first operating decision of the night. In my experience it shapes more of the service than most of what gets said at lineup.

Start From Who Is Actually Working

Before anyone touches the floor plan, I start from the schedule as it stands at 4 PM, not as it was posted on Monday. Shifts get swapped, someone calls out, a new hire is on their third night. A chart built from the posted schedule breaks the first time reality differs from it.

Three questions come first. Who is confirmed, meaning on the schedule and expected to clock in? Who is new enough to need a smaller or simpler section? Who is cut early, so their tables should be the ones that empty first?

Then I match the number of sections to the book, not to the number of servers who happened to be scheduled. If forty covers are booked before 7:00 and a hundred after, an early section can be folded into a neighbour when the opener leaves. Planning that handoff at 4 PM is far easier than improvising it at 8:30 with a full room.

This is also part of good front of house management more broadly: the pre-shift hour is where the night gets decided, and the schedule is the first thing to read in it.

Match Servers to Tables and Party Sizes

The second input is server performance, and specifically performance by table and party size, not one overall ranking. A server who turns two-tops quickly and sells wine well might be the wrong choice for a ten-top that needs patient pacing and split checks. Another might be at their best with large parties and only average with deuces.

You can see this when you split each table turn into stages: seated, ordered, courses out, check dropped, departed. Compare where each server's time goes on four-tops versus six-tops, and look at spend per guest by table type. Over a few weeks, patterns appear that the whiteboard does not show. I wrote more about reading those stages in my piece on coaching the stages of a table.

In software customer success, much of my job was deciding which person on the team took which accounts. The lesson carried over directly: assignments go better when they follow what someone does well with that kind of customer, not who had the account last.

In Regular, table assignment does this pairing. It suggests who takes which section tonight from who is on the schedule and how each server does with those tables and party sizes. The manager still makes the call.

Balancing Fairness and Results

The obvious objection is that sections are money. Give the strongest server the best section each night and the rest of the team earns less, learns less and may eventually leave. That objection is right, and a chart built purely on results will wear a team down.

Here is how I balance it. I rotate the highest-earning sections across the week rather than within a night, so a server might get the back room on Friday and the bar-side tables on Tuesday. I give newer servers sections that stretch them by one step, such as one six-top among deuces, rather than the whole party room. And I explain the chart at lineup in a sentence, so the team does not have to guess why.

Where tips are pooled or shared, check your local rules, because how sections and tips interact varies by place.

Visibility matters too. Staff should see their own numbers so an assignment does not feel like a verdict. Server Performance pairs its rankings with coaching notes, which is the right spirit: the reason to look at how someone does with large parties is to help them get better at large parties, not to keep them away from those tables.

A Ten-Minute Section Routine

Here is the routine I would use at your next service. It fits between the schedule check and lineup.

  1. Confirm who is clocking in tonight and who is cut early.
  2. Read the book: covers by hour, large parties and where they are seated.
  3. Mark the tables that matter most: big parties, tight back-to-back bookings, regulars and celebrations.
  4. Assign those tables first, to the servers who do best with that table type and party size.
  5. Fill the rest of the floor plan, giving newer servers one stretch table.
  6. Check the rotation: has the same person had the top section three nights running?
  7. Plan the early cut: whose section gets absorbed, and by whom.
  8. Explain the chart at lineup, one sentence per section.
  9. After service, note one section that worked and one that did not.

Step nine is what turns habit into a system. A week of those notes tells you more than a year of whiteboards.

On technology: it should do the counting and hand the manager a starting chart. It should not decide who earns what tonight, and it should not put a screen between the manager and the team at lineup. The suggestion is a draft; the manager signs it. If you want to see how Regular drafts that chart, you can book a demo. And if you run sections in a way that works for your room, tell me on Instagram.

Frequently Asked Questions

How do restaurants decide server sections?

Many restaurants assign sections from habit: seniority, last week's chart or who usually works a given area. A stronger approach starts from who is actually clocking in tonight, then matches servers to the tables and party sizes they handle best, while rotating the highest-earning sections across the week so the team stays fair and keeps learning.

How many tables should a server have in a section?

It depends on the room, the menu and the service style rather than a fixed number. Many managers size sections by expected covers and party sizes instead of table count, give newer servers smaller sections with one stretch table, and plan how sections merge when early servers are cut so the late room is not overloaded.

Should the best server always get the best section?

Giving the strongest server the top section every night tends to cost the rest of the team earnings and experience. A common balance is to give the most important tables to the best fit for that night's book, rotate premium sections across the week, and use coaching so more servers become strong with large parties over time.

Can software assign restaurant sections?

Software can suggest a starting chart by combining the schedule with how each server performs by table and party size. The manager should still make the final decision, adjust for things the data cannot see, and explain the chart at lineup. The useful role for technology is counting and drafting, not deciding who earns what.

Regular

Run the Night Your Regulars Remember

One suite of apps that connects your reservations, POS and schedule, from before the meal to the next visit.