Skip to content

Banquet Notes

Per-event profit: food from the recipe, labor from the schedule, margin on the night.

Most venues can state what an event billed. Far fewer can state what it kept. The arithmetic is not hard — it is just spread across three systems that never talk, so nobody runs it.

· 6 min

A wedding books the room on a Saturday in October. The coordinator quotes it, the client signs, the deposit lands, and the night goes well. On Monday somebody asks what it made.

The honest answer at most independents is a shrug and a revenue figure. Revenue is the number the contract produced, and it is the number every system already knows. What the event kept lives somewhere else — half of it in the kitchen’s food cost, half in whoever worked the floor that night — and nobody assembles it while it still matters.

Start with the bill, in the order the client saw it

Worked on illustrative numbers, in the same order the client portal shows them, because a margin conversation that does not reconcile to the invoice is a conversation nobody trusts:

Subtotal            $9,500.00
Service charge 20%  $1,900.00
Tax 7%                $798.00
─────────────────────────────
Total              $12,198.00
Deposit (25%)       $3,049.50
Balance due         $9,148.50

That is the event as the client experiences it. Note what it does not contain: any statement of what the night cost you.

Then the two costs nobody adds up in time

Food cost comes from the plates, not from a guess. If the menu is built from costed recipes, a 140-guest plated dinner has a real number attached the moment the menu is chosen — not in a month, when the invoices land.

Labor comes from the schedule. Not “we usually run eight” — the actual shifts assigned to that event, at their actual rates.

Revenue (subtotal)  $9,500.00
Food cost           $4,800.00
Labor               $1,120.00
─────────────────────────────
Contribution margin $3,580.00   (37.7%)

$3,580 on a $9,500 event. That is the number worth knowing, and it is worth knowing at proposal time, not in a quarterly review — because at proposal time it is still a decision.

Why the margin is usually missing

Not because the arithmetic is hard. Because the three inputs live in three systems that were never introduced: the menu in one place, the schedule in another, the contract in a third. Assembling them by hand for every event costs more than most coordinators have, so it happens for the disasters and never for the ordinary Saturdays — which is exactly backwards, since the ordinary Saturdays are most of the year.

It may be worth running the number on your last five events before deciding anything. If the spread between best and worst is small, this is a report you can happily ignore. If it is wide, you have been pricing on instinct and finding out afterwards. The event-margin calculator runs the same arithmetic on your own figures, with nothing to sign up for.

What changes when it is automatic

When food cost comes from the recipes and labor comes from the schedule, the margin is previewed while the proposal is still a draft and recomputed as an actual after close-out. The coordinator sees it. The client never does. A date-hold policy, a minimum, or a menu swap becomes a decision with a number behind it rather than a feeling about October.

This is the part the incumbents mostly leave out: they will show you what an event billed all day long. Compared with Tripleseat, the difference is not the proposal or the BEO — both do those — it is whether anything tells you the profit on the night. The operator walkthrough shows where the number surfaces.

heard, captain.