A seating plan for a room that changes nightly

In many restaurants, the seating plan is rebuilt every evening. At a quarter to six, someone looks at the bookings, sees a party of ten and three sixes, and starts pushing tables together. Twos are moved to make room, a four ends up in the walkway, the sections no longer make sense, and the host spends the first hour of service working out which table number is now where. The next night, it happens again, differently.

A room that changes from night to night is normal. Party sizes vary, the terrace opens and closes with the weather, private bookings take over a corner. What does not need to vary is the plan. Venues that run smoothly through those changes usually have two or three standing layouts, drawn once and used again and again, and a clear rule for which one to set up each night.

This guide covers how to build those standing layouts, how to choose the trigger for switching between them, how to keep table numbers, sections and zones consistent across layouts, and how to move tables mid service without losing track of who is sitting where. Every figure in it is an example.

A dining room is rarely set the same way two nights running, for good reasons:

Each of these is a reason to change the room. None of them is a reason to improvise.

Rebuilding the room from scratch each evening has hidden costs. Furniture is moved in a hurry by people who should be setting up. Tables end up in walkways, or too close for servers to pass. Sections are redrawn on the fly and the load becomes uneven. Table numbers lose their meaning, so the kitchen sends food to the wrong place. Bookings assigned to tables that no longer exist in tonight's arrangement have to be reassigned at the door.

Worst of all, the plan lives in one person's head. When that person is off, the room is set differently again, and the team spends the evening learning it.

A standing layout is a version of the room, drawn once and used whenever it fits the night. Most venues need only two or three:

Each layout is a complete seating plan: every table's position and number, its seats, the sections, the routes and the accessible tables. The team learns three plans instead of improvising a new one every night, and setting up becomes a matter of choosing a layout and following it.

The everyday layout is the room as it is most often needed: the table mix that matches your ordinary nights. For many venues, that means mostly twos and fours, a few sixes, and space for a pram or a wheelchair at a few tables. It is the layout the room returns to at the end of every changed night.

Build it from your own data: the party sizes that actually book on ordinary nights. Our guide to table mix covers how many twos, fours and sixes a room needs.

The large-party layout is for nights when groups dominate: weekend evenings, Sunday lunch, the weeks before the end-of-year holidays. Some twos and fours are joined into sixes, eights and tens, in places where joining is easy and the joined table does not block a route.

Plan exactly which tables join to make which large tables, and number the joined tables in a way the kitchen and servers will understand. A large-party layout that has been drawn and practised can be set up in minutes; one that is improvised takes half an hour and often ends up in the wrong place.

The event layout is for private hire, a set-menu evening, a tasting night or a celebration that takes over the room or part of it. It might be one long table, a set of round tables, or the everyday room with one section closed off for a private party.

Because events are booked in advance, the event layout can be planned with the organiser: how many guests, how they want to sit, whether there are speeches, where the cake goes. Keep a drawing of each event layout you use, so the next similar event starts from it.

The key to standing layouts is knowing which one to set, and that needs a trigger: a simple rule that decides the layout from the bookings and the conditions. Some examples:

Write the triggers down. A trigger means the decision does not depend on who is on that day, and the team can start setting up the moment it is made.

Decide the layout at a set time each day, early enough to set the room calmly and late enough that most bookings are in. For many dinner services, mid-afternoon works well. Check the diary, the weather and any events, apply the triggers, and tell the team which layout tonight is.

Once the layout is decided, bookings should be assigned to tables that exist in it. A booking assigned to a table that the large-party layout joins into an eight needs moving before service, not at the door.

Each standing layout should be drawn properly, not sketched on the back of a menu. An accurate drawing of each layout shows:

A floor plan drawn to scale prevents the most common mistake with layouts: a version of the room that looks fine on paper but blocks a walkway or squeezes a table against a pillar once it is set up. Our guide to designing a restaurant floor plan that sells covers routes and spacing.

Each layout needs its own sections. A large-party layout with three joined tables in one corner gives that section far more covers than the others unless the sections are redrawn to match. Draw the sections as part of each layout, so the load stays even whichever layout is set.

Zones, the named areas of the room such as the terrace, the window or the bar, usually stay the same across layouts, because they describe the room, not the furniture. Keep zone names consistent, so a guest who asks for the window gets the window whatever the layout. Our guide to sections and zones covers how to split the room fairly.

The most useful rule for standing layouts is that table numbers do not change. Table 12 is table 12 in every layout, standing in the same place where possible. When tables join, the joined table takes a clear name, such as the number of its first table, and the kitchen and servers know the convention.

Changing numbers with each layout causes mistakes at the pass, where tickets are sent to table numbers, and at the host stand, where bookings are assigned to them. Stable numbers mean the kitchen never has to ask where a table is tonight.

Each layout has its own table mix, and each mix should match the parties it is meant for. The everyday layout might have twelve twos, ten fours and three sixes; the large-party layout might join eight of the twos into four fours and four of the fours into two eights.

Count the seats in each layout and check them against your booking capacity for the nights it will be used. A large-party layout that seats fewer covers than the everyday one may still earn more, because large parties fill tables more completely, but it is worth knowing. Our guide to booking capacity covers how capacity is set.

Outdoor seating is the most changeable part of many rooms. A terrace layout needs a trigger based on the weather, a time by which the decision is made, and a plan for moving guests inside if the weather turns during service.

Take bookings for the terrace carefully. If a guest books outside, say what happens if it rains: a table inside, held for them, or the booking moved to another evening. A terrace with no fallback plan becomes a scramble for tables indoors at the first drop of rain.

Each layout should come with a set-up routine: who moves what, in what order, and by what time. A printed drawing on the wall of the back room, or a picture on a screen, shows the team exactly where every table goes.

Practise the change between layouts during a quiet afternoon, and time it. Most changes take far less time once the team has done them a few times, and the drawing removes the debates about where a table should go.

Sometimes the room has to change during service: a large walk-in party, rain on the terrace, a booked party twice the size it said. Moving tables mid service is risky, because guests are seated, orders are in the kitchen, and bills are open. Done carelessly, it loses track of who is where.

A few rules keep it safe:

A table moved without telling anyone is how food ends up at the wrong table and bills end up on the wrong party.

The booking diary needs to know which tables exist tonight. If the large-party layout joins tables 3 and 4 into an eight for the evening, both tables must be blocked in the diary for the length of the booking, or online booking will happily sell table 4 to someone else.

Record joins and splits in the same place as bookings, and check them whenever the layout changes. Our guide to double bookings covers joined tables as one of their common causes.

Drawing a layout on paper is good; seeing it from a guest's height is better. A 3D view of the floor plan shows what a drawing from above cannot: whether a pillar blocks the view from the corner table, whether a joined table feels cramped against the wall, whether the route from the door to the accessible table is as clear as the drawing suggests.

Look at each standing layout in 3D before setting it up for the first time, and walk the routes in the real room once it is set. The fewer surprises when the furniture moves, the faster the team learns the layout.

Every member of the team should know the standing layouts: what each one is called, when it is used, where the tables go and how the sections change. Show new starters the drawings in their first week, and let them set the room once with someone who knows it.

Name the layouts simply, such as everyday, large parties and events, so the instruction at the start of a shift is a single word everyone understands.

Layouts age. The table mix that suited last winter may not suit the summer; a new menu may bring more large parties; a refurbishment may move a wall. Review the standing layouts at the start of each season, using your booking data: party sizes, how often each layout was used, where guests waited.

If one layout is used almost every night, perhaps it should be the everyday layout. If one is almost never used, perhaps it is not needed.

Sometimes the layout is decided at three o'clock and a booking for twelve arrives at four. Decide in advance what happens. If the booking arrives before a set time, switch to the large-party layout. If it arrives later, join tables within tonight's layout, using a combination planned in advance, rather than rearranging the whole room an hour before service.

A rule like this means the host does not have to choose between turning away a large booking and rebuilding the room in a hurry. The combinations available within each layout should be drawn on its plan, so a late large booking always has somewhere to go.

Layout drawings go out of date quietly. A table is replaced with a larger one, a banquette is added, a fridge is moved, and the drawing on the wall no longer matches the room. Within a few months, the team stops trusting it and goes back to improvising.

Keep one master copy of each layout, date it, and update it whenever the furniture changes. Throw away old copies, so there is never a choice between two drawings. A drawing that matches the room is one the team will keep using.

An invented restaurant with 64 seats rearranges its room every Friday and Saturday by instinct. Setting up takes forty minutes, tables end up in walkways, and the kitchen regularly sends dishes to the wrong table because numbers change with each arrangement.

It draws three standing layouts: everyday, large parties and private room. The trigger is simple: three or more bookings of six or more means the large-party layout; a private booking means the private room layout. Table numbers stay fixed, joined tables take the number of their first table, and each layout has its own sections. Setting up now takes fifteen minutes from a drawing on the wall, and mistakes at the pass become rare.

servearound draws your rooms on floor plans, one for each room or floor, such as the main floor and the terrace. In the designer, you move the walls to match the room's real shape, place round, square, long and bar tables with their seats, mark zones such as the window or the terrace, and add landmarks: the bar, the kitchen, the entrance, the host stand, server stations, pillars and stairs. The 3D view shows the room from above, at an angle or in perspective, with the walls cut away, before a table is moved. See the reservations module.

servearound does not save alternative layouts of the same room today: a table stands on one plan at a time, so keep your standing layouts as drawings, and make each night's changes on the tables screen, where staff merge and split tables, reassign bookings, and on the till move a bill and its kitchen tickets to another table. Coming next is the Digital Twin: a scan of the room, or your own furniture and finishes made from photos, so the plan in 3D looks like your room.

A version of the room, drawn once and used again whenever it fits the night, such as an everyday layout, a large-party layout and an event layout.

Usually two or three. More than that becomes hard for the team to remember.

With a written trigger based on the bookings and conditions, such as the number of large parties or the weather, applied at a set time each day.

No. Keep each table's number the same in every layout, and give joined tables a clear name the kitchen understands.

Yes. Draw the sections as part of each layout, so the load stays even whichever one is set.

Move empty tables where possible, move any party's order and bill with them, tell the servers and the kitchen, and update the booking.

With a weather trigger, a set time for the decision, and a fallback plan for moving guests inside if the weather turns.

Yes. It shows sightlines, cramped corners and routes that a drawing from above can hide, before any furniture is moved.

At the start of each season, using your booking data and how often each layout was used.

Have a rule: before a set time, switch layouts; after it, join tables within tonight's layout using a combination already drawn on its plan.

A room that changes every night does not need a new seating plan every night. Draw two or three standing layouts, everyday, large parties and events, each a complete plan with table positions, seats, sections, routes and accessible tables, and set one by a written trigger at a set time each day.

Keep table numbers fixed, redraw sections for each layout, block joined tables in the diary, plan a fallback for the terrace, and move bills with any party that changes table mid service. Check each layout in 3D before setting it up, train the team on all of them, and review them every season so the room keeps matching the guests who book it.