Restaurant Table Statuses: An 11-State System for Smoother Service (2026)

August 7, 2026 at 6:32 PMTabres Team

table management restaurant table statuses table turnover restaurant floor plan front of house restaurant operations

Most restaurants run their floor on three table statuses: free, taken, and dirty. That's why the host seats a party at a table that's still waiting on a card payment, and why table 7 sits empty for 20 minutes because nobody knew it was ready.

A restaurant table status is the one word that says what's happening at that table right now. Eleven of them cover every real situation on a floor: vacant, reserved, pending confirmation, seated, occupied, bill requested, awaiting payment, needs cleaning, no-show, blocked, and out of service. Each one needs an owner and a trigger. Get that right and you'll turn more tables without rushing a single guest — mostly by killing the dead minutes between them.

It sounds like admin. It isn't. It's the difference between a floor everyone can read at a glance and a floor that runs on shouting.

What a Table Status Actually Is

A table status answers one question: what is this table doing at this exact second?

Not what it did earlier. Not what it should be doing. Right now.

That's the whole idea, and it's why "taken" is such a weak status. A table can be taken and still waiting to order. It can be taken and finished eating. It can be taken by people who paid 10 minutes ago and are now just chatting. Those are three completely different situations for the host, the waiter, and the kitchen — and one word hides all three.

Three statuses tell you the table is busy. Eleven tell you what to do about it.

The 11 Table Statuses at a Glance

Status	What it means	Who sets it	Typical duration
Vacant	Clean, set, ready to seat	Whoever finishes the reset	Until seated
Reserved	Held for a named party at a time	Host stand	Until arrival
Pending confirmation	Booking exists but isn't confirmed	Host stand	Until confirmed or dropped
Seated	Party is down, hasn't ordered yet	Host	3–10 min
Occupied	Order is in, service running	Automatic on first order	30–120 min
Bill requested	Guest has asked for the bill	Waiter or guest tap	1–4 min
Awaiting payment	Bill is on the table, unpaid	Automatic when bill prints	3–10 min
Needs cleaning	Paid, guests gone, not reset	Automatic when payment settles	Target under 7 min
No-show	Booking never arrived	Host, after a grace window	Until released
Blocked	Deliberately kept empty	Manager	Hours
Out of service	Broken, unusable	Manager or maintenance	Days

Seven of these form the normal service loop. Two handle bookings that go sideways. Two take a table out of play. That's the whole system.

The Service Loop: Seven Statuses, One Circle

Here's the path a working table walks every single time:

Vacant → Seated → Occupied → Bill requested → Awaiting payment → Needs cleaning → Vacant

Add Reserved at the front when the party booked ahead. That's it. Every shift, every table, same circle.

The value isn't the diagram. It's that each step hands work to a specific person. When a table flips to "needs cleaning", that's a busser's job appearing on a screen instead of a manager walking the room looking for plates.

1. Vacant

Clean, set, cutlery down, ready for the next party.

Vacant means ready, not empty. That distinction matters more than anything else on this list. An empty table with crumbs and a used glass is not vacant — it's needs cleaning. If your team treats them the same, hosts will seat guests into a mess, and that's a bad first 30 seconds you can't get back.

One rule: the person who finishes the reset sets it to vacant. Not the person who cleared the plates. Not the host who assumes. Whoever puts the last fork down.

2. Seated

The party is down, menus are with them, nothing ordered yet.

This is the status most floors skip, and skipping it costs you. Seated is a countdown. If a table has been seated for more than 8 minutes with no order, something's wrong — the waiter hasn't been over, the guests are stuck on the menu, or the section is drowning.

You can't see that problem if seated and occupied are the same word. With them split, a manager glances at the floor and spots the four tables that have been sitting too long without a drink in front of them.

Target: first order in within 5 to 8 minutes of seating. In a café, 3.

3. Occupied

An order is in. Food and drinks are moving. This is the long, normal part of the meal.

Occupied should set itself the moment the first order lands, not by hand. Anything a waiter has to remember to tap during a rush will be forgotten in the rush.

How long occupied lasts is your dwell time, and it varies wildly by format:

Coffee shop / quick service: 20–35 minutes
Casual dining: 45–75 minutes
Full service dinner: 75–110 minutes
Fine dining: 100–150 minutes

Know your real number before you try to improve it. Most owners guess 60 and the actual figure is 85.

4. Bill Requested

The guest has asked for the bill. The bill hasn't arrived yet.

This tiny status is worth more than it looks. It's the moment a guest mentally leaves — and the moment your risk of a bad review spikes. Everything up to now can be excellent, and a 9-minute wait for a bill will still be what they tell their friends about.

Target: bill on the table within 3 minutes of the ask. Not five. Three.

In 2026 this status often arrives on its own. When guests order or pay from a QR menu at the table, "bill requested" comes in as a tap rather than a wave across the room. That's a real upgrade for a floor with two waiters and 20 tables — nobody has to catch anyone's eye. If you're setting that up per table, this is worth a read: one QR code per table.

5. Awaiting Payment

The bill is on the table. Money hasn't landed yet.

Keeping this separate from "bill requested" is what stops the classic disaster: the host seats a new party at a table where the last group is still hunting for their card. Awaiting payment means do not touch this table yet.

It's also where split bills live. Six people, four cards, two paying cash — that table can sit in awaiting payment for 10 minutes, and that's fine as long as everyone can see why. If splitting is common in your place, the practical side is here: how to handle split bills.

Worth being precise about the words too: a bill is what's owed, a receipt is proof it was paid. Mixing them up on a busy floor causes real confusion — the difference, in plain terms.

6. Needs Cleaning

Paid, guests gone, table not reset. Also called dirty, bussing, or "on the turn".

This is the single most profitable status in the whole list, because it's the one that's usually invisible. Nobody's sitting there. Nothing's happening. And you're not making money.

Do the arithmetic once and you'll never ignore it again. Take a 10-table restaurant, five hours of dinner service, 75-minute dwell:

Reset takes 14 minutes: cycle is 89 minutes → about 3.4 turns per table
Reset takes 6 minutes: cycle is 81 minutes → about 3.7 turns per table

That's roughly 3 extra parties across the floor per night. At a $70 average check, that's about $210 a night. If you're genuinely full three nights a week, you're looking at somewhere near $32,000 a year — from bussing faster, not from selling harder.

The honest caveat: this money only exists when people are waiting. On a quiet Tuesday, a fast reset earns you nothing. That's a different problem, and there's a whole playbook for it: how to fill empty tables on slow weekdays.

Target: under 7 minutes from payment to vacant. Time it yourself this weekend. Most floors think they're at 6 and are actually at 15.

The Booking Statuses: Reserved, Pending Confirmation, No-Show

These three cover the gap between "someone said they're coming" and "someone actually came".

Reserved holds a table for a named party at a set time. The trap is holding it too early. A table blocked from 6 p.m. for an 8 p.m. booking is two hours of dead seats. Hold it around 15 to 20 minutes before, no more, and let it stay vacant until then.

Pending confirmation is for bookings that aren't solid yet — a big group that hasn't come back to you, a request that came in by message, a party that owes you a deposit. It stops a maybe from being treated as a yes. Large tables are where this earns its keep: losing a 12-top on a Saturday because nobody chased the confirmation is an expensive silence.

No-show is the one nobody wants to set, and it should be almost automatic. Pick a grace window — 15 minutes is the usual — and after that the table goes back into play. Write the rule down and give the host permission to use it. Without a written rule, hosts hold tables far too long, because releasing one feels like a decision they might get blamed for.

Track no-shows by weekday and by party size. If 8-plus tops no-show twice as often as everyone else, you've just learned which bookings need a confirmation call.

The Out-of-Play Statuses: Blocked and Out of Service

These two mean the table exists but isn't available. They're different, and the difference is time.

Blocked is a choice. You're closing a section because you're short-staffed. You're keeping the window tables free for walk-ins. You're setting up a private party at 7. Blocked is usually hours, and it usually ends the same night.

Blocking a section on purpose is often the smartest move a manager makes on a thin shift. Two waiters covering 12 tables badly is worse than two waiters covering 8 tables well. If your rota keeps producing those nights: restaurant employee scheduling.

Out of service is a fault. A wobbly leg, a broken chair, a dead radiator, a leak above it. It's measured in days, not hours, and it's your maintenance list. Any table sitting out of service for more than a week is either getting fixed this month or it isn't really a table — and you should know which.

Keeping these two apart gives you an honest seat count. "We have 96 seats" means nothing if 12 of them are under a dripping ceiling.

Who Sets What: The Ownership Rule

Statuses fail for one reason. Everybody can change them, so nobody does.

Fix it with a single rule: every status has exactly one owner and one trigger. Here's a mapping that works in most restaurants:

Status	Owner	Trigger
Vacant	Busser or waiter	Reset finished
Reserved	Host	Booking taken
Pending confirmation	Host	Booking not yet confirmed
Seated	Host	Party sits down
Occupied	System	First order sent
Bill requested	Waiter or guest	Guest asks or taps
Awaiting payment	System	Bill printed or sent
Needs cleaning	System	Payment settles
No-show	Host	Grace window passes
Blocked	Manager	Manager's call
Out of service	Manager	Fault reported

Notice how many say "system". That's deliberate. Four of the eleven should never be tapped by a human, because they follow an event that's already recorded — an order going in, a bill printing, a payment landing. The fewer statuses your staff have to set by hand, the more you can trust the floor screen.

The ones humans do own are the ones only a human can see: someone sat down, someone wants the bill, this table's a mess, this table's broken.

Colour-Coding the Floor Screen

A floor plan works when a manager can read it from across the room without focusing. That means colour does the talking, and you use as few colours as you can get away with.

A layout that reads well:

Green — vacant. Ready to sell.
Blue — reserved and pending confirmation. Spoken for.
Amber — seated and occupied. In service, all good.
Yellow — bill requested and awaiting payment. Closing out, don't touch.
Purple — needs cleaning. Money on the floor. Go.
Grey — blocked and out of service. Not in play.
Red — no-show. Needs a decision.

Group the statuses into these seven colours rather than giving each of the eleven its own. Eleven colours is a paint chart, not a floor plan. And keep the same colours in every branch if you run more than one — a manager covering across town shouldn't have to relearn what purple means.

What Table Statuses Tell You After Service

Statuses aren't just for tonight. Timestamp them and they turn into the four numbers that actually explain your floor.

Table turnover rate = parties served ÷ tables, for a period. Ten tables serving 34 parties in a dinner service is 3.4 turns. Track it by day and by section — a section that consistently turns slower usually has a layout problem or a training problem, not a lazy waiter.

Dwell time = seated to payment settled. Your real one, not the one you assume.

Reset time = needs cleaning to vacant. The cheapest number to improve on this whole list.

RevPASH — revenue per available seat hour = revenue ÷ (seats × hours open). A 40-seat place open 5 hours doing $2,800 has a RevPASH of $14. It's the one metric that catches both empty seats and cheap ones, which is why it beats covers as a headline number.

Two of these numbers land in the weekly review naturally — here's the wider set worth checking: restaurant KPIs to check every Monday morning.

One warning. Chasing turnover on its own is how restaurants accidentally get worse. A faster turn is only a win when it comes from cutting the dead minutes — the wait for a bill, the wait for a reset, the wait for a host to notice. Cutting the meal itself just makes guests feel pushed out, and they don't come back. Pair turnover with average check so you can see if speed is costing you: how to increase your average ticket.

Status and Order Are Not the Same Thing

This trips people up constantly, so let's be blunt about it.

The table status describes the table. The order status describes the order. They move on different clocks.

A table can be occupied with the order already served — dessert's done, they're finishing wine.
A table can be needs cleaning while the order is still unpaid — a walkout, and you need to know.
A table can be awaiting payment while a second order is still preparing, if someone added a coffee at the last minute.

Anyone who tries to force these into one field ends up with a floor plan that lies. Keep them separate. The table tells you what to do with the room; the order tells you what to do with the food and the money.

Rolling This Out Without a Big Project

You don't need a new system to start. You need one shift and a bit of stubbornness.

Draw your floor on paper. Every table, with its number. Ten minutes.
Name the eleven statuses and post the list at the host stand and the pass.
Assign one owner per status using the table above. Say the names out loud in pre-shift.
Pick two to measure this week: reset time and bill-request-to-bill time. Just those two. Use a phone timer if you have nothing else.
Run one service. Note where the status was wrong and why. It'll usually be the same two spots.
Fix those two spots. Then keep going.

Most teams get the loop right within three or four shifts. The status that always takes longest to stick is "needs cleaning", because it depends on someone owning the reset rather than everyone half-owning it. Name that person every shift and the problem disappears.

If you're running several sites, use the same eleven names and the same colours everywhere. Different vocabulary per branch is how a good manager transfers in and spends a full week being useless — the same trap that shows up with menus and reporting across locations: multi-location restaurant problems.

Mistakes That Break Table Status Systems

Only three statuses. Free, taken, dirty. You lose every useful signal in the meal.
Treating empty as ready. The number one cause of a party being seated at a dirty table.
No grace window for no-shows. Hosts hold tables for 40 minutes because nobody told them the rule.
Holding reserved tables too early. Two hours of blocked seats for one 8 p.m. booking.
Manual statuses for automatic events. If a payment settling doesn't flip the table by itself, it won't get flipped.
Blocked and out of service mixed together. Now your seat count is fiction.
Statuses nobody looks at. If the floor screen isn't visible from the host stand and the pass, it's a form, not a tool.
Chasing turn time by rushing guests. Cut the dead minutes, never the meal.

FAQ

What are the standard restaurant table statuses? The full set is eleven: vacant, reserved, pending confirmation, seated, occupied, bill requested, awaiting payment, needs cleaning, no-show, blocked, and out of service. Seven of them form the normal service loop, and the other four cover bookings and tables that are out of play.

What's the difference between seated and occupied? Seated means the party is at the table but hasn't ordered yet. Occupied means the order is in and service is running. Splitting them is how you spot a table that's been sitting 10 minutes with no drink in front of it.

What does "needs cleaning" mean for a restaurant table? The guests have paid and left, but the table hasn't been cleared and reset. It's the most profitable status to shorten, because it's pure dead time. Aim for under 7 minutes from payment to a fully reset table.

How is table turnover rate calculated? Divide the number of parties served by the number of tables over the same period. Ten tables serving 34 parties in a dinner service means a turnover rate of 3.4. Track it by section and by day, not just as one restaurant-wide number.

How long should a table stay in "bill requested"? Under 3 minutes. The bill should be on the table within three minutes of the guest asking. This is the point where guests have mentally left, and long waits here hurt reviews more than almost anything else in service.

Who should change table statuses — the host or the waiter? Both, plus the system. Hosts own reserved, seated, and no-show. Waiters and bussers own bill requested and vacant. Managers own blocked and out of service. Occupied, awaiting payment, and needs cleaning should flip automatically off orders and payments.

Do I need table statuses for a small café? Even a 10-table café benefits from at least five: vacant, occupied, awaiting payment, needs cleaning, and out of service. The full eleven matter most once you take bookings or run more than one section.

What's the difference between a blocked table and one out of service? Blocked is a deliberate choice for a few hours — short staff, a private party, holding walk-in space. Out of service is a fault that lasts days and belongs on the maintenance list. Keeping them apart is the only way your seat count stays honest.

How do QR menus change table statuses? They let the guest trigger some of them. A guest can request the bill from their phone, so "bill requested" arrives without anyone flagging down a waiter. When the QR code is bound to a specific table, orders and payments also attach to the right table automatically.

What is RevPASH? Revenue per available seat hour — revenue divided by seats multiplied by hours open. A 40-seat restaurant open five hours taking $2,800 has a RevPASH of $14. It's the best single measure of whether your floor is working, because it catches both empty seats and low-spend ones.

Table statuses look like a small operational detail. They're really a shared language for the floor — one word per table that tells the host, the waiter, the busser, and the manager the same thing at the same time.

Try this before your next busy service. Time two things: how long a table sits between payment and reset, and how long a guest waits between asking for the bill and getting it. Whatever those two numbers turn out to be, cutting each of them in half is worth more than any new marketing idea you'll try this month — and it costs nothing but attention.