Catering menu guide: the per-head math that decides whether a 50-guest event makes money

A catering menu is a fixed set of packages priced per head, committed to before the event, and produced for a guaranteed guest count. That makes it a different object from a restaurant menu, which is an à la carte list priced per dish and cooked on demand. The commercial consequence is that a catering menu is mostly arithmetic: portions per guest, staff per guest, and a cost structure that has to survive a cancellation two days out.

Most catering menu articles are lists of dish ideas. This one is the other half — the part that decides whether the event is profitable. Every number below carries a named source and a date, and where no authoritative standard exists, that is stated rather than papered over.

What makes a catering menu different from a restaurant menu

Dimension	Restaurant menu	Catering menu
Unit of sale	One dish	One guest, or one package
When the guest chooses	At the table	Weeks or months ahead
Production quantity	Unknown until service	Fixed by a guaranteed count
Price basis	Per item	Per head, plus labour and rentals
Who absorbs a no-show	The restaurant, as an empty table	The client, if the contract says so
Allergen handling	Guest asks the server	Client declares at booking, no server present at service
Menu lifespan	Until the next print run	Until the ingredient market moves

The last two rows are where catering menus actually go wrong. A guest at a table can ask what is in the sauce. A guest at a wedding buffet cannot, because nobody who knows is standing there. And a restaurant absorbs a bad ingredient price on one dish, while a caterer who quoted a per-head price in March for a September event has locked in that exposure across 150 covers.

The six service styles and what each costs in labour

Service style drives staffing, equipment and dining duration more than the food does. There is no national staffing code for catering, so the honest way to present ratios is to show real published operating rules and their spread.

Service style	Published staffing basis	Staff for 50 guests	Service labour	Fits
Plated / sit-down	Nicolet College catering curriculum: 1 server per 20-25 guests, plus 1 kitchen employee per 30-40. Marquette: 1 waitstaff per 20 at lunch and dinner	2-3 servers plus ~2 kitchen	High	Formal dinners, awards, programmed events
Buffet	Nicolet: 1 person front and 1 back per 50 guests for hot self-service. Marquette: 1 waitstaff per 30 at lunch and dinner	2	Medium-low	Conferences, weddings, anything needing throughput and choice
Family style	Institutional policies run as tight as 1 staff member per 12 guests	~4-5	High	Social dinners built around shared tables
Action stations	Staffing follows station count, not guest count: commonly 1-2 attendants per station	2-4 for two stations	Medium-high	Networking receptions, experiential events
Passed hors d’oeuvres	Commonly 2 attendants per 25 guests for butlered service	~4	High labour, lower food consumption	Cocktail hours, openings, mingling formats
Drop-off / delivery	No on-site service staff; delivery and setup labour only	0 on site	Lowest	Office lunches, casual meetings, budget events

The ratios come from Nicolet College’s catering personnel chapter and Marquette University’s food and beverage planning guide, both accessed August 2026.

Notice the spread. Nicolet’s plated ratio is one server per 20-25 guests; some university catering operations run one per 10 to 12. All of those are genuine operating rules, and none of them is a US standard. Anyone who tells you “one server per 20 is the industry standard” is quoting one operator and calling it a law.

The practical answer is to store labour as a formula rather than a constant:

event labour = prep + production + delivery and setup + service + bussing + breakdown + management

Then attach a house service standard to each style and check it against actual event hours for a season. That is what stops the classic buffet mistake: pricing from food cost, saving on servers, and then discovering that replenishment, clearing and breakdown ate the saving.

Portion planning: starting points, not standards

No FDA or USDA rule sets banquet production portions. USDA food-group servings serve nutrition programmes and the FDA Food Code governs safety; neither is a production standard, and repackaging them as one is how bad catering advice gets written. The usable numbers come from university extension education and institutional catering operations, and they openly disagree.

Situation	Sourced planning figure	Source
Reception, no meal served	14 appetizers per person per hour	Marquette University catering planning guide
Reception over the lunch hour	~10 appetizers per person	Marquette
Late afternoon or evening reception	6-8 appetizers per person	Marquette
Boneless meat	1/4 to 1/3 lb (2-3 oz cooked) per serving	Iowa State University Extension, December 2025
Bone-in cuts	1/3 to 1/2 lb per serving	Iowa State Extension
Bone-heavy meats and turkey	3/4 to 1 lb per serving	Iowa State Extension
Vegetables	4 oz per serving	Iowa State Extension
Potatoes	5 oz per serving	Iowa State Extension
Grains	1.5 oz per serving	Iowa State Extension
Bread	1-2 portions per person	Iowa State Extension

The meat and side figures come from Iowa State University Extension’s meal-quantity guidance, which also notes children count as roughly half an adult serving.

The gap between a 6-piece reception and a 14-piece one is not one source being wrong. It is proof that event context governs consumption: piece size, richness, time of day, and whether anything else is being served. Build the question into the booking form rather than averaging the two into a number that fits no event.

Two numbers per menu item, always

Every item on a catering menu needs a served portion and a production factor, and conflating them is the most expensive error in the trade.

The served portion is what reaches one guest under controlled plating. The production factor is what the kitchen must buy or produce per guaranteed guest after cooking yield, trim and bone loss, guest choice behaviour on multi-protein menus, and a documented overage policy. A 6-ounce finished chicken portion is not 6 ounces of raw chicken purchased. Iowa State’s bone-in figures exist precisely because that conversion is where the money leaks.

There is also no authoritative buffet overage percentage. The folklore “add 10%” has no US source behind it. Replace it with your own consumption data: record guaranteed attendance, portions produced, product returned unserved, product discarded, and items that sold out. Two seasons of that turns industry practice into your standard, and it feeds directly into the waste side of the operation covered in our restaurant food waste statistics hub.

How to structure catering packages

Three tiers work because they let the client self-select on budget without you quoting from scratch each time. The structure that survives contact with real bookings looks like this.

Tier 1, the volume package. One protein choice, two sides, a salad, bread, disposable service. Drop-off or minimal-staff buffet. This is the office lunch and the community event. It exists to be booked without a phone call.

Tier 2, the standard package. Two protein choices including one vegetarian, three sides, salad, bread, dessert, staffed buffet with china. Most bookings land here, so this tier’s margin sets your season.

Tier 3, the full-service package. Plated or family style, coursed, passed hors d’oeuvres on arrival, full rentals, dedicated event captain. Priced from the labour up.

Then decide what is deliberately not in any tier: bar service, rentals beyond the standard set, cake cutting, late-night additions, overtime beyond the contracted window, and delivery outside a defined zone. Every one of those should be a named line item with a price, because each is a real cost and none of them scale with the per-head number.

One structural warning from the à la carte world applies here too. The comparison of fixed-price and per-item formats in our guide to à la carte vs prix fixe menus is the same trade-off catering packages make: a fixed package is predictable to produce and easy to price, and every substitution the client negotiates erodes both of those properties. Decide in advance which swaps are free, which carry a fee, and which are refused.

How to price catering per head

The formula that keeps a caterer solvent solves for margin instead of adding markup to ingredients:

required pre-tax revenue = (food + labour + rentals and disposables + logistics + allocated overhead) ÷ (1 − target operating margin)

Food cost percentage is a cross-check, not the pricing system. A restaurant benchmark of roughly 30% food cost has no authority over a catered event where labour and rentals can exceed the food line entirely.

Here is the arithmetic for a 50-guest staffed buffet, with every input visible. These are illustrative inputs for the method, not market rates; substitute your own invoices.

Line	Calculation	Amount
Food, at recipe cost	50 x $11.00	$550.00
Kitchen production labour	14 h x $26 loaded	$364.00
On-site service, 2 staff	2 x 5 h x $28 loaded	$280.00
Delivery and vehicle	Flat, 18-mile zone	$120.00
Rentals, chafers, linen, china	Per event	$310.00
Disposables and packaging	Per event	$65.00
Allocated overhead	12% of the above	$178.68
Total event cost		$1,867.68
Required revenue at 18% margin	$1,867.68 ÷ 0.82	$2,277.66
Per-head price	÷ 50 guests	$45.55

Two things fall out of that table. First, food is under 30% of the total cost, which is exactly why pricing from a food-cost percentage misprices catering. Second, the per-head number is a function of the guest count: the same event at 30 guests carries the same delivery, rentals and setup labour, so its per-head price is materially higher. That is what a minimum guest count exists to protect.

The general costing method behind all of this is covered step by step in how to price a restaurant menu; catering adds the labour, rentals and logistics layers on top.

What the market data actually says

There is one legitimate per-head benchmark worth knowing, and it is narrower than people quote it. The Knot’s 2025 Real Weddings Study, based on almost 17,000 US couples who married in 2024, reported an average wedding catering cost of $80 per person, with a regional range of $62 to $123 — lowest in the Midwest, highest in the Mid-Atlantic.

That is wedding-market data on 2024 spending. It is not a 2026 national catering rate, and it does not describe corporate drop-off, institutional catering or private parties. No transparent study establishing an all-events US catering price per head turned up in this research. Benchmark local competitors and your own cost model instead of publishing somebody’s wedding average as your rate card.

Service charge is not a gratuity

This distinction has payroll and tax consequences, so it belongs in the contract and the pricing model.

The US Department of Labor’s Fact Sheet #15 states that a compulsory charge for service — 15% of the bill, for example — is not a tip under the Fair Labor Standards Act. Sums distributed to employees from service charges are not tips; they count toward the employee’s total compensation and must be included in the regular rate for overtime.

The IRS reaches the same place from the tax side. Its guidance on tip recordkeeping and reporting treats mandatory service charges as employer income, with distributions to employees treated as wages, while an amount is a tip only where the customer genuinely decides whether and how much to pay.

So a catering contract should say plainly whether a percentage is a service or administrative charge, whether any part reaches service staff, and whether a separate voluntary gratuity is expected. Calling a mandatory 20% a “gratuity” on the menu and then treating it as a service charge in payroll is the version that generates a wage claim. None of this is legal advice; verify with counsel in your jurisdiction.

Allergens: nine, not eight

The single most common outdated statement in catering documents is the “Big 8”. FDA confirms sesame is the ninth major food allergen under the FASTER Act, effective 1 January 2023. The current US list is:

milk · eggs · fish · crustacean shellfish · tree nuts · peanuts · wheat · soybeans · sesame

Two legal regimes are involved and they are not the same thing. Packaged-food allergen labelling sits under federal law. Restaurant and catering obligations come through the FDA Food Code, which is a model that states and localities adopt into their own rules — FDA itself states the Food Code is neither federal law nor federal regulation. Sesame was added to the 2022 Food Code as a major food allergen on the same 2023 date.

Where a jurisdiction has adopted the 2022 Food Code language, unpackaged food served in a retail food establishment requires written notification of major allergens present as ingredients, and FDA lists acceptable forms including physical or electronic menus, brochures, labels, table tents and placards. Self-dispensed bulk food carries its own prominent labelling requirement, which is directly relevant to buffets. Allergen awareness is also required in food-safety training under the same edition.

A cross-contact protocol that survives an event

FDA defines allergen cross-contact as the unintentional incorporation of an allergen into food. Its retail research on allergen removal and transfer found that a full wash, rinse, sanitize, air-dry procedure was effective at removing allergens and limiting transfer, with pre-scraping helping and wet wipes outperforming dry ones. Wiping a surface with a dry cloth is not an allergen control.

The workflow that holds up:

1. At booking, capture allergies and dietary requirements as counts against the guest list, separately from preferences. “Some GF” is not a specification; “3 gluten-free, 1 severe peanut allergy” is.
2. Before production, keep an ingredient-to-allergen matrix built from current supplier labels, so a substituted bread or sauce changes the item’s allergen profile automatically.
3. During production, sequence deliberately, segregate utensils and clean fully between incompatible tasks.
4. At service, put durable labels on every buffet and station item and keep the matrix with someone trained to answer questions.
5. For special meals, never say “allergen-free” when you mean “made without that ingredient in a shared kitchen.” State the difference in writing.

State law can go further than the federal baseline — Massachusetts and Rhode Island both impose their own allergen-awareness requirements on food service establishments. The checklist is federal packaged-food rules, then the adopted state Food Code, then state allergen statutes, then county and city health rules.

Wedding and holiday menus

Weddings and holiday events change three things about the menu without changing its structure.

Lead time gets longer and prices get riskier. A quote issued in March for a September wedding is a nine-month commodity exposure. Put a validity date on every proposal, mark genuinely volatile items at market price, and define in the contract what happens when a market price moves.

Dietary requirements arrive in bulk. A 150-guest wedding will produce a list of restrictions from the couple rather than from individual guests, usually late. Set the deadline for that list at the same point as the final guarantee, not after it.

Guest counts move in one direction. Final-guarantee clauses in hotel and institutional contracts commonly sit 3 to 7 business days out, are non-reducible, and allow late increases within a capped percentage. That band reflects purchasing lead time, not a legal standard — set yours from your own ordering deadlines.

Holiday catering compresses all of it. The same three weeks carry your highest volume, your tightest labour market and your least flexible delivery windows, which is an argument for capping how many events you accept per day rather than for raising prices alone.

Contracts: the clauses that actually matter

There is no national standard for catering terms. Published contracts show a consistent pattern — deposit at signing, non-reducible final guarantee shortly before production, cancellation costs rising as the date approaches — but the specific percentages and deadlines vary widely between operators. Pick yours from your own exposure.

Clause	What it protects	How to set it
Minimum	Fixed delivery, setup and rental cost on small events	From the smallest event that still covers its own labour
Deposit	Date reservation and early purchasing	Tie it to genuine reservation risk; state clearly when it becomes non-refundable
Staged payment	Large events with big pre-buys	A balance point weeks out, final balance days out
Final guarantee	Production quantity	Match your purchasing and prep lead time, commonly 3-7 business days
Non-reducible guarantee	Food already bought	State that decreases after the deadline are not credited
Late increases	Last-minute additions	Cap them as a percentage and price them separately
Cancellation schedule	Unrecoverable purchases and reserved labour	Dated tiers rising toward 100% near the event
Price validity	Ingredient market movement	An effective date on the quote plus a market-price clause
Service charge definition	Payroll and tax treatment	Say whether it is a service charge or a gratuity, per the DOL and IRS position above

How to deliver the menu to the client

Catering menus live as PDFs, and that is the format’s core operational problem. A PDF sent to twenty prospects is twenty copies of your prices in twenty inboxes, and you cannot correct any of them. When beef moves 14% in a quarter, the old file keeps quoting the old number back at you, and the client is not wrong to hold you to what they were sent.

The architecture that fixes this without abandoning the sales document:

A web page as the source of truth → a printable or PDF sales version generated from it → an event-specific proposal or BEO → the signed guarantee.

Only the first layer needs editing when a price moves. The others are generated from it. Put a visible effective date on the web menu so a client can see which version they are looking at, and put the quote-validity clause in the proposal so the binding price is the contracted one, not whichever file someone forwarded.

The practical migration is smaller than it sounds: the existing PDF becomes the content of a page, the page gets a link and a QR code, and the QR goes on the tasting-room card and the proposal cover. Our guide to converting a PDF menu into a QR menu covers the mechanics. Three benefits show up immediately: a price fix propagates everywhere at once, package contents can carry photos without a 40 MB attachment, and corporate clients with international attendees can read the menu in their own language, which matters more than it used to given the demand for multilingual menus.

Catering menu template structure

A catering menu that a client can buy from, in order:

1. Header — business name, contact, service area, effective date of prices
2. How it works — lead time, minimums, deposit, final guarantee deadline in plain language
3. Packages — three tiers, each with what is included, per-head price and minimum guest count
4. Service styles offered — with what staffing each includes
5. À la carte additions — passed hors d’oeuvres, stations, desserts, beverages, priced individually
6. Dietary and allergen statement — the nine allergens, how to declare restrictions, and an honest cross-contact note
7. What is not included — bar, rentals beyond standard, overtime, delivery outside the zone, cake cutting
8. Terms summary — deposit, guarantee, cancellation schedule, service charge definition, tax
9. Next step — one link or button to request a proposal

Bakery-cafés and other venues adding events to an existing operation can lift most of this structure directly; the pricing arithmetic is the same one used in our bakery menu guide, with event labour and rentals stacked on top.

If you want to test the web-first version cheaply, Duckhub’s free Egg plan covers a full menu with 70 products and 10 categories at 0% commission, which is enough to publish a catering package page with photos and hand clients a link instead of an attachment. The point is not the software. It is that your prices should exist in one place you control, with a date on them.