How to build a banquet menu: structure, portions and what the kitchen can deliver

A hotel banquet menu is a fixed structure of courses and choices built backwards from what the kitchen can send out at one time, not a list of dishes. Decide the service format first (plated, buffet or cocktail), then set the tiers, portions, allergen labels and the last date for changes.

The sales team sends the same three menus to every client, and the kitchen finds out on the day that two hundred hot plates have to leave the pass in the same ten minutes. The menu was never the problem. The order in which it was decided was. After reading this you will be able to build a hotel banquet menu from a capacity number, structure it in tiers, plan portions from the confirmed count, run the allergen duty correctly and control changes after signing.

What can your kitchen actually deliver at one time?#

The menu is limited by the pass, not by the recipe book. Count how many hot plates can leave the kitchen together and build the menu backwards from that number.

Follow the whole chain, not one link. Oven racks multiplied by trays and items per tray give you output; holding cabinets, pass width, the number of plates the hotel owns and the walk from pass to table decide whether that output reaches guests hot. A number that looks fine on paper dies in a corridor or a slow service lift.

Separate seated capacity from service capacity. A room may seat 300, but the kitchen may only be able to send 180 plated mains within the window the client expects. Service style sets the clock: a plated main has to land on every table within a few minutes of the first one, while a buffet only needs a replenishment rhythm the kitchen can hold for the whole service.

Count hands, not just equipment. Each plated course needs a fixed number of runners and commis per section, and that number does not shrink because the menu is short. Then work the timeline backwards from the fixed moment in the room, usually the speeches or the toast, and check where the kitchen would be standing at that minute.

Write the one-time-serve number on the menu sheet itself, so nobody in sales can promise a format the pass cannot deliver. For example, a kitchen that can plate 120 covers in fifteen minutes can serve a 200-guest wedding only by splitting the room into two sittings or by changing the main to a buffet. That decision belongs in the sales conversation, not on the event day.

The menu sheet then feeds the event order, which carries the whole service plan. If you have not fixed that document yet, read how a banquet event order carries the service plan.

Plated, buffet or cocktail: what does each ask of the kitchen?#

Plated service asks for timing discipline and plate count; buffet asks for holding equipment, replenishment and labelling; cocktail asks for small items that survive on a tray without cutlery.

In plated service, every plate must be identical and hot at the same moment, so the constraint is the pass plus the number of hands. Fewer choices per course is faster, and a choice of two mains is usually the practical maximum at scale. In buffet service, the constraint moves to holding temperature, refill cycles and queue length: long rooms need two lines or two identical buffets, and dishes are replaced in small batches rather than topped up.

A cocktail reception asks something different again. Items must be one or two bites, eaten standing, with no cutlery and no dripping, so the kitchen tests how long each item holds at room temperature before it is passed around. Mixed formats, a reception followed by a seated dinner, give the kitchen a changeover window that is often tighter than either service on its own; that window belongs in the plan.

The trade-off is always the same: choice costs speed, and speed costs choice. Decide which one the event is buying before the dishes are named. Note also that buffet carries a labelling duty that plated service carries on the menu card, which is why the format decision is also a compliance decision.

What does a hotel banquet menu look like in three tiers?#

A workable hotel banquet menu is a small set of fixed structures, not a long list of dishes: three tiers that differ by course count, protein and service style, all built on the same skeleton so the kitchen rehearses one flow.

The tiers should differ in structure, not in quantity. Adding a second dessert does not make a premium menu; adding a cold starter and a choice of mains does. Keep one skeleton across all three tiers: cold, soup, main with sides, dessert, tea and coffee. The kitchen then learns one sequence and swaps components inside it.

For example, an essential tier might be soup, one main with two sides, one dessert and tea or coffee; a signature tier adds a cold starter and a choice of two mains; a premium tier adds a meze trio, a vegetarian main alongside the two choices, and a dessert duo. This is an illustration, not a standard.

Cap the choices in writing. Every extra main splits the pass, slows the plating and raises the chance of a wrong plate reaching a guest. Write the menu description the guest will read at the same time as the kitchen sheet, so the words on the card and the work at the pass describe the same dish. Include the drinks line and the service time on the same page, because a menu without a time is only half a plan.

Illustrative structure, not a price list or a standard.

How do you plan portions and quantities?#

Plan from the confirmed number, not the expected one: take the guaranteed guest count, add a margin you have decided on purpose, and convert each dish into a per-guest quantity the kitchen can multiply.

Separate the expected number from the guaranteed number. The guaranteed number is what you buy, prep and cook for; the margin above it is a commercial decision, not a habit. Set the portion from the hotel's own standard recipe, so the same dish costs and looks the same at every event, and so a change of chef does not change the plate.

For buffet, plan by covers and refill cycles rather than one large display: smaller batches, more refills, less food sitting under a lamp. Count separately the guests who will not eat the main menu: children, vegetarian and vegan guests, guests fasting, and the technical crew and musicians who are often fed from the same kitchen.

Agree the last date for the final guest count in the contract, and name the person who owns that number, because the kitchen orders against it. Then measure what comes back: weighing buffet returns after a few events gives the hotel its own real per-guest figure, which is more useful than any published norm. The same thinking applies to all-inclusive breakfast and dinner buffets; see planning buffet quantities from covers and measuring what is wasted.

How do you handle allergens, vegetarian, child and religious needs?#

Start with a written allergen matrix for every menu item and one named person who answers questions, because for non-prepacked food the information duty is legal, not optional.

The duty in Türkiye: under the Turkish Food Codex Regulation on Food Labelling and Consumer Information (Official Gazette 26 January 2017, No. 29960 bis; last amended 6 April 2024, No. 32512), consolidated on the Mevzuat Bilgi Sistemi (opens in a new tab), mass catering places must give consumers the name of the food, the substances or products in Annex 1 that cause allergies or intolerances, and the extra mandatory information on alcohol and pork-derived ingredients (Annex 2, rows 6 and 7). The information must be easy to see and clearly legible, on menus, boards, brochures or similar means (Article 15(5), read with Article 9(1)(a) and (c)). Confirm how this applies to your own operation with your food safety adviser or local authority.

Build the matrix once per menu: rows are dishes, columns are the Annex 1 allergen groups. Update it whenever a recipe, a supplier or a garnish changes, not once a year. Cross-contact is a kitchen question, not a recipe question: shared fryers, boards, tongs and grills decide whether a dish is safe for a guest, so the matrix must describe the kitchen, not only the ingredient list.

Vegetarian and vegan guests need a designed dish, not the meat removed from the plate; a vegetarian main also has to be plated at the same speed as the others. Children need a smaller portion, mild seasoning, no bones, and served early, so the child plate does not compete with the main service at the pass. Religious and cultural needs, including pork and alcohol avoidance and fasting periods, should be asked at the point of sale and written on the order, never discovered on the day. For the service side, a guest safety routine for food allergies in restaurants and buffets covers the floor and kitchen handover.

What should a tasting promise, and who attends?#

A tasting is a decision meeting, not a treat: the people who will sign the order and the people who will cook it should both be in the room, and what is tasted must be what will be served.

Who attends: the client's decision maker, the chef or sous chef who will run the event, the banquet manager and the salesperson who wrote the order. Cook at event scale where the equipment allows, or at least with the same equipment and the same holding time, because a tasting for four does not test a 200-cover service.

Taste the whole menu, including the vegetarian main and the child plate, not only the dishes the client is excited about. Record what was agreed: photograph the plate, write the garnish, the portion and the sauce on the tasting sheet, and have the client sign that sheet.

State what the tasting does not prove: it does not test timing at volume. That needs a separate rehearsal or a proven format from a previous event. Agree in advance who pays for the tasting, how many people may attend, and how far ahead it happens, because all three vary by hotel and by event size.

What happens when the client changes the menu after signing?#

Set the last date for changes in the contract, price every change from the recipe cost, and treat each change as a new version of the menu sheet that the kitchen, the labels and the order all follow.

The cut-off date is a kitchen date, not a sales date: after it, ingredients are ordered, prep has started and staff rotas are fixed. Version control is the discipline that prevents most event-day errors: every change gets a number, a date and initials, and only the latest version is valid at the pass. Two versions in circulation is how a wrong plate reaches a guest.

Price the change honestly from the standard recipe cost: ingredients already bought, re-testing, extra labour and any new equipment need. A change is rarely only a swap of one dish. Treat a change of guest number differently from a change of menu: the first moves quantities, the second moves the kitchen's whole plan and often the service format. For the costing side of this, see standard recipes and portion cost in the hotel kitchen.

Push the change through every copy: the kitchen sheet, the buffet dish cards, the allergen matrix, the printed menu for the table and the event order. For example, replacing a plated main with a buffet main two days before the event changes the plate count, the staffing and the room layout, not just the dish name.

What to do next#

Before the next menu goes out, write the one-time-serve number on it: the plates the pass can send together, the hands available, and the fixed minute the room expects. Everything else in this article, the format, the tiers, the portions, the allergen matrix, the tasting and the change cut-off, hangs from that number, and it is the one thing sales and the kitchen can agree on before a single dish is named.