Restaurant seating software is bought to answer one question repeatedly and quickly: where does this party go. Everything else it does is scaffolding around that. The reason products differ so much is that the question is not really about parties, it is about the room, and a system that has not been told the truth about the room will answer it confidently and wrongly. This page is about what it has to be told, and what happens on the floor when it has not been.
A seating plan is a set of constraints, not a picture
The drawing on the screen is the least important part. What matters is what the system knows underneath it: which tables seat how many comfortably rather than at a squeeze, which join and which only appear to, which are reached without crossing the service route, which are cold in January, and which you would rather not give to a first time booking at seven when a regular usually rings at half past. A restaurant seating system that holds only shapes and seat counts will produce plans that look tidy and cannot be worked.
Comfortable, maximum and honest
Almost every room has three capacities and the difference between them is where the money and the arguments are. There is what the tables physically seat, what they seat with people able to get past, and what you actually fill on an ordinary service once a party of two takes a four top. The last of those is usually well under three quarters of the first, and it is the number the free worksheet on this site asks for on purpose, because a covers figure built on the first number is a forecast nobody hits.
Seating is a sequence, not a snapshot
The reason seating is hard is that a decision at seven constrains eight thirty. Putting a couple on the six top because it is free is fine until the party of six rings, and then it is the whole evening. Good restaurant seating software makes the future cost of a present decision visible, usually by showing what is still bookable after this allocation rather than only what is free now. That is the feature to ask for in a demo, and it is the one most products show worst.
What the software cannot fix
If the room genuinely has the wrong table mix for the parties that book you, no amount of seating logic will rescue it: eight twos and one six is a different business from four fours and two sixes, and the second one says yes to more of the phone calls it gets. Working the table mix as a question, before buying anything, is usually worth more than the software, and it is the reason the tool on this site takes the mix as an input rather than a fixed fact about your building.
Questions people ask about restaurant seating software
Is restaurant seating software different from a floor plan tool?
Yes. A floor plan tool draws the room. Seating software allocates parties to what the drawing describes, over time, under rules. You can run a room from a drawn plan and a pencil; what you cannot do with a drawing is know at five o'clock what is still bookable at eight.
How many seats should I assume my room fills?
Do not assume, measure. Count what you took last month against what the plan seats and you will have your own number, which is usually somewhere near three quarters and is occasionally much lower. The worksheet on this site takes it as an input for exactly that reason, because every honest capacity conversation starts with it.
Does a restaurant seating system decide my legal capacity?
No. It works with the tables you tell it about. How many people your premises may hold is a matter for your fire risk assessment and the authority that enforces it, and the published floor space factors used in building design are a different calculation from what your table plan seats.