In this article
Your dining room can seat 50 covers an hour at full turn. Your kitchen might only be able to cook for 33 of them — and nobody ever multiplied the numbers that would have shown it in advance.
Owners obsess over floor capacity: table mix, turn times, RevPASH, no-shows. All of it floor-side. Meanwhile the kitchen has its own hard ceiling, and it almost never gets a number.
Ask a kitchen to cook for more covers an hour than it physically can, and the room doesn't get "busier" — tickets back up, plates arrive slower, quality slips, and the floor staff take the blame for something the dining room never caused.
The good news: your kitchen's ceiling is just arithmetic — cooks × available minutes ÷ how long a dish takes at the bottleneck station. Once it's a number, you can plan bookings, staffing and menu design against it, instead of discovering it live during Saturday's rush.
This article walks through the seven numbers that make up that ceiling, with a live calculator at the end that runs on your own kitchen's stations.
Why the dining room's own number isn't the whole story
Reservation systems, table plans and covers forecasts are all built around the ROOM: how many seats, how fast they turn. Necessary, but it silently assumes the kitchen can always keep up with whatever the room can seat.
A kitchen doesn't fail gracefully when it's asked to do more than it can. It doesn't say no — it just gets slower, on every ticket, for everyone, at once. A guest waiting forty minutes for a main blames the service, not the maths that put them there.
The fix isn't "hire more staff" or "cook faster" in the abstract — it's knowing, station by station, which one actually sets the ceiling, and by how much.
The 7 numbers behind your kitchen's real ceiling
Work through these in order — each one builds on the last, and together they tell you exactly how many covers an hour your kitchen can serve, not how many your dining room can seat.
1. The two ceilings
Every restaurant has two separate capacity ceilings, and usually only one of them gets a number. The floor's ceiling is seats × how many times they turn in an hour — familiar territory, already covered by every table-turnover and peak-hour article on this site. The kitchen's ceiling is different: it's set by whichever station can push out the fewest dishes an hour, and it is very often the smaller of the two numbers.
A restaurant can never actually serve more covers per hour than the SMALLER of these two ceilings — obvious once you say it, and exactly why almost nobody has ever written both numbers down side by side.
2. Ticket time — the number nobody times
Ticket time is how many minutes a dish is actively being worked at its station, from the ticket landing to the plate leaving for the pass. Not the whole visit, not how long the guest waits for their course — the station's own hands-on minutes.
Time it during a real service (a phone stopwatch and a clipboard is enough): most kitchens have never measured this station by station, and the number is almost always higher than the head chef's gut estimate, because it never accounts for the ticket that comes in wrong, the last-minute substitution, or the six that land within the same ninety seconds.
3. Station capacity — the smallest number wins
Multiply the cooks at a station by the minutes available in an hour, divide by that station's ticket time, and you get dishes per hour. Divide that by the share of your covers that actually order from that station (not every guest orders a starter or a dessert — that share matters), and you get COVERS per hour that station can support.
Do this for every station, and the kitchen's ceiling is simply the SMALLEST of them — one slow or short-staffed station caps the whole kitchen, no matter how fast the others are running. In the worked example below, cold has room to spare (36.4 covers/hr), fry has even more (37.5), but hot only manages 32.7 — and that number is the real ceiling, not the average of the four.
Covers per hour each station can support, at the ticket time and attach rate above. The shortest bar sets the whole kitchen's ceiling.
Figures from the worked kitchen above — plug in your own stations in the calculator further down to see your own ceiling.
4. The floor ceiling, recomputed
The floor side is simpler and usually already known: seats × (60 ÷ average minutes a table occupies, including reset time) = covers per hour, at full house. Sixty seats with a 72-minute turn give exactly 50 covers an hour.
It is almost always the rounder, bigger-looking number of the two, for one simple reason: dining rooms get designed around square metres and covers targets; kitchens get staffed around a wage budget — the two get planned by different people, at different times, against different numbers.
5. The gap — your phantom seats
Subtract the kitchen's ceiling from the floor's and you get the number that actually matters: covers the room can physically seat that the kitchen cannot physically cook for in that same hour. In the worked example below that's 50 minus 32.7, or 17.3 covers an hour. Call them phantom seats — filled on the reservation sheet, invisible on the pass.
They don't show up as empty tables or turned-away guests; they show up as every ticket running late, at once, for the whole room, at exactly the moment it costs you the most.
The floor's ceiling (grey) against the kitchen's ceiling (amber). The hatched section is what the room can seat that the kitchen cannot cook for.
The green line is the safe booking pace — roughly 85% of the kitchen's ceiling — so one bad ticket doesn't drag down the whole service.
6. The cushion — why 100% is already too much
A kitchen running AT its ceiling — not over it, exactly at it — already has no room left to absorb the one thing that always happens: a dish sent back, an ingredient that runs out, a table of twelve landing mid-service. There's no slack to catch it, so one hiccup cascades into every ticket behind it.
This is why this model's own recommendation is to pace bookings against roughly 85% of the kitchen's ceiling for a sustained rush, not the full number — in the worked example below that's 27.8 rather than 32.7 covers an hour. The 15% you leave on the table is what keeps one bad ticket from becoming a bad service.
7. What actually raises the ceiling
There are exactly two levers on a bottleneck station: shave its ticket time, or add a position to it. Either one raises the kitchen's ceiling — but only up to whatever the NEXT-tightest station allows. Shave a minute off the hot station's ticket time in the worked example below, or add a fourth cook to it, and the ceiling doesn't jump to 40 — it rises to 34.3, because dessert now takes over as the bottleneck. You buy back 1.6 covers an hour, not 7 or 8.
Fix the bottleneck without checking what's behind it, and you'll spend real money buying back a smaller number than you expected. This is also the number worth pacing your reservation system against, rather than however many seats the room can physically hold — a system that books to the floor's ceiling books the kitchen into a wall it can't see.
What's your kitchen's real ceiling?
Fill in the cooks, ticket time and attach rate per station for your own kitchen, plus your dining room's seats and turn time. Everything below recomputes live.
The starting values describe a mid-sized brasserie with four stations — adjust them to your own venue to see where your real ceiling sits.
What's your kitchen's real ceiling?
Fill in your own stations and dining room — everything below recomputes live.
—
A model, not a rule: ticket time and attach rate differ by kitchen and by dish. Measure your own figures for the best result.
Remember: fixing the bottleneck station never lifts the ceiling all the way to what that station alone would suggest — the next-tightest station takes over immediately. Always recompute the whole row, not just the one station you just fixed.
And pace your bookings against the safe rate above, not the full ceiling — that's exactly the margin that absorbs one bad ticket without dragging down the whole service.
The number worth writing down
Most kitchens have never had a ceiling — they had a feeling, built up over years of busy Fridays that came out just fine or just short. Now you have a number, and a way to see which station sets it.
That number doesn't change how you cook. It changes how much you book, how you staff your stations, and which dish you might pull off the menu right before the weekend you can't actually keep up with it.
Run the numbers once for your own kitchen. Next time the room is full and tickets are backing up, you'll know instantly whether it's the floor, or the station you could already see coming.