In this article

• Turnover is not about rushing anyone

• The two settings behind every full night

• Pacing: how many parties land in the same 15 minutes

• Turn time: how long a table is actually held

• One number does not fit every table in the room

• The holiday problem nobody budgets time for

• What pacing cannot fix

• Where Peblla fits — and where it does not

• Frequently asked questions

Turnover Is Not About Rushing Anyone

Ask ten owners how to improve table turnover and most will describe some version of moving faster. Drop checks earlier. Push the servers. Clear plates the moment the last fork goes down. It feels like the only lever available, and it is the one that guests notice first — usually as the reason they will not come back.

The uncomfortable part is that speed at the table is the smallest of the three factors. A room that seats twelve parties between seven and eight will feel frantic no matter how relaxed the service is. A room that seats four will feel dead even if every server is excellent. What decides the difference happened hours earlier, in a settings screen almost nobody opens.

Two numbers govern how many covers a dining room can physically do in a night. Most restaurants inherited both from whoever set up their booking tool, have never changed them, and could not say what they are set to right now.

The Two Settings Behind Every Full Night

The first is pacing: how many parties you allow to book into the same slice of time. The second is turn time: how long a table stays assigned to a party before the system offers it to someone else.

Together they draw the ceiling. Pacing decides whether arrivals come in a wave or a stream. Turn time decides how often that stream refreshes. Everything the floor experiences on a Friday — whether the kitchen keeps up, whether the host stand has a line, whether tables sit empty at nine — is downstream of those two values.

The reason they get ignored is that they are invisible when they are wrong. A kitchen buried at 7:15 reads as a staffing problem. Empty two-tops at 8:40 read as a demand problem. Neither owner goes looking in the reservation settings, because nothing on the floor points there.

Pacing: How Many Parties Land in the Same 15 Minutes

Pacing is usually expressed as a cap per interval — four parties per fifteen minutes, say. It sounds like a small technical detail. It is the single most direct control you have over whether your kitchen has a good night.

Set it too high and you have built a wave. Twelve tables order appetizers inside the same ten minutes, the line backs up, tickets age, and every one of those parties waits longer than they should for food they will remember as slow. Set it too low and the dining room protects the kitchen at the cost of the business — tables sit open at prime time while people who wanted to eat with you went somewhere else.

The right number is not universal. A bubble tea counter can absorb a wave a full-service steakhouse cannot; a taqueria firing off a plancha sits somewhere between. It depends on how many hands are on the line, how much of the menu is fired to order, and how long your slowest dish takes. A kitchen running a kitchen display system with clear station routing can absorb a heavier wave than one working off a printer, because tickets get distributed instead of stacked.

The practical approach is to start conservative and raise it. Move the cap up by one party per interval, work a full weekend at that setting, and watch ticket times rather than covers. The moment average ticket time climbs past what your guests tolerate, you have found the ceiling. That number is worth more than any advice an article can give you, because it is measured in your kitchen.

Turn Time: How Long a Table Is Actually Held

Turn time is the block of time a reservation occupies a table. Ninety minutes is the common default for a standard dinner table. Most rooms never revisit it.

The cost of getting it wrong runs in both directions. Set it too short and you double-book yourself into an apology: the eight o'clock party is standing at the host stand while the six-thirty party is still on dessert. Set it too long and you throw away a turn — the table cleared at 8:20 but the system is still holding it until nine, so nobody could book it and nobody was seated in it.

The honest way to find yours is to stop guessing and read your own history. A pizzeria two-top and a Korean BBQ four-top are not the same seating, and neither is a bakery cafe table at eleven in the morning. Look at what your tables actually do on a normal Saturday, by party size. Two-tops and six-tops rarely behave the same way, and the gap between them is often thirty minutes or more.

One Number Does Not Fit Every Table in the Room

This is where a single global setting starts to hurt. A dining room is not one kind of seat.

A private room sold for a birthday is not a ninety-minute table and never was. Neither is a grill table where the cooking happens in front of the guest, or a counter built around a longer tasting format. Forcing all of them onto one turn time means either the fast tables are held too long or the slow ones are offered to a party that cannot possibly be seated on time.

Table types solve this by letting each kind of seat carry its own clock. A room that runs 150 minutes stops being offered like a 90-minute two-top. Restaurants with grill tables and private rooms feel this immediately, because their room mixes formats that have no business sharing a setting.

It also changes what a guest can do at the moment of booking. Some guests want to choose the space — a room, a booth, a counter seat — and will look at photos before they commit. Others only want to say four people at seven and let the system find something appropriate. Supporting both means you stop losing the guest who does not fit the path you built.

The Holiday Problem Nobody Budgets Time For

Valentine's Day is not a normal Friday. Mother's Day is not a normal Sunday. Every operator knows this, and most handle it the same way: change pacing and turn time, work the holiday, then remember to change everything back.

The remembering is where it breaks. The setting gets left in holiday mode, and for three weeks the dining room runs at a pace built for one abnormal night. Nobody notices, because a slightly wrong pacing number does not announce itself.

Most reservation tools let you scope a schedule to a date range, which means you can build one that lands on February 14 alone — tighter turn times, a different cap per interval, a fixed menu window if you run one. What it does not spare you is the schedule that normally covers that night. A Korean BBQ room on a standing Friday-to-Sunday rule still has to work around it, and a pizzeria closing for Thanksgiving still takes that day out by hand.

Treat it as part of holiday prep, not a setting that manages itself. Write down what you changed and the date you are changing it back, on the same calendar where you schedule staff. A pacing number left wrong for three weeks costs more covers than the holiday brought in.

What Pacing Cannot Fix

Two settings will not save a room with the wrong staffing. If you are one server short on a Friday, correct pacing only spreads the shortfall more evenly. Scheduling is its own discipline, and shift management deserves the same attention you give the dining room.

They also will not fix a table that has been cleared but never released. If a party leaves at 8:20 and the floor does not mark it, the system believes the table is still occupied. Every minute after that is a turn nobody could book. This is why status changes need to be one tap where the server already is — on a handheld rather than a walk back to a terminal.

And they will not make a slow night busy. Pacing shapes demand you already have. Filling the room in the first place is a different job, closer to what an ordering tablet does for check average than to anything in a reservation setting.

Where Peblla Fits — and Where It Does Not

Peblla Table lets you set pacing and turn time yourself, per table type, with separate arrangements for specific dates. Because bookings and service run on the same platform as the POS, seating a party opens the check with the guest already attached, and the table's real status is what the booking calendar reads from.

It is not the right answer for everyone. If your priority is maximum discovery on a public dining marketplace, that is a different category of product and we are not that. If you run a counter-service room where nobody books ahead, pacing is not your constraint and this will not help you. And if your floor does not update table status during service, no reservation system will read your room correctly — that habit has to come first.

What it does do is make the two numbers visible and adjustable by the person who actually knows the room. More on the reasoning behind that on why restaurants choose Peblla.

Frequently Asked Questions

What is a good table turnover rate for a restaurant?

There is no single benchmark worth chasing. A casual room might turn a two-top three times in a dinner service; a tasting-format restaurant may turn once and be more profitable. The useful measure is whether your tables sit empty at prime time, not how your rate compares to somebody else's format.

How do I know if my turn time is set wrong?

Two symptoms. If parties regularly wait at the host stand while the previous table is still seated, it is too short. If tables sit visibly empty during your busiest hour while the booking calendar shows no availability, it is too long. Both are settings problems, not service problems.

Should every table have the same turn time?

No. Party size and table format both change how long a seating runs. Private rooms, grill tables and counter seats behave differently from a standard two-top, and giving each its own clock is usually the single biggest improvement available.

How many reservations should I accept per 15 minutes?

Enough that your kitchen's ticket times stay where you want them, and no more. Raise the cap one party at a time, work a full weekend, and watch ticket times rather than cover counts. The setting where ticket times start climbing is your ceiling.

Do I have to change my settings back after a holiday?

Usually yes, and that is the part operators forget. If you widened pacing or shortened turn times for one night, put the reset on your calendar the same day you make the change. A dining room left running holiday numbers for three weeks quietly loses more covers than the one busy night ever brought in.

Does changing pacing affect walk-in guests?

Yes, indirectly. Every seat committed to a booking is a seat unavailable to someone at the door. Deciding how much of the room to leave open for walk-ins is a business choice, and it should be a deliberate one rather than a side effect of a default setting.

If you want to see what your two numbers are doing to your Friday, book a walkthrough and we will look at your room with you.