How Many Buffet Counters for 500 to 1,000 Wedding Guests? The Serving-Time Maths
Ten counters for a thousand guests is the usual advice, but the number that decides whether dinner runs smoothly is minutes at the counter, not counters. A worked method for 500 and 1,000 guests, with the assumptions to challenge your caterer on.

Ask three Bangalore caterers how many counters a 1,000-guest wedding needs and you will hear eight, ten and fourteen. All three can be right, because the count depends on how long each guest spends at a counter and how many guests want food in the same hour. Neither of those figures appears on a quotation.
This is the arithmetic a family can do on the back of an invitation card before the tasting. It will not replace your caterer's own numbers, but it tells you which of their numbers to question.
The problem is a peak, not a headcount
Dinner at a large wedding does not start evenly. Once the stage programme reaches a natural pause, or the announcement goes out that dinner is open, a large share of the room stands up at once. In our guest flow piece we looked at the same effect at the gate: most guests arrive inside one hour. Food has the same shape, only tighter.
A working assumption for planning is that 60 to 70% of guests go to eat in the first hour after dinner opens. For 500 guests that is 300 to 350 people. For 1,000 it is 600 to 700. The rest come later, or graze on starters, or are on the dance floor and will eat at eleven.
Plan for the first hour. If the counters cope with that hour, the second hour looks after itself.
Minutes at the counter decide everything
The method takes three inputs and one division.
- Guests eating in the peak hour. From above: 650 for a 1,000-guest wedding.
- Minutes each guest occupies a position at the counter. Filling a plate from a spread of eight or nine main-course dishes takes about two to three minutes, longer if there are elders being helped or children being negotiated with.
- Positions per counter. A table that guests can approach from both sides gives roughly eight positions on a 12 ft run. A single-sided table of the same length gives four.
Then: guests per minute needed, multiplied by minutes per guest, divided by positions per counter.
For 1,000 guests: 650 guests over 60 minutes is about 11 guests a minute. At 2.5 minutes each, that is 27 positions in use at any moment. At 8 positions per double-sided counter, you need 3.4 main-course counters, so four.
For 500 guests: 325 over 60 minutes is about 5.4 a minute, 13.5 positions in use, 1.7 counters, so two.
Those numbers surprise people, because they are well below the ten counters usually quoted. The gap is explained by what else the ten has to cover.
What the other six counters are for
A thousand-guest dinner is several meals running at once, and each needs a separate queue. Putting them on one table is how a line of 80 people forms in front of the paneer.
| Counter type | Why it is separate | Typical count at 1,000 guests |
|---|---|---|
| Main course (rice, breads, curries) | Longest time per guest, heaviest plates | 4 |
| Starters | Eaten standing, early, before dinner opens | 2 |
| Live counters (dosa, chaat, pasta, tandoor) | Made to order, so slowest per guest | 2 to 4 |
| Desserts | Second trip, mostly later in the evening | 1 or 2 |
| Beverages and water | Quick, but blocks lanes if placed on the main axis | 1 |
That adds up to ten to thirteen, and it is why ten is a reasonable figure for 1,000 and a lazy one for 500. At 500 guests the same table gives you two main, one or two starter, two live, one dessert and one beverage station, so seven or eight.
Splitting them has a practical purpose. A dessert queue and a main-course queue are made of the same people at different times. If they share a table, the desserts get rushed in at the exact minute the main course is jammed.
Live counters are the bottleneck
A made-to-order counter is the slowest thing in the room. One chef making dosas or tossing pasta turns out something like 40 to 60 plates an hour, depending on the dish. A chaat counter with two people moves faster; a tandoor with fresh bread that must go straight to the guest slows everything down.
So if 40% of your 650 peak-hour guests go to live counters, that is 260 plates in the hour. At 50 plates per chef per hour, you need five or six chefs. Two chefs per counter gives three counters.
The common mistake is to book one impressive live counter, a dosa station perhaps, and expect it to serve a quarter of the room. At 50 plates an hour it serves 50 people. The queue that forms there is the one guests photograph for the wrong reasons.
Two rules that work in practice. Never let a live counter carry the dish everyone wants without a buffet version of the same thing elsewhere. And put live counters where queues can form away from the dining area, which the guest flow article covers as the buffet-placement problem.
Refill is a second system
Counters do not run out of space; they run out of food at the wrong moment. A chafing dish that holds enough for 60 plates will be half empty after 30 guests have passed, and the replacement has to arrive hot, in a trolley, through a lane that does not cross the queue.
Ask your venue and caterer for the following, specifically.
- A service lane behind the counters, separate from the guest side.
- Where the staging kitchen sits relative to the farthest counter. Every extra 30 seconds of carrying adds up across hundreds of refills.
- Who watches the dishes. One captain per two or three counters is a working ratio.
- What the policy is when a main dish runs low: top up, or swap a dish. Empty trays with a queue in front of them damage the evening more than a missing dish.
The sit-down lunch is a different calculation
Many Karnataka and South Indian weddings serve a traditional lunch on banana leaf, seated in rows, in batches. The counter maths disappears and a different one takes over.
A batch sits, is served, eats and leaves. Allow 25 to 30 minutes per sitting including clearing and resetting. If a hall seats 150 per sitting, 1,000 guests take seven sittings, about three hours. If you can seat 300 per sitting across two halls or a hall plus a covered lawn, it is four sittings and a little over two hours.
For this format, ask how many guests can sit at once, how many servers work each row, and where families wait. People who are fed in the order they arrive are happy. People who are told "next batch in 40 minutes" at 2 pm in Bangalore sun are not.
What to do with the number
By now you have a rough count for your format. Three decisions follow from it.
Suppose the venue offers fewer counters than you need. Either the caterer adds counters, which costs more food stations and staff, or you stagger the opening. A quick fix that works: open starters and live counters before the stage programme ends, so the main-course peak is smaller by the time it begins.
Guest mix changes the answer too. A wedding with many elders wants more seated service and fewer queues. A wedding with many young families wants more live counters and a clear kids' area. Our 500-guest hall size article and the 1,000-guest version show how to size the floor for either mix.
Finally, check the room. Counters need queue room in front of them as well as footprint. Our large-scale wedding venue checklist lists the other things to confirm before you commit, including washrooms and the wet-weather plan. For a wider view of which venue formats suit which guest bands across North Bengaluru, the guide to wedding venues by guest count sets them side by side.
Send us your guest count and food formatA note on Le Roma Gardenia
Le Roma Gardenia, at Hesaraghatta in North Bengaluru, is an upcoming resort and is not open or taking bookings yet. The articles on this site that discuss it describe plans and published layouts, not a venue you can book today. You can register interest and ask the team how large-format dining will be planned when the resort opens.
If you are shortlisting venues now, use the method above on any of them. A venue that can tell you its counter positions, service lanes and staging kitchen location has done this calculation before. One that answers "we manage 1,000 guests all the time" has not.
Questions to take to a tasting
- How many guests do you plan to serve in the first hour after dinner opens, and what is that as plates per minute?
- How many counters of each type, and which are double-sided?
- How many chefs on each live counter, and what is the plates-per-hour for each dish?
- Are the same dishes repeated across counters?
- Where is the staging kitchen, and which lane do refills take?
- Who is the counter captain, and what is the swap policy when a dish runs out?
- If the dinner opens late, what happens to the hot-holding?
- For a seated lunch, how many sittings, and where do waiting guests stand?
Working out food service for a large wedding?
Share your guest count, whether dinner is buffet or seated, and your preferred date. We will talk through counters, queues and timing against your numbers, and tell you honestly where the format needs to change.
Related reads:
- Guest Flow at a 1,000-Guest Wedding: Entry, Seating and Parking That Doesn't Jam →
- Banquet Hall Size for 500 Guests →
- Banquet Hall Size for 1,000 Guests: The Sq Ft, Seating and Parking Math →
- Planning a Large-Scale Wedding: A Venue Checklist for 1,000+ Guests →
- Kalyana Mantapa vs Banquet Hall vs Resort Lawn →