Table assignment: who decides where guests sit

Where a guest sits shapes their whole evening. The same meal feels different at a quiet corner table and at a two-top beside the kitchen door. For the venue, table assignment shapes the evening too: how evenly the servers are loaded, how steadily orders reach the kitchen, how many covers the room can serve, and whether the guests in the queue feel they were treated fairly.

Yet in many restaurants nobody has decided how tables are assigned. A booking system puts parties on tables by its own logic, guests ask for particular tables, and the host on the night rearranges everything by instinct. Each host does it differently, and on the busiest nights, when a good plan matters most, it is improvised.

This guide covers who should decide where guests sit, the rules worth writing down so any host can run the door, how table assignment interacts with the table mix, server sections and pacing, and how to keep the queue fair. Every figure in it is an example.

Each time a party is given a table, several things are decided at once:

A good assignment balances all five. A poor one usually gets the first right and the rest wrong: the guests are happy at a lovely table, while one server is drowning and a party of six waits for a table that two people are lingering at.

There are three ways tables get assigned, and most venues use a mix.

Many booking systems assign a table automatically when a booking is made, choosing a free table that fits the party. It is quick, it means every booking has a table from the start, and it works well on quiet nights. Its weakness is that it cannot see what the host sees on the night: a server who is already stretched, a regular who prefers the corner, a table that is running late.

Some venues let guests choose their own table when they book, from a plan of the room. Guests like it, especially for occasions, and it removes many requests for particular tables. Its weakness is that guests choose for themselves, not for the room: two couples may each book a six-top because it has the best view.

The host assigns tables on the night, or reviews the assignments made at booking and changes them. It is the most flexible approach, and the only one that can balance servers, pacing and requests in real time. Its weakness is that it depends on the host: a skilled host does it brilliantly, and a new host on a busy night may not.

Most venues get the best results from a mix: tables assigned at booking as a starting point, guest choice where it makes sense, and the host reviewing and adjusting before and during service, following written rules.

Written rules for table assignment turn the best host's instincts into something every host can follow. They do not need to be long; a single page at the host stand is enough. The rules below are a starting point, in a sensible order of priority.

Seat parties at tables that fit them. A two at a two-top, a four at a four, a six at a six or at joined tables. A party of two at a six-top wastes four seats for the length of their meal, and if a party of six then arrives, there is nowhere to put them.

Where the right size is not free, a slightly larger table is acceptable on a quiet night, but on a busy one it is better to offer a short wait for the right table than to tie up a larger one. Matching works best when the room has the right table mix for the parties that book; our guide to table mix covers how to get it right.

Each server can look after a certain number of tables well. Seat tables in rotation across sections, so each server gets a new table in turn rather than three at once. A simple rotation, section one, then two, then three, then back to one, keeps the load even through the evening.

The rotation should bend for party size and for how busy each section actually is. A server who has just taken a table of ten should not get the next table too, even if it is their turn. Our guide to sections and zones covers how to split the room so the rotation is fair.

Seating eight tables in ten minutes sends eight orders to the kitchen at once. Even when the tables are free and the servers can cope, the kitchen may not. Spreading seatings by a few minutes, especially for large tables, keeps orders flowing at a pace the kitchen can cook for.

Pacing covers is partly a booking decision, about which times are offered and how many guests can arrive in each, and partly a seating decision made at the door. Our guide to pacing covers so the kitchen never drowns covers the booking side, and our guide to table pacing covers the seating side.

Before seating anyone at a table, check when it is next booked. A walk-in seated at a table booked in an hour, at a table where guests usually stay two, creates a problem the host will have to solve later, in front of two parties.

Tell walk-ins how long the table is theirs if time is short: "This table's yours until eight-thirty, is that all right?" Most guests are happy to know. Our guide to turn times covers how long tables really stay.

Some guests need particular tables: a step-free route for a wheelchair, space for a pram, a quiet table for a guest who is hard of hearing, a seat near the toilets. These come first, ahead of preferences such as a window or a booth.

Plan these tables before service, from the booking notes, and keep them clear for the guests who need them. Our guide to special requests covers which requests to promise and which to try for.

Every room has tables guests prefer: the window, the corner booth, the table by the fire. Decide how they are used. Some venues give them to occasions and regulars; some to whoever books first; some to the largest spenders. Any of these can work, as long as it is consistent and the team knows the rule.

What does not work is giving the best tables to whoever the host happens to like, or holding them empty for guests who might come. A window table held all evening for a regular who never arrives is an empty table in the best spot in the room.

When the room is full and guests are waiting, table assignment becomes a question of fairness. Guests watch who is seated before them, and a party that arrived later being seated first feels unfair, even when there is a good reason.

The usual reason is size: a table for two comes free, and the party of two who arrived after the party of four is seated first. That is sensible, and most guests accept it if the host explains: "A table for two has just come free; yours will be the next four, in about ten minutes."

Queue fairness is less about strict order and more about being seen to be fair, which means explaining, keeping promises and updating guests when the wait changes. Waiting lines have their own branch of mathematics, queueing theory, but the part that matters at the door is simpler: writers on the psychology of waiting have long observed that a wait that is explained feels shorter than one that is not.

Large parties are often seated at joined tables, and joining needs planning. Decide in advance which tables can join, and how: two fours into an eight, a line of twos into a long table. Draw these combinations on the floor plan, so the host does not have to work them out at the door.

Joining tables takes them out of use for everyone else, so do it as late as you reasonably can, and split them again as soon as the party leaves. A pair of fours left joined for an hour after a party has gone is two tables lost.

Table assignment is only as good as the floor plan the host works from. An accurate restaurant floor plan, with every table numbered, its seats shown, its zone marked and its status visible, lets the host see the whole room at a glance: which tables are free, which are seated, which are on dessert, which are booked next.

A plan on a screen helps further, because it can show status as it changes. Seeing the room in 3D helps new hosts in particular, who may not yet know which table number is the one by the window. Our guide to designing a restaurant floor plan that sells covers the layout itself.

The best assignments are made before the doors open. Look at tonight's bookings and plan the tables that matter most: large parties, joined tables, guests with access needs, occasions, regulars with a favourite table, and anything requested. Leave the rest flexible.

Check the plan against the sections: if one server has three large tables booked within half an hour, move one. Check it against the kitchen: if four large tables are booked at eight, consider seating one at quarter to and one at quarter past. Ten minutes of planning before service saves an evening of firefighting.

Plans change. A table runs late, a party arrives early, a guest asks to move away from a draught. Reassigning a booking to a different table should be quick, and recorded where everyone can see it, so the server and the kitchen follow the guests to their new table.

If a party moves table mid-meal, their order and their bill must move with them. A bill left on the old table, or kitchen tickets still showing the old table number, cause confusion at the pass and at the end of the meal.

Table assignment is learned by doing, with the rules as a guide. Let new hosts shadow an experienced one through a busy service, then assign tables themselves with the experienced host beside them, then alone on a quieter night.

Ask new hosts to explain their choices: why this table, why now, why this section. Explaining the reasons builds judgement far faster than following instructions. Keep the written rules at the host stand until they are second nature.

Sometimes the host's plan and the floor's reality clash: a server says their section is full, the host says it is their turn. Agree in advance who decides. Usually the floor manager has the final word on the floor, and the host follows the manager's call. Disagreements during service should be settled in a quick word away from guests, not at the host stand in front of a queue.

A few figures show whether table assignment is working. Covers per server per shift show whether the load is even. Table utilisation shows whether tables are used, or left empty while guests wait. Waits at the door show whether tables are ready when booked guests arrive. The gap between seatings shows how quickly tables are turned and reassigned.

Look at these every few weeks. A server who consistently takes far more covers than the others, or tables that are rarely used, point to rules that need adjusting.

The written rules work best as a single page at the host stand, short enough to read in a minute. An example, for an invented brasserie:

A page like this lets a new host run the door on a busy night with the judgement of an experienced one, and gives the team a shared answer when a decision is questioned.

If guests book online, decide which tables the booking page can offer and to whom. Large tables can be kept for larger parties, so a couple cannot book a table for six on a busy night. Some tables, such as the best window table or a table kept for walk-ins, can be kept off online booking entirely and assigned by hand.

Set these rules table by table, and review them when the table mix changes. They protect the room's capacity before the host ever sees the booking.

An invented brasserie with 70 seats lets its booking system assign tables and changes nothing on the night. On Fridays, the system puts most early bookings in the front section, closest to the door; one server takes eight tables before seven-thirty while the back section sits empty, and the kitchen receives a cluster of orders from the front.

The brasserie writes six rules on a page at the host stand: match the table to the party, rotate sections, space large tables, check the next booking, needs before preferences, and window tables for occasions. The host reviews the night's assignments at five, moves bookings to balance sections, and seats walk-ins in rotation. Within a few weeks, servers' loads even out, the kitchen's Friday rush becomes steadier, and guests in the back section get the same attention as those at the front.

When online bookings are confirmed as they are made, servearound gives each one a free table, and offers the guest the waitlist when none is free. Venues can instead let guests choose their own table on the booking page, on the 2D plan, in the room in 3D, or both with a switch. Tables marked VIP are only ever assigned by hand, and each table has its own booking rules: whether it can be booked online, the party sizes it takes, and how far ahead and when. See the reservations module.

On the night, the host decides: servearound does not suggest tables to staff. Staff assign and reassign tables, seat arrived guests on the floor plan, merge and split tables, and give each table a responsible server, and the tables screen shows the room in 2D or 3D.

Table analytics show utilisation, median seating time and the gap between seatings by table and zone. Coming next is the Digital Twin: a scan of your room, or your own furniture made from photos, so the plan in 3D looks like the room your guests walk into. See Analytics.

Usually a mix: tables assigned at booking as a starting point, guest choice where it suits, and the host reviewing and adjusting before and during service, following written rules.

Match the table to the party, spread the load across servers, pace the room, respect the next booking, put needs before preferences, and use the best tables consistently.

Not if there is a good reason, such as a table of the right size coming free. Explain it to the guests who are waiting, and keep your promises.

It works well for occasions and reduces requests, but guests choose for themselves, so keep an eye on large tables booked by small parties.

Seat tables in rotation across sections, adjusting for party size and how busy each section actually is.

As late as reasonably possible for the party, using combinations planned in advance, and split again as soon as the party leaves.

Large parties, joined tables, access needs, occasions, regulars and requests, then check the plan against sections and the kitchen's pace.

Reassign the booking and move the order and the bill with them, so the server and the kitchen follow the guests.

Look at covers per server, table utilisation, waits at the door and the gap between seatings every few weeks.

Often, yes. Keep large tables for larger parties online, and keep a few tables, such as walk-in tables or the best window table, for the host to assign by hand.

Table assignment decides the guests' comfort, the servers' load, the kitchen's pace, the room's capacity and the fairness of the queue. Use a mix of assignment at booking, guest choice where it suits, and the host's judgement on the night, guided by a short page of written rules.

Match tables to parties, rotate sections, pace the room, respect the next booking, put needs before preferences and use the best tables consistently. Plan the important tables before service, explain any change in order to waiting guests, move the bill with any party that changes table, and check the figures every few weeks so the rules keep up with the room.