Restaurant Floor Plan Software
See the whole floor, live. Every table's real status, in one view — not a static chart a host has to cross-check against memory.
Why it matters
Most venues already have a floor plan. It is a laminated sheet at the host stand, or a drawing in somebody's head, and it answers exactly one question: where the tables are. Everything an operator actually needs to know during service — which of them are free, who is on which, what has been ordered where, which one is promised to a party arriving at eight — lives somewhere else. Usually in four different somewhere elses.
That is where the disagreements come from. The booking system thinks table nine is free because nobody told it about the walk-in. The waiter thinks eleven is his because he was on it last night. The kitchen sends a plate to a table that got moved twenty minutes ago. None of these are mistakes people make out of carelessness — they are what happens when four things that all describe the same room keep separate copies of it.
Drawing the room once fixes the category of problem rather than any one instance of it. Reservations, orders, events, large parties, the QR codes on the tables and the servers' own screens all read the same plan. Move a table in the designer and it has moved for every one of them. There is no second place to update and nothing to reconcile at the end of the night, because there was only ever one room.
Drawing the room
Drag tables where they actually are
Position, size and angle. A room where nothing is square is drawn as a room where nothing is square, because a plan a host has to mentally rotate is a plan they stop reading during service.
The shapes you really have
Round, square, rectangle, oval, booth and bar seat. A booth is not a four-top with different upholstery and a bar stool is not a table, and a floor plan that pretends otherwise seats parties wrong.
The things that aren't tables
The bar, the kitchen door, the entrance, the walls, the restrooms, the big plant everyone navigates around. Landmarks are what make a plan legible at a glance — without them it is a grid of numbers and nobody can find anything on it.
More than one room
Ground floor, terrace, upstairs, the private room. Each is its own plan, in the order you want them, rather than one drawing trying to be a building.
Sections that mean something
Group tables into the sections your servers actually work. It is what a shift gets rostered to, what a claim defaults to, and what reporting can be read by afterwards.
Seats per table, and they count
Seat counts are not decoration. They are what availability is computed from, so a party of six is never offered a table that seats four however empty the room looks.
The floor during service
A plan is only worth drawing if it tells you something at half past eight on a Saturday. This is what it carries once the room is full.
Status, changing as it changes
Available, occupied, reserved, being cleared, out of service. Every screen looking at the plan sees the same state at the same moment — the host stand, the servers' phones, the owner at home.
Waiters claim their own tables
Staff take the tables they are working, from their own portal. Nobody is assigned a section by an owner who is not in the room, and every order that lands on a table is credited to whoever is actually holding it.
A claim ends with the shift
Holding a table lasts as long as the service does. It lapses at the end of it, so tomorrow's orders are never stamped with whoever happened to claim that table last week.
Push two tables together, and pull them apart
A party of eight arrives and two four-tops become one. Merge them on the plan and split them afterwards — and a table with a live order or a booking on it refuses to be merged, because moving furniture under an open bill is how a night goes wrong.
A new party starts a clean bill
When a table turns over, the bill turns over with it. The couple who just sat down cannot see what the party before them ordered, and staff don't have to remember to clear anything down.
Calls arrive on the table that made them
A guest asking for a waiter from the code on their table shows up against that table on the plan, rather than as a notification somebody has to interpret.
What else reads the plan
The floor plan is not a module with a screen of its own so much as the thing the other modules agree about. Everything below is looking at the same room.
Reservations
Bookings are made against real tables with real seat counts, and a table already spoken for is not offered again. A booking holds its sitting and then gives the table back.
Events and large parties
An evening that takes tables, or a party of twenty an enquiry has been holding since March, stands on this floor like anything else — and comes out of the same pool ordinary bookings are offered from.
Orders and the kitchen
Orders belong to tables, so the kitchen knows where a plate is going and the waiter holding that table is the one told when it is ready.
The code on the table
Every table carries its own short code for its QR. It is not the table number, so nothing is guessable from a web address — and because the sticker encodes only the table, you can point the terrace at a different menu without reprinting a thing.
Common questions
Can I lay it out to match our actual room?
Yes. Tables are placed, sized and angled where they really are, alongside the bar, the entrance, the walls and anything else that helps somebody find a table at a glance. Separate rooms — terrace, upstairs, a private room — are separate plans.
Is the floor plan the same one guests book against?
Yes, and so are your events and your large parties. All of them stand on one floor, which is what stops a table being promised to two of them.
How long does a booking hold a table?
For its sitting — a start, a length and an end — rather than the whole evening, so the table is offered again as soon as that window closes. Cancel it or mark a no-show and it comes back immediately.
Can we push tables together for a big party?
Yes. Merge them on the plan and split them afterwards. A table carrying a live order or a booking won't merge — that's deliberate, because rearranging furniture underneath an open bill is how a night goes wrong.
Who decides which waiter is on which table?
The waiters do, from their own portal. A shift rostered to a section starts with that section suggested, but nobody is assigned tables by someone who isn't in the room.
Does a table stay assigned to the same waiter forever?
No — a claim lasts as long as the shift it was made on. It lapses at the end of service, so next week's orders aren't credited to whoever happened to be on that table last night.
Does the next party see the last party's bill?
No. Turning the table over starts the bill fresh, so what the previous party ordered is gone from the table's running total without anybody having to clear it down.
Can different parts of the room run different menus?
Yes. Each table's QR opens the menu you've pointed it at, and the sticker only encodes the table — so switching the terrace to a terrace menu doesn't mean reprinting anything.
Do we need to redraw it when we move things around?
Move it in the designer and it has moved everywhere — bookings, orders, events, the servers' screens. There is no second copy to update.