Floor plan software: what it has to do on a Friday

Floor plan software looks wonderful in a demo. The room appears on the screen, tables glide into place, the colours are lovely and the salesperson seats an imaginary party with a flourish. Then comes the first busy Friday. The host has a queue at the door, the phone is ringing, a table of eight wants to move, and the software that looked so smooth on a quiet afternoon turns out to need six taps to seat a party and shows nothing about which tables are about to free up.

The gap between the demo and the Friday is the most important thing to understand when choosing floor plan software. A plan on a screen has two jobs: designing the room, which happens occasionally and calmly, and running the room, which happens every night under pressure. Demos show the first. Fridays test the second.

This guide sets out the six things floor plan software has to do at the peak of a busy night, where a 3D view of the room earns its place and where it does not, the features that look good in a demo and fail at the door, and the questions to ask before you choose. Every figure in it is an example.

A restaurant floor plan on a screen does two different jobs.

The first is design: drawing the room, placing tables, marking zones and sections, planning layouts for different nights. This happens when the venue opens, when it changes the room, and when it plans events. It can take time, and it should be thorough.

The second is operation: showing the room as it is right now, seating parties, moving them, joining and splitting tables, and seeing what is coming next. This happens hundreds of times a night, under pressure, often by someone with a queue in front of them. It has to be fast.

Good floor plan software does both, and keeps them apart: everything the designer needs when designing, and nothing in the way when running the room.

A demo is usually done on a large screen, in a quiet room, by someone who knows the software perfectly, with a sample restaurant that has a dozen bookings. Every feature works, and there is time to admire each one.

A Friday is done on whatever screen is at the host stand, in a noisy room, by a host who may have started last month, with a full diary, walk-ins, late arrivals and a kitchen that is behind. The only features that matter are the ones the host can use in seconds. When you watch a demo, imagine the Friday.

At the peak, the host needs to see the whole room in one look: which tables are free, which are seated, which are booked next and when, which are waiting to be cleared, which are joined. Status is the most important thing a plan on a screen shows, more important than how the tables look.

Status should change as the night changes, without anyone refreshing anything: a party seated at one screen shows as seated everywhere. A plan that shows the room as it was ten minutes ago is worse than no plan at all.

Seating a party is the action the host repeats most, so it must be quick. Find the booking, tap the table, done. Or tap the table, choose the party that has arrived, done. Anything more, a form to fill in, a confirmation to dismiss, a menu to open, is multiplied by every party in the evening.

Count the taps in the demo. Then ask how many it takes to seat a walk-in, to seat a party at a different table from the one they were booked at, and to seat a party that is only half there.

A host does not just need to know which tables are free now; they need to know which will be free soon and which are needed next. A table that is free but booked in twenty minutes is no use to a walk-in for two who will stay an hour.

Good floor plan software shows each table's next booking and how long the current party has been seated, so the host can judge when it will free up. Without that, the host keeps it all in their head, which is exactly what the software was meant to stop.

Fridays change the room. A party of ten needs three tables joined; a large party that was booked as eight arrives as five and the tables need splitting; a couple wants to move away from a draught. Joining, splitting and moving should each take seconds.

Moving tables mid service is the hardest test. When a seated party moves, their order and their bill must move with them, and the kitchen must see the new table on their tickets. Software that moves the guests on the plan but leaves the bill on the old table creates confusion at the pass and at the end of the night. Ask to see a party moved mid-meal, with an order already in the kitchen.

The booking's notes, the allergy, the anniversary, the wheelchair, the guest who must leave by nine, need to show on the table itself, not only in the booking. The host should see them when seating, and the server when serving.

Allergies need to go further, to the kitchen ticket with the order. Floor plan software that shows notes only when you open the booking leaves most of them unread.

On a Friday, the plan is used by several people at once: the host at the door, the manager on the floor, perhaps a second host, perhaps the kitchen. Each needs the same picture, updated as the others act. Signing in should be quick on shared screens, so the person who seated each party is recorded without slowing anyone down.

The plan should also work on the screens the team actually has: the host stand's screen, a tablet carried on the floor, the manager's phone. Software that only works well on a large monitor in the office is not floor plan software for a Friday.

Some features impress in a demo and get in the way at the door. Watch for these.

Beautiful drawings of the room, with plants and textures and lighting, are lovely for designing and for showing guests. At the door, they matter far less than knowing which tables are free. If the demo spends more time on the decoration than on the status, ask to see a full Friday's worth of bookings on the plan.

Automatic table assignment is useful as a starting point. Assignment that the host cannot easily change, or that changes things the host has already decided, causes chaos on busy nights. Ask how the host moves a booking to another table, and whether some tables can be kept for assignment by hand.

Every extra tap is multiplied by every party, every night. Features that need a menu, a dialog and a confirmation for a common action will be bypassed on a Friday, and the plan will drift away from the room.

Charts and analytics are valuable after service. During service, they should stay out of the way. Software that puts graphs on the host's screen at eight on a Friday is designed for the demo, not the door.

Some systems make it easy to draw a plan that looks nothing like the real room: tables in the wrong places, walls in the wrong shape, numbers that do not match. A plan that does not match the room confuses new staff and loses its value. The designer should make it easy to draw the room as it really is, and to keep it that way when the room changes.

A 3D view of the room has become a feature of floor plan software, and it is fair to ask whether it matters. It does, for particular jobs.

When designing the room, 3D shows what a flat plan hides: whether a pillar blocks the view from the corner table, whether a joined table feels cramped, whether a route that looks clear from above is clear at eye height. When guests choose their own table when booking, seeing the room in 3D helps them pick the window or the quiet corner they actually want. And for new staff, a 3D view of the room is the fastest way to learn which table number is where.

At the door on a Friday, a flat plan is usually quicker to read at a glance. The best software lets anyone switch between the two in a tap, and falls back to the flat plan on screens that cannot draw 3D. 3D in a web browser depends on WebGL, which most modern devices support but some older ones do not, so a fallback matters.

Software can only show the plan you give it. Before choosing floor plan software, it helps to know how your room works: your standing layouts, your table mix, your sections and zones. Our guide to a seating plan for a room that changes nightly covers standing layouts, and our guide to sections and zones covers splitting the room between servers.

Then ask how the software handles each: can it show sections, can it join tables in the combinations you use, can it hold different rooms or floors?

The design side of floor plan software should make it easy to draw the room accurately once, and keep it accurate:

A room drawn properly once saves hours of confusion afterwards. Our guide to designing a restaurant floor plan that sells covers what the layout itself should achieve.

Table assignment on a busy night follows rules: match the table to the party, rotate sections, pace the kitchen, respect the next booking. Floor plan software should support those rules, not replace them. Showing each table's server, seats and next booking helps the host apply the rules quickly; filtering the plan by server or by size helps them find the right table.

Our guide to table assignment covers the rules themselves.

Some venues let guests choose their table when they book, from the plan of the room. It reduces requests for particular tables and pleases guests booking occasions. If you want this, ask how the guest sees the room, whether some tables can be kept off the booking page, and what happens when the guest's chosen table is needed for something else.

After service, the floor plan becomes a report. Shading each table by how often it was used, how long guests stayed or what it earned shows which tables work hardest and which are wasted. A plan shaded by utilisation shows, at a glance, the corner nobody wants and the window everyone books.

These views belong after service, in the office, not at the host stand during it.

Bring these questions to any demo of floor plan software:

Our guide to choosing restaurant software without a demo haze covers demos more generally.

The only real test of floor plan software is a busy night. If you can, run a trial: draw your room, put a real weekend's bookings in, and run a Friday with the new software alongside the old. Ask the host what slowed them down.

If a full trial is not possible, run a rehearsal: an afternoon with the whole team, the real room drawn in the software, and a pretend Friday of bookings, walk-ins and changes. You will learn more in an hour than in a week of demos.

Floor plan software is usually part of a wider reservations system, priced per venue. Compare what is included: the designer, the live plan, guest table choice, analytics, the number of screens and staff. Our pricing page sets out what servearound includes.

An invented restaurant chooses floor plan software from a polished demo full of beautiful drawings. On its first busy Friday, the host finds that seating a party takes five taps, the plan does not show when tables are next booked, and moving a seated party leaves their bill on the old table. By eight, the host has gone back to a printed plan and a pencil.

For its next choice, the restaurant brings a list of Friday questions to every demo, counts taps, and runs a rehearsal with its own room and a full weekend of bookings. It chooses software that seats in two taps, shows each table's next booking, moves bills with parties and lets the host switch between the flat plan and the room in 3D. On the next busy Friday, the printed plan stays in the drawer.

servearound's floor plans do both jobs. In the designer, you move the walls to match your 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, stairs, pillars and more, renamed, resized and recoloured. A grid, shortcuts and undo make it quick. The room can be seen in 3D from above, at an angle or in perspective, with the walls full, cut away or off. See the reservations module.

On the night, the tables screen shows every table's status, available, reserved, occupied, needs cleaning or merged, in 2D or 3D, filtered by plan, server or size. Staff seat an arrived party from the table itself, merge and split tables, reassign bookings, and on the till move a bill and its kitchen tickets to another table.

Notes and allergies show on the reserved table, and guests can choose their own table on the booking page, on the 2D plan, in 3D or both, with the flat plan wherever a browser cannot draw 3D. After service, table analytics shade the floor plan by any figure. Coming next is the Digital Twin: scan your room into 3D, or make your own chairs, tables and finishes from photos, so the plan looks like the room your guests walk into.

Show the room at a glance, seat parties in a couple of taps, show what is coming next, change the room quickly, carry notes to the table and work for the whole team at once.

Yes, for designing the room, for guests choosing a table and for training new staff. At the door, a flat plan is often quicker, so a quick switch between the two matters.

Live table status: which tables are free, seated, booked next and waiting to be cleared.

The party's order and bill should move with them, and the kitchen should see the new table on their tickets.

As a starting point, yes, but the host must be able to override it easily, and some tables should be kept for assignment by hand.

Count the taps to seat a party, ask to see a party moved with an order in the kitchen, and check where notes appear and how it works on a tablet.

Yes. A plan that drifts from the room confuses staff. Draw the real walls, tables, zones and landmarks once, properly.

With some software, yes. Check how the room looks to the guest and whether some tables can be kept off the booking page.

Run a rehearsal with your real room and a full weekend of bookings, or a trial alongside your current system on a real busy night.

Floor plan software has two jobs: designing the room, calmly and occasionally, and running it, fast and under pressure. Demos show the first; Fridays test the second. Judge it on six things: the room at a glance, seating in a couple of taps, what is coming next, joining, splitting and moving quickly, notes on the table, and the whole team working from one picture.

3D earns its place in designing the room, in guests choosing a table and in training, with a quick switch to the flat plan at the door. Beware decoration without status, assignment you cannot override, too many taps and reports in the way of service. Bring Friday questions to every demo, and test with your real room before you commit.