Design a restaurant floor plan that sells

A restaurant floor plan is one of the few decisions that affects every single service. It decides how many guests the room can seat, how easily the team can move through it, how comfortable guests feel, which tables are fought over and which are dreaded, and how quickly a table can be turned or combined for a large party. Get it right and the room works quietly in the background. Get it wrong and every service is a little harder than it needs to be.

Most floor plans are not designed so much as inherited. Tables are arranged once, when the venue opens, and then adjusted by instinct over the years: a two-top squeezed in here, a booth removed there, a corner that never quite works left as it is. The result often seats roughly the right number of people, but not the right mix of parties, and not in a way that lets service flow.

This guide sets out how to design a restaurant floor plan that sells. It covers the three jobs a plan has to do, the three compromises every plan must make, how to choose the right table mix from your own bookings, how to think about covers per table, service paths and sections, how to handle the tables nobody wants, and how to turn a single layout into a set of seating plans for different services. It assumes an existing room rather than a new build, because that is where most operators are.

Every floor plan has three jobs, and they pull in different directions.

The first job is to seat covers. A room that seats more guests can take more revenue on a busy night, and the number of seats is the hard ceiling on what any service can earn. This is the job most layouts are judged on, and it is the easiest to measure.

The second job is to let service flow. Servers need to reach every table, carry plates and trays without squeezing past chairs, reach the pass and the bar quickly, and see their section. Runners need clear paths from the kitchen. Guests need to reach the toilets and the door without crossing a server's path every few seconds. A room that seats many guests but blocks service will often take less money than a slightly smaller room that flows, because everything takes longer.

The third job is comfort. Guests choose restaurants partly for how the room feels: whether they can talk without shouting, whether the table next to them is too close, whether they are sitting in a draught by the door or beside the toilets. A cramped room fills once; a comfortable one fills again.

Because those jobs pull in different directions, every floor plan is a set of compromises. It helps to name them, so you make them deliberately.

More tables mean more covers and less space between them. There is a point at which adding a table reduces revenue rather than increasing it, because it slows service and makes guests reluctant to return. That point depends on the venue: a busy café can be denser than a fine dining room. Decide where your venue should sit, and do not let the room drift denser over time without noticing.

A room full of identical tables for two can be combined in any shape, which is flexible, but it seats parties of four less efficiently than tables designed for four. A room full of fixed booths is efficient for the parties it suits and useless for the ones it does not. Most good floor plans mix a core of fixed tables matched to the most common parties with a set of flexible tables that can be combined.

Some of the most attractive positions in a room, by the window or in a quiet corner, are also the hardest to serve. Some of the most efficient positions, close to the pass, are the least pleasant to sit in. The plan has to balance where guests want to be with where the team can reach them.

The single most important decision in a floor plan is the table mix: how many tables for two, for four, for six and larger, and how many can be combined. It should come from your own bookings, not from habit or a standard layout.

Look at a month of bookings and walk-ins and count parties by size. Many venues find that couples make up a large share of their parties, that parties of three are more common than expected, and that parties of five or more are rarer but valuable. If most of your parties are couples and most of your tables seat four, you are leaving seats empty every night. If you have plenty of tables for two but cannot seat a party of eight without disrupting the room, you are turning away your largest bookings.

Once you know the mix of parties, aim for a mix of tables that seats them with as few empty seats as possible. Tables for two that can be pushed together are the most flexible building block. A few tables for four serve groups efficiently, and a larger table or a set of combinable tables handles bigger parties. Our guide to table turnover rate shows how the table mix also affects how often each table can be turned.

A useful way to judge a table mix is covers per table: how many guests actually sit at each table on average, against how many it seats. A table for four that usually seats two is running at half its capacity, even when the room looks full.

Calculate it by service. If your tables for four average around two and a half covers on a Saturday, a good share of your seats are empty at your busiest moment. That might justify replacing some fours with twos, or making more fours splittable. If your twos are always full and your fours are often seating couples, the answer is usually more twos.

There is a limit to how far this can go. A room made entirely of twos is very efficient on paper and makes groups hard to seat. The aim is not to fill every seat, which is impossible, but to reduce the empty seats that come from a mismatch between your tables and your guests.

Once you know which tables you want, think about how the team moves around them. Walk the room as a server would: from the pass to each table, from each table to the bar, from the bar to the back of the room. Every route should be clear enough for someone carrying plates, without asking guests to move their chairs.

Service stations, where servers keep cutlery, water, napkins and the till or terminal, should be positioned so that each section has one within easy reach. A server who walks the length of the room for a fork on every table is a server who has less time for guests. Keep stations out of guests' sightlines where you can, and never block a fire exit or a main path with one.

Pay attention to the busiest paths: the route from the kitchen door and the route to the toilets. These carry the most traffic and cause the most collisions. Keep them wider than the minimum, and keep tables out of them.

Divide the room into sections, each served by one server or one team, and zones, which are areas with a different character or purpose, such as the bar, a terrace or a private room.

Sections should be fair. Each should hold a similar number of covers and a similar mix of good and difficult tables, so that no server is always given the worst part of the room. Rotate sections over time, so the same people are not always on the quiet side or the busy side. Uneven sections are a common source of tension in a team and a common reason some tables are served more slowly than others.

Zones let you open and close parts of the room as trade changes. A terrace that opens in good weather, a back room used only on busy nights, a bar area kept for walk-ins: each is a zone with its own rules. Marking zones on the floor plan makes it easier to plan staffing and to tell guests where they will be seated.

Every room has tables guests ask for and tables they try to avoid. The window table, the quiet corner booth and the table with a view are requested; the table by the toilets, the one beside the kitchen door and the one in the draught by the entrance are dreaded.

Do not pretend the bad tables are fine. Make them better where you can: a screen between a table and the kitchen door, a curtain to stop the draught, better lighting in a dark corner. Where you cannot, use them deliberately: as the table you offer to walk-ins on a busy night, or the table that goes into service only once the rest of the room is full.

Watch which tables earn the least. If a table is regularly unsold, or regularly seats a single cover, it may be worth removing it to give the tables around it more space. A room with one fewer table and no dreaded seats often takes more money than a room that crams in one table nobody wants.

Large parties are often among the most valuable bookings, and they are where floor plans most often fail. A party of eight that cannot be seated without breaking up three other tables is a party you will turn away, or one you will seat at the cost of several smaller bookings.

Plan your combinations in advance. Decide which tables can be pushed together, in which shapes, and what that does to the room around them. A row of tables for two along a banquette can become a long table for eight; a pair of fours can become an eight. Make the combinations easy to set up and break down, and make sure your booking system knows which combinations exist, so it can offer them to large parties without the host having to improvise.

Bar and counter seats are often undervalued. They suit solo diners and couples, they let walk-ins be seated quickly, and they turn faster than tables. A bar with stools that guests can eat at adds covers without adding much space.

Treat bar seats as part of the floor plan, with their own covers and their own place in the seating plan. If guests can book them, make that clear. If they are kept for walk-ins, make sure the host knows to offer them first on busy nights. A busy bar also gives a waiting party somewhere to go while their table is prepared.

A floor plan that works only for guests who can walk, climb a step and squeeze between tables excludes some of your guests. Make sure there is a step-free route from the door to at least some tables, that those tables can seat a wheelchair user comfortably, and that the route to an accessible toilet is clear.

Let guests request an accessible table when they book, so the host can plan for it rather than rearranging the room on arrival. Mark accessible tables on your floor plan, so anyone seating guests knows which tables to use.

A single floor plan rarely suits every service. A Saturday night with lots of couples and two large parties needs a different arrangement from a Sunday lunch full of families. A seating plan is the floor plan arranged for a particular service: which tables are combined, which zones are open, which tables are held for walk-ins.

Keep a small number of saved seating plans for your most common situations, such as a standard weeknight, a busy weekend and a large private party. Switching between them should be a decision made the day before, not an improvisation at seven o'clock. Our guide to pacing covers covers how the seating plan and the booking slots work together.

Table assignment is the decision about which party goes to which table. Done well, it balances the floor, keeps sections even, gives regulars their favourite tables and seats large parties where they fit. Done badly, it leaves one section overloaded and another idle, and it puts couples at tables for six on the busiest night of the week.

Write down a few simple rules for the host: seat parties at tables that match their size, balance new arrivals across sections, keep the best tables for the guests who requested them, and hold back a few tables for walk-ins on busy nights. A booking system that suggests a table based on party size and availability helps, but the host should always be able to override it.

Here is an illustrative redesign for a 60-seat room, to show how the table mix changes the numbers. The figures are examples, not recommendations.

The point is not the specific layout, which depends entirely on the room and its guests, but the method. Matching the table mix to the parties you actually serve usually seats more people than adding more seats.

Before you commit to a new layout, test it. Set it up on a quiet afternoon and walk every route as a server would, carrying a tray. Sit at every table and ask whether you would be comfortable there. Check the routes to the toilets and the door, and check that every table can be reached and seen from its section.

Then run it on a moderate service before a busy one. The first few services on a new floor plan will show problems no drawing could predict: a table too close to the pass, a path that jams at nine o'clock, a corner that is colder than expected. Adjust before the room is full.

A floor plan can be measured. Track covers per table and seat utilisation by service, revenue per table, how long tables sit empty between sittings, and which tables are unsold most often. Watch these over a few weeks after any change, and compare them with the weeks before.

The tables that earn least and sit empty longest are the ones to look at first. The sections where tickets take longest to reach the table are the ones where service paths may be the problem. Measured this way, the floor plan stops being an inherited arrangement and becomes something you can improve.

In servearound, you draw the room as it is: its walls and zones, each table's shape and seats, and areas such as a terrace that opens only part of the year. You can keep a plan for every room and change it the day the room changes, and every booking, seat and check works from the same tables. Tables show their status to the whole floor, and pushing tables together for a large party treats them as one until you split them back.

Where you allow it, guests can pick their own table from the floor plan when they book, or look at the room in 3D first. Checks open on the same floor plan the host seats from. The table report in Analytics shows seatings, covers and revenue for every table and zone, the minutes each table went unsold, and shades the floor plan itself by whichever you choose. See the reservations module, or get in touch to see it with your own room. The broader idea of a floor plan, a scaled drawing of a space seen from above, is old; using it live during service is what makes it useful.

Enough for a server to pass with a tray and for guests to sit and stand without moving their neighbours. The right figure depends on the style of the venue, and local regulations may set minimums for exits and paths.

Not necessarily. Many venues keep some tables for walk-ins or for the host to assign by hand, especially on busy nights.

Review it whenever the mix of parties changes noticeably, and keep a few saved seating plans for different services so you can change the arrangement without redesigning the room.

Round tables suit conversation and fit odd spaces; square tables combine more easily. Most rooms benefit from a mix.

They add capacity and suit bars and casual venues, but guests tend to stay for a shorter time and some guests avoid them. Use them where they fit the style of the venue.

Plan the combination in advance, set it up before service, and take the booking only if the combination is available. Improvising a table for twelve at eight o'clock disrupts everyone.

A restaurant floor plan has three jobs, seating covers, letting service flow and keeping guests comfortable, and three compromises: density against comfort, flexibility against efficiency, and atmosphere against operations. Start from your own table mix, aim for covers per table that match the parties you serve, plan service paths and stations, divide the room into fair sections and useful zones, and plan your table combinations in advance.

Improve or remove the tables nobody wants, make the room accessible, keep a few seating plans for different services, write simple rules for table assignment, and test any change before a busy night. Then measure, and let the numbers tell you which part of the room to change next.