The same four-course menu costs more per head at a wedding than at a corporate dinner on a Tuesday — and couples who do not understand why think the caterer is charging a "wedding tax". They are not. A wedding genuinely costs more to deliver, for four specific reasons, and a caterer who cannot name them either underprices the job or loses the booking trying to explain a number they have not broken down. Here is what actually drives a wedding's per-head cost.
It is the same stack, weighted differently
A wedding is priced on the same per-head stack as any catering job — food, labour, rentals, overhead, margin. If that stack is new to you, start with catering cost per head; this piece is about the four things that push a wedding's numbers up relative to an ordinary event of the same size. None of them is greed. All of them are real cost.
1. The guarantee — you cook to a number, not a hope
A wedding runs on a guaranteed guest count: the couple commits to a minimum, usually a set number of days out, and you cook and bill to it whether or not every guest arrives. This protects you, but it also means you prep for the guarantee plus a buffer — you cannot run short at the one event nobody forgives running short at. That certainty has a cost: you are committing food and labour to a fixed number early, and the guarantee is what makes that safe to do.
2. The tasting — you cook the menu twice
Almost every wedding includes a tasting: you cook a version of the menu weeks before, for the couple, to win and confirm the booking. That is real food and real labour, and it belongs in the event's cost, not absorbed silently as a marketing expense. Spread a tasting across a 60-cover wedding and it is a dollar or two a head — small per guest, but it is there on every wedding you book, and pretending it is free is a slow leak across a season.
3. The timeline — weddings are long, labour-dense days
A wedding is not a two-hour service. It is a load-in in the early afternoon, canapés, a sit-down dinner timed around speeches you do not control, cake, and a breakdown that ends near midnight. That is a long, staff-heavy day — and banquet labour, not food, is the largest cost layer in catering. A wedding's timeline stretches the labour layer well beyond what the same menu would need at a tidy corporate lunch. The per-head food might be identical; the per-head labour is not close.
4. The buffer — the one cost you must not cut
At a wedding, running out of the main course is not a small operational hiccup. It is the story the couple and their families tell for years, the review that costs you the next ten bookings. So a wedding carries a buffer — on the protein especially — that an ordinary event might not. The buffer is food cost whether or not it is served, and it is the cheapest insurance in catering. The cost of a small protein buffer is trivial against the cost of the alternative.
A worked example, weighted for a wedding
60 guaranteed covers, four-course plated. Illustrative numbers — use your own:
| Layer | Per head | Wedding weighting |
|---|---|---|
| Food (incl. tasting + buffer) | ~$16 | tasting + protein buffer added |
| Labour | ~$43 | 10-hour day, full team |
| Rentals (china, glass, linen) | ~$12 | full formal setting |
| Overhead share | ~$8 | insurance, vehicle, admin |
Notice the food is barely a fifth of the cost. A couple comparing your $105 to a "we'll do it for $60" quote is not comparing the same thing — the cheaper number almost always has the labour underpriced, which shows up as a thin team and cold food on the day. When you can break the per-head down into these four drivers, the higher number stops being a "wedding tax" and becomes an itemised, defensible quote.
What couples are really buying
The food matters, but a wedding client is buying certainty: that 60 people will be fed well, on time, on the most scrutinised day of their lives, with nothing running short. That certainty is built from the guarantee, the tasting, the staffed timeline, and the buffer — the four things this article is about. Pricing research from hospitality programs such as the Cornell Nolan School of Hotel Administration covers the same labour-and-certainty cost structure that sits under every banquet quote.
In ProChefDesk
The Event tool costs the wedding menu against your real recipes scaled to the guaranteed count, tracks the labour layer as a real P&L line, and lets you add the tasting, buffer, rentals and service charge as itemised charges — then prints a client proposal that shows the four drivers without exposing your cost or margin. The couple sees an itemised, defensible number instead of a flat figure to haggle. Open the app to quote one.
What to do this week
- Put the tasting in the cost. It is real food you cook to win the job — price it into the event, not your overheads.
- Cost the labour for the whole day, load-in to breakdown, not just service.
- Carry a protein buffer and treat its cost as insurance, because it is.
- Break your per-head into the four drivers so you can show a couple why the number is the number.
The point
A wedding costs more per head because it is genuinely more to deliver: a guaranteed count you commit to early, a menu you cook twice, a long staffed day, and a buffer you cannot skip. Name those four drivers and the per-head price stops looking like a tax and starts looking like what it is — the honest cost of feeding 60 people perfectly on the one day that has to go right.