Blog / Events & Banquets
Events & Banquets

How Much Food to Cook for an Event: Quantity Planning Without the Guesswork

By Jigar Chanana, Founder, HospiMinds··7 min read
Large catering trays being prepared for a big event
The short answer

Event food planning works off per-guest portions by dish category, adjusted for how long the menu is and who the guests are. The counter-intuitive rule: the more dishes on the menu, the less of each one people eat, because they sample rather than fill up on one item. Plan per-guest quantities per category, scale by headcount, add a modest buffer, and you avoid both the embarrassment of running short and the margin loss of cooking a mountain nobody eats.

Start with per-guest portions, not total pots

The reliable way to plan an event is bottom-up: decide the portion per guest for each dish category — so many grams of rice, of each main, of each starter, of dessert — then multiply by the guaranteed headcount. Guessing in "how many big pots" invites both shortfall and waste. Per-guest planning also connects cleanly to banquet pricing, because the same per-guest quantities that feed the crowd are what you costed the plate on.

Who is eating changes the numbers

Quantities also flex with the crowd. A corporate lunch eats differently from a wedding; a young crowd eats more than an older one; a long evening event with drinks sees more food consumed than a quick reception. Vegetarian-heavy gatherings shift the balance between dishes. Good planning starts from sensible per-guest defaults and adjusts for the event type and audience, rather than applying one number to every function.

The buffer: enough, not a mountain

You never want to run out — an event that runs short is remembered for it — so a buffer is essential, but a buffer is not a licence to double everything. A modest, planned over-production (a sensible percentage on the calculated quantity) covers the guest who comes back for more and the headcount that creeps up, without the wastage that eats the event's margin. Plan the quantity properly, add the buffer deliberately, and you protect both the guest experience and the profit.

Do it now, free

Event & Banquet Quantity Planner

Plan raw food quantities for weddings and events from guest count and per-person norms for rice, breads, curries, starters and dessert.

Open the tool

Step by step

Plan food quantities for an event.

  1. Set per-guest portions by category. Decide grams or portions per guest for rice, each main, starters and dessert.
  2. Adjust for menu length. Reduce the per-guest quantity of each dish as the number of options rises — people sample a long menu.
  3. Flex for the audience. Adjust for event type, crowd and duration; a wedding, a corporate lunch and a drinks evening all differ.
  4. Scale by headcount and add a buffer. Multiply by the guaranteed headcount and add a modest planned over-production — enough, not a mountain.

Frequently asked questions

How much food should I cook per guest for an event?

Plan per-guest portions by dish category — rice, each main, starters, dessert — then scale by headcount. The right per-guest quantity depends heavily on how many dishes are offered and the type of event, so start from sensible defaults and adjust.

Does a longer menu mean cooking more food?

Counter-intuitively, less of each dish. The more options on the menu, the less of any single item guests eat, because they sample across the spread rather than filling up on one. Per-dish quantities should fall as the number of dishes rises.

How much buffer should I add for an event?

A modest, planned over-production — enough to cover a guest returning for more and a headcount that creeps up — not a doubling of everything. Too large a buffer turns straight into wastage that eats the event’s margin.

Jigar Chanana · Founder, HospiMinds

BBA Hospitality (NMIMS). Grew up around the trade and built two hospitality platforms — Hospiverse and Hospiwork. Writes the numbers side of running restaurants, cafés and hotels in India.

Keep reading

Want this run for you? Book a free auditExplore the platform →