One Seating or Two at Dinner? The Revenue-vs-Experience Call That Defines Your Floor

There’s a choice that defines a restaurant’s character more than almost any other: at dinner, do you seat each table once and give the guests the whole evening, or do you run two seatings, handing the same table to two different parties? In the US and much of the world, double and triple turns are standard practice — nobody blinks at a 6:30 and an 8:45 on the same four-top. So this isn’t a question of principle. It’s a revenue-versus-experience tradeoff, and the answer isn’t obvious — and it’s not the same for everyone.

The two philosophies

The single seating gives the table to one party for the night. A booking at 8:00, and the table is theirs. No one rushes them, the check tends to climb (more courses, more wine, coffee, a digestif), the mood is unhurried. It’s the relaxed-hospitality model, and for many venues it’s part of their identity: “here, you take your time.”

The double seating schedules two bookings on the same table: one at 6:30, one at 8:45. It doubles potential covers — and therefore revenue — on high-demand nights. But it demands rhythm, precision and, crucially, flawless communication, because the first table has to clear in time for the second.

The temptation is to assume the double seating “always earns more.” It doesn’t. And the way to know is a metric.

RevPASH: the honest way to compare them

Comparing one seating to two by counting covers alone is misleading, because it ignores two things: how much each table spends and how long it stays. The metric that settles the argument is RevPASH — Revenue Per Available Seat-Hour, the revenue earned per seat for each hour of service. It’s the standard from the Cornell School of Hotel Administration, designed precisely to compare different floor models. (Quick definition in the RevPASH glossary entry.)

The calculation is simple:

RevPASH = night’s revenue ÷ (number of seats × service hours)

Why is it honest? Because it accounts for both covers and time. A single seating with a $70 check that holds the table for 3 hours can have the same RevPASH as two seatings of $40 each. In that case, the double seating gives you more work, more kitchen stress and more risk of friction with guests… for the same hourly revenue. Not worth it.

Try the calculator below: plug in your seats, average check and average dwell time, and compare the revenue of one seating against two at a glance.

When one seating wins

The single seating is the right call when:

• The check is high. Tasting menu, a serious wine list, a long experience: here the value per table is such that squeezing in a second turn adds little and kills the atmosphere.
• The experience is the product. If you sell an evening, not a meal, rushing contradicts the promise. Service becomes hospitality precisely in the time you grant.
• Demand doesn’t fill the room anyway. If you don’t even fill one seating, the double turn is a non-problem: focus first on filling your quiet nights.
• Your crowd rejects being hurried. Knowing your guests is decisive: a crowd that returns because they’re never shown the door is an asset to protect.

When two seatings win

The double seating makes sense when:

• Demand exceeds your seats. If you turn away bookings every Saturday, you’re leaving revenue on the table. The second seating captures demand you’d otherwise lose — and there’s real money in that empty table.
• The check is mid-range and the meal is naturally shorter. Bistro, trattoria, quality-but-quick formats where 90 minutes is already a complete experience.
• The kitchen can handle the rhythm. Two concentrated waves stress the brigade: it takes organization, good FOH–BOH communication and solid pacing.
• You can communicate the limit. And here we reach the point that decides everything.

If you’ve gone with the double seating, the numbers behind it mean mastering your table turnover rate and the levers that raise covers.

The real bottleneck isn’t the math — it’s communication

Here’s the truth many discover too late: the double seating doesn’t break on the numbers, it breaks on communication. The RevPASH calculation tells you whether it’s worth it; but if the first table doesn’t clear in time, the whole model collapses — and with it the calm of the night, because you end up having to ask a guest to free the table at the last minute.

The solution is the same one that runs through all of table-time management: set the expectation at booking. If you communicate the time limit as a guarantee — “the table is yours until 9:15” — the second seating isn’t experienced as a rush. The first guest knows their window from the start; the second finds the table ready. Nobody feels pushed. The double seating works when the guest doesn’t even notice it exists.

This is exactly why double seatings sometimes get a bad reputation: not because the model is wrong, but because it’s often applied without communicating the window, which turns into guests shown the door by surprise. Done with the right communication, it’s perfectly compatible with warm hospitality — the packed bistro that turns twice a night has done it for decades without anyone feeling mistreated.

The choice isn’t binary

Worth saying: you don’t have to choose once and for all. Many restaurants run a hybrid model: single seating on quiet nights and on big tables (where the check is generous), double seating on Friday and Saturday for two- and four-tops. The question isn’t “am I a one-seating or two-seating restaurant,” but “tonight, on this table, is one seating or two the better call?”. Your turnover and per-slot check data tell you where to draw the line.

Mistakes to avoid

Choosing the double seating by looking only at covers. Without RevPASH you risk doubling the work for the same revenue. Run the real math.

Applying the double seating without communicating the limit. It’s the error that makes guests feel rushed and breeds bad reviews. The window must be stated at booking, every time.

Forcing a single seating even when you’re turning bookings away. If you send guests off every Saturday, you’re giving away revenue: consider the second seating at least on the small tables.

Stressing the kitchen without preparing it. Two concentrated waves require organization and pacing, not improvisation.

The bottom line

One seating or two isn’t a matter of principle — it’s a matter of numbers and communication. RevPASH tells you honestly whether the second seating adds real revenue or just more effort; often a single seating with a high check holds its own. And when the double seating does win, it only works if you communicate the time limit as a guarantee, up front, so the guest never feels the rush. The math decides whether to do it. The communication decides whether it works.

The scripts for communicating the seating window are in the Floor Scripts Kit below.

Coperti calculates your real turnover and check size by slot and lets you run one or two seatings on the same table with the time windows already communicated in confirmations, so the second seating never becomes a rush. Explore the features or tell us about your venue for a demo.