See your whole floor on one colour-coded map. Tables mark themselves occupied when an order starts and free themselves the moment the bill is paid — so the host always knows what is truly open.
A colour-coded floor map that keeps itself up to date — available, reserved, occupied or cleaning.
Waiters see the whole floor at a glance with seating capacity, current order and how long the table has been occupied. Statuses move themselves: an order on a free table marks it occupied, and the final payment releases it back to available. Manual override is always there when the floor disagrees.
On a busy night the only accurate picture of the floor is in the head of whoever is running it — and it goes out of date every few minutes. A table cleared ten minutes ago still looks taken; a table that just paid is seated again before it is wiped.
The host seats a party at a table that is not actually free, waiters cover for each other and lose track of whose section is where, and walk-ins are turned away while empty tables sit unnoticed. Every one of those is a cover you could have served.
DinePilot shows every table on one colour-coded grid — available, reserved, occupied or cleaning — with its seating capacity, current order and how long it has been sitting. Everyone on shift sees the same picture at the same moment.
The statuses move on their own: an order on a free table marks it occupied, and the final payment releases it back to available. When the automatic state and the real floor disagree, a manual override is always one tap away.
No hardware to buy and no technical skills required — just a few steps to go live.
Add your tables with their types and seating, from 2-seaters to 9-plus private rooms, and print a QR sheet for each.
The host sees at a glance which tables are truly free, and seats parties without guessing or walking the floor.
The first order marks the table occupied; the grid shows its live order and how long it has been sitting.
When the bill is settled the table releases back to available — or set it to cleaning until it is wiped and reset.
Available, reserved, occupied and cleaning, colour-coded so the state of the room reads in a second.
Orders occupy tables and payments free them, so the map matches the room without anyone maintaining it.
See which tables have been sitting longest and which just freed up, and seat waiting guests sooner.
When the floor disagrees with the app, one tap sets a table right. Automatic, never rigid.
Not a competitor comparison — a comparison with the paper-and-shouting workflow most restaurants run today.
Step
The usual way
With DinePilot
Knowing what is free
Usually — Walk the floor, or ask whoever is running the pass and trust their memory.
With DinePilot — Look at one colour-coded grid. Available, reserved, occupied, cleaning.
Keeping it current
Usually — Somebody has to remember to update it, during the exact hour nobody has a spare hand.
With DinePilot — The first order occupies the table; the final payment releases it. Nobody maintains it.
Covering sections
Usually — Each waiter knows their own tables. When they cover for each other, both lose track.
With DinePilot — One shared view, so the host, the captains and the manager see the same floor.
Table turnover
Usually — No idea which tables have been sitting longest without walking over and looking.
With DinePilot — Every occupied table shows how long it has been sitting and what is open on it.
Seating a walk-in
Usually — Guessing, and sometimes seating a party at a table that was not actually wiped.
With DinePilot — Cleaning is its own state, so a cleared table and a ready table are never confused.
When the app is wrong
Usually — Not applicable — the board was always manual.
With DinePilot — One tap overrides any status. Automatic, never rigid.
It helps every dine-in restaurant, but these are the rooms where the difference is largest.
Every minute a cleared table looks occupied is a minute a waiting party is not seated. This is where turnover translates directly into covers.
Below that the floor fits in one person's head. Above it, the head goes out of date faster than it updates.
A terrace, a mezzanine or a back room that the host cannot see from the door. The map is the only way to know without walking.
Shift changes, breaks and a captain pulled to the bar. A shared floor map is what stops handover being a conversation.
Real screenshots from the DinePilot staff app — no mockups, no marketing renders.
Live table grid
Add a table
Floor at a glance
Three moments from an ordinary week, and what happens differently in each.
The host looks at the grid instead of the room. Table 12 settled its bill two minutes ago and released itself; table 7 is marked cleaning and is not offered. The party is seated at 12 without anyone walking the floor to check, and without being told there is a twenty-minute wait for a table that was already free.
Section three is covered by someone who does not normally work it. They open the same floor map, see which of those tables are occupied, how long each has been sitting and what is open on each one, and pick up mid-service without a handover conversation.
The payment released the table automatically, so the map says available while the plates are still on it. The floor sets it to cleaning with one tap — the override exists precisely for the gap between what the system knows and what the room looks like.
What the restaurants who get the most out of this do — and what trips up the ones who don't.
Table types run from 2-seaters up to 9-plus private rooms, so a room you add later — a terrace in season, a private dining space, an overflow area on weekends — is a handful of new tables and a fresh QR sheet rather than a reconfiguration. Because status is driven by orders and payments rather than by anyone remembering to update it, a floor of sixty tables takes exactly as much maintenance as a floor of ten: none.
Ask us anything else — we reply to every message.
Automatically. The first order placed on a free table — whether by QR or a waiter — moves it to occupied, so the floor map reflects the room without anyone updating it by hand.
When the bill is paid. Recording the final payment releases the table back to available, or you can set it to cleaning first until it has been wiped and reset.
Yes, always. The automatic states cover the common cases, but a single tap lets you set any table to available, reserved, occupied or cleaning when the floor disagrees with the app.
Anything from 2-seaters up to 9-plus private rooms. Each table carries its type and seating capacity, which the host sees when deciding where to seat a party.
Yes. The floor is a single shared view, so the host, waiters and manager all see the same statuses at the same moment — even when staff cover each other's sections.
They do. Reserved is one of the four states, so a table held for a booking is clearly distinct from one that is free or already occupied.
It is software that tracks the live status of every table — available, reserved, occupied or cleaning — on one shared floor map. DinePilot updates the map itself: a table becomes occupied when its first order is placed and frees up when the bill is paid, so the host always knows what is genuinely open.
DinePilot is one connected system — here is what works alongside this.
Guests scan the QR on their table and order from their own phone — no app install, no login, no waiting for a server.
Every order — QR or waiter-taken — in one filterable list, from placed all the way to completed.
Unpaid orders grouped by table, itemised bills with tax, and a receipt you can share in a tap.
Written for owners rather than for us — free to read whether or not you ever use DinePilot.
Set up your restaurant, print your QR codes and take your first order today. Starter is free.
No card required · Nothing to install for your guests