A Chennai banquet kitchen can receive a function sheet marked “200 guests” and still be missing the number it needs. Is that the minimum being billed, the host’s latest estimate, the number confirmed for dinner or the capacity the kitchen has promised to serve?
Those figures may coincide. When they do not, a single headcount field hides the disagreement until food is ready or the bill arrives. Writing the meaning beside the number is a small change with a useful consequence: sales, service and the kitchen can see exactly what has been agreed.
What the minimum guarantee means
Sarthi Hotel in Ahmedabad states in its own banquet terms that billing uses the higher of actual attendance and the guaranteed count. It also says the minimum given at booking cannot be reduced. That is a concrete example of a billing floor, rather than a prediction that every guaranteed guest will come (Sarthi Hotel banquet terms).
Radisson Srinagar’s public banquet brochure similarly says the guaranteed minimum is charged when attendance falls short. Its billing section describes an agreed plate-counting arrangement, with joint monitors and further plates released in lots of 25 after the initial minimum. Counting is therefore something the parties can settle before service, not reconstruct from memory afterwards (Radisson Srinagar brochure, page 10).
These are property-specific published examples checked on 15 September 2026. Neither document establishes a nationwide banquet rule. The pages are undated; the current event proposal and agreed terms need to confirm the count, revision deadline, extra-guest treatment and counting method for that booking.
For the host, a lower turnout can leave the minimum bill unchanged. For the kitchen, it does not prove that the difference became wasted food. Food may never have been cooked, may remain in an approved reserve, or may have been consumed in different quantities by the guests who came.
Give the event separate counts
The following is an illustrative event, not a reported hotel result or a recommended staffing or food buffer.
| Record | Example | What the number decides |
|---|---|---|
| Guaranteed guests | 200 | The contractual minimum used for billing |
| Expected attendance | 180 | The latest estimate used in planning discussions |
| Production plan | 190 equivalent portions | A simplified planning quantity, before item-level decisions |
| Actual customers served | 170 | The observed service volume |
| Billable guests | 200 | The result under this example’s higher-of-actual-or-guaranteed rule |
The attendance estimate is 20 below the guarantee. Actual service is another 10 below the estimate. Neither subtraction measures waste. The simplified production figure is also not evidence of 20 discarded meals: buffet dishes have different take-up, portion sizes and amounts remaining.
A real production sheet should break that illustrative meal-equivalent number into items and batches. A dessert portion, a bowl of gravy and a live-counter order cannot be treated as interchangeable units. Keep the agreed service capacity explicit even when the team’s most likely attendance estimate is lower.
Extra guests need more than a percentage
The Srinagar brochure separates its extra-guest pricing from the minimum: the quoted price extends to the guarantee plus 10%; consumption beyond that is charged at 10% above the quoted price, with a qualification about the additional food and service the hotel can provide. It also describes possible repricing or hall-hire changes if the guarantee is reduced after confirmation (brochure, page 11).
That wording is not a universal instruction to cook 10% extra. Price coverage, physical capacity and readiness to serve are separate matters. A kitchen may have ingredients available but lack the cooking time, hot-holding space or staff to turn them into the promised meal during a sudden arrival wave.
For a Chennai reception, the useful discussion is specific: how many additional diners can each counter accommodate, what can be replenished within the service window, and who can approve the extra count? A vague “we will manage” leaves both the host and the chef guessing.
Plate counting also needs a definition. Record how second plates, children, vendors and crew meals will be treated. A plate issued is a billing proxy only under the agreed method; it should not silently become the attendance measure in a separate operating report.
The billable guest count should not quietly become the kitchen’s demand forecast.
Translate attendance into a production plan
A forecast becomes useful when it reaches the chef in time to change a batch. Give the kitchen the latest estimate, its revision time and the basis for the change. A confirmed reduction from the host carries different weight from an informal guess made while the room still looks empty.
The team can then separate food ready for first service from ingredients or prepared reserve that can be released later under the property’s food-safety procedure. This is a planning choice, not a reason to delay an agreed meal or to depend on uncertain leftover reuse.
For buffet service, the next decision is the size of each release. The hotel buffet refill guide explains how remaining customers, recent demand and food already displayed can inform that decision. Keep the event’s total service promise visible alongside those smaller batches.
Before the function sheet reaches the kitchen
Record the guarantee and the agreed basis for billing extra guests. Keep the accepted proposal available to the team handling changes.
Add the service, time of revision and source of the estimate. Separate guest meals from crew or vendor meals if they have different arrangements.
Agree what the kitchen must be able to serve, by when, and what happens when arrivals exceed that capacity. State who authorises a change.
Set the first release and feasible reserve for each item. Review the slowest dishes and counters before applying a blanket buffer.
Record customers served, production, returns, discards and stockouts. Preserve the billing count separately so the next forecast uses attendance.
Use actual service in the waste denominator
There is another place the guarantee can distort the event review. Suppose the illustrative function above produces 17 kg of measured food waste within the same service boundary.
- Dividing by 200 guaranteed guests gives 0.085 kg per guaranteed guest.
- Dividing by 170 customers served gives 0.100 kg per customer served.
Using the guarantee makes the figure 15% lower than the actual-served measure. No food has been saved; only the denominator changed. These are worked numbers, not a benchmark for acceptable banquet waste.
The WWF and Greenview Hotel Waste Measurement Methodology includes food waste per customer as an additional measure and says customer data must also be collected. Its glossary defines customers by people served in the venue or function space (2021 methodology, Table 4b and Appendix H).
Use the same event and meal boundary for both the food weight and the served count. Our hotel food-waste log guide covers the source categories and missing-entry checks needed before that division is trustworthy.
The commercial review still needs its own numbers. Ingredient consumption, billable sales and discarded-food cost should remain identifiable; the food-cost percentage guide explains the stock-and-sales calculation. A well-covered minimum bill does not by itself show whether the kitchen forecast was accurate.