Key takeaways
- Cap online bookings at the largest table you can seat without rearranging the room or the kitchen’s plan, often six or eight.
- Large parties are not the main no-show risk: tables of ten or more had the lowest recorded rate in platform data, 1.15%[1]. The risk is what each failure costs.
- Above the cap, send guests to a short enquiry form with a reply promised within hours, not a “no availability” message.
- Agree deposits, pre-orders and final-number deadlines in writing before the date.
Why cap online party size at all
An online widget is brilliant for tables of two and four. It shows real availability, takes the details and confirms in seconds. It is much worse at a table of twelve. A large party needs tables joined, a section set aside, a menu decision, often a deposit and a conversation about timing. Left to the widget, it lands in the diary as a single booking that quietly blocks a quarter of the room at 19.30 and gives the kitchen ten mains to fire together.
A party size cap is the line where self-service stops and a conversation starts. Set it right, and small bookings stay quick while large ones get the attention that makes them work, for the guest and for you.
What the data says about big tables
Large groups are more reliable than many operators expect. In the Resos No-Show Index, which covers about 3.8 million reservations, tables of one to two had the highest recorded no-show rate, at 2.63%. The rate fell with party size, to 1.73% for seven to nine and 1.15% for ten or more[1].
Source: Resos, 2026[1]
Show the data
| Item | Value |
|---|---|
| 1 to 2 | 2.63% |
| 3 to 4 | 2.13% |
| 5 to 6 | 2.28% |
| 7 to 9 | 1.73% |
| 10+ | 1.15% |
The catch is the size of each failure. When a table of twelve fails to arrive, twelve covers go with it, and often a section of the room that could have taken three other bookings. Operators feel that knock-on effect: in OpenTable’s research, 60% of restaurant operators said no-shows had led them to turn away other bookings[2]. The reason to cap online party size is control, not mistrust.
Choosing your cap
| Venue | Suggested online cap | Reason |
|---|---|---|
| Small café or bistro under 40 covers | 4 to 6 | A table of eight takes a large share of the room |
| Neighbourhood restaurant, 40 to 80 covers | 6 to 8 | Joined tables need planning; kitchen timing matters |
| Large restaurant or food-led pub | 8 to 10 | More flexible room, but groups still need a menu plan |
| Venue with a private room | Room bookings by enquiry only | The room has its own minimums and terms |
| Tasting-menu or counter venue | 4 | Fixed seats and one menu pace |
| Peak dates such as December | Lower than usual | Groups book early and need set menus |
Look at your floor plan and your kitchen before you pick a number, not at what competitors allow. Two quick tests help. First, what is the biggest table you can seat without moving other bookings? Second, what is the biggest order your kitchen can fire together at peak without slowing other tables? Your online cap should be the smaller of the two. Set the cap separately for busy and quiet times if your booking system allows it; a table of eight at 18.00 on a Tuesday is easy, the same table at 19.30 on a Saturday is not.
Above the cap: an enquiry route that converts
Show the route, not a dead end
When a guest selects a party above the cap, the widget should say “For groups of 9 or more, tell us a bit more and we’ll come back to you today”, with a short form or a phone number.
Keep the form short
Ask only for what you need to reply: date, preferred time, number of guests, occasion, name, mobile and email, and any dietary needs.
Reply fast
Groups often ask several venues at once. Aim to reply within a few hours in opening times, with available times and the group terms.
Hold the date provisionally
Pencil the space in the diary when you reply, so it is not sold while the organiser decides. Release it if there is no answer by an agreed time.
Confirm in writing
Once agreed, send a confirmation with the menu, deposit, final-numbers deadline and what happens if numbers fall.
Group enquiries often arrive by phone in the evening, when staff are busiest. Ava, an AI employee, can capture private-dining and party enquiries on those calls and pass them to the right person, so the organiser gets a reply before they book elsewhere.
What to ask in the group enquiry
- Date, preferred time and how flexible they are.
- Number of adults and children, and how firm the number is.
- Occasion: birthday, work gathering, wake, celebration.
- Dietary needs and allergies across the group.
- Access needs, including step-free access or space for a wheelchair.
- Whether they want a set menu, a pre-order or to order on the night.
- Budget expectations, if they want to share them.
- Who the main contact is, and the best way to reach them.
Most of these can be optional, apart from date, time, numbers and contact details. Use the answers to suggest the right format. A work lunch for twelve with a fixed end time suits a set menu. A family birthday for sixteen with children suits sharing dishes and an early start. Offering the right format is what turns an enquiry into a booking.
Terms for large groups
Large bookings deserve clear, fair terms, agreed before the date. Keep them proportionate to the loss you would face, and put them in the confirmation. A common set looks like this:
- A deposit per head, deducted from the final bill, with a clear cancellation window.
- Final numbers by a set time, such as 48 hours before, with a small reduction allowed without charge.
- A pre-order or set menu for parties above a size you choose, so the kitchen can prepare.
- Any discretionary service charge for large tables shown on the menu and the confirmation in advance.
- An arrival window, and what happens if the group is late, given the effect on other tables.
Size matters for safety too. Very large events can bring new duties: under Martyn’s Law, premises where at least 200 people may be present are in scope[3]. Most restaurant bookings are nowhere near that, but venues hosting large parties, private hire or events should check whether the rules apply to them.
December and other peak dates
Group demand peaks in late November and December, when work parties and family gatherings compete for the same Friday and Saturday evenings. Lower the online cap for those weeks, so every large booking comes through the enquiry route with a set menu and a deposit. Publish the party packages early, with clear dates for numbers and pre-orders, and give each enquiry a reference so the organiser can come back to the same conversation. A December table of fourteen booked through the widget with no menu, no deposit and no named contact is the booking most likely to go wrong on the busiest night of your year.
Example: a 70-cover restaurant sets a cap of eight
Example. A fictional 70-cover restaurant has no online limit. On Saturdays, two or three tables of ten or more appear in the diary each month, booked at 19.30, with no menu agreed. The kitchen struggles, and other tables wait. The owner sets an online cap of eight, with an enquiry form for larger groups. Groups now get a reply the same day offering 18.30 or 20.30 and a sharing menu with a deposit. Large tables still come in, but at the edges of the evening, with the menu agreed. Saturday ticket times improve, and the restaurant has a list of group organisers to thank and invite back.
Mistakes to avoid
- A cap that sends guests to “no availability” with no other route.
- An enquiry form that nobody checks until the next morning.
- Different caps on different channels, so groups book through a platform that allows twelve.
- Groups split into two bookings of six to get round the cap, which the diary then seats apart. Watch for this and call the organiser.
- Terms for groups that only appear after the deposit is paid.
- Treating every enquiry the same, when a work lunch and a christening need different menus, timings and tables.
Group bookings are among the most valuable a venue takes, and the most likely to come back as repeat events. They are also the easiest to lose to a slow reply. The cap is there to make sure each one gets a person’s attention. The market for events is a substantial one: there were 9,995 event catering enterprises in the UK in 2026[4], many of them competing for the same celebrations and work dos.
Frequently asked questions
What should the maximum party size be for online restaurant bookings?
The smaller of the biggest table you can seat without moving other bookings and the biggest order your kitchen can fire together at peak. For many venues that is six to eight.
Are large groups more likely to no-show?
Not in the Resos index. Tables of ten or more had the lowest recorded no-show rate, 1.15%, but each failure costs more covers[1].
How should we handle group bookings above the online limit?
Send them to a short enquiry form or a phone number, reply within hours, hold the date provisionally and confirm menu, deposit and final numbers in writing.
Should large groups pay a deposit?
Many venues take a deposit per head for large groups, deducted from the bill. Keep it proportionate and show the terms before the guest pays.
References
Resos (2026). Restaurant no-show rate: the Resos No-Show Index (opens in a new tab) ↑
Restaurant Online (2026). No-show rates fall year-on-year, report finds (OpenTable Restaurant Impact Report) (opens in a new tab) ↑
Home Office (2025). Martyn's Law factsheet (opens in a new tab) ↑
Office for National Statistics (2026). UK business: activity, size and location, 2026 (workbook) (opens in a new tab) ↑