Chapter 14: Catering — Menus, Service Styles, and Reading the BEO

"Ask not what you can do for your country. Ask what's for lunch." — Orson Welles, quoted in various forms; the sentiment is his, the exact wording varies by source

Chapter Overview

At 6:47 p.m. the first plate goes down at table three.

At 7:29 the last plate goes down at table seventeen.

Forty-two minutes, and in that time the couple has been photographed twice, the best man has asked three separate people when he is speaking, four guests have gone to the bar because there is nothing in front of them, the band has played its entire dinner set and started it again, and the food that went out at 6:47 is now being eaten by people at table three who finished eleven minutes ago and are watching table seventeen receive theirs.

Nothing went wrong. Nobody was late, nothing was cold, no dish was missing. The caterer staffed to their standard ratio and served in their standard time.

Forty-two minutes is what plated service for 140 guests takes at one server per 25. It was in the proposal, in the staffing line, and nobody converted it into minutes.

This chapter converts it.

Catering is the largest line in almost every wedding budget — roughly a third of the total — and it is the vendor whose decisions most constrain the timeline, the floor plan, the power budget, and the guest experience. It is also the category where planners are most inclined to defer to the vendor, on the grounds that food is the caterer's job.

Food is the caterer's job. Service is a schedule, and the schedule is yours.

In this chapter, you will learn to:

• Compare six service styles on cost, duration, staffing, and space — and know which one a specific event needs
• Design a menu around what a season, a kitchen, and a guest count will actually support
• Handle dietary requirements safely, which means having a protocol rather than a list
• Read a banquet event order and find the four things that are usually wrong with it
• Set a guarantee, and know what it costs to be wrong in each direction
• Compute how long dinner takes, before it takes it

🏃 Fast Track: If you have hospitality or foodservice experience, skim §14.2 and read §14.1 (the duration arithmetic), §14.3 (the allergen protocol), and §14.4 (the BEO) in full. The service-style comparison will be familiar; what will not is the conversion of staffing ratios into timeline minutes, which is the planner's specific contribution and which the industry mostly does not do. Then do exercises B.1, B.3, C.2, and D.1.

🔬 Deep Dive: Work case-study-02.md, which designs the same dinner four ways for the same budget and measures cost, duration, staffing, space, and what a guest actually experiences.

14.1 Service Styles

Six, and they differ on four dimensions that matter.

⚡ Quick Reference: service styles compared

	Plated	Family style	Buffet	Stations	Heavy passed	Seated buffet
Cost per head	Highest	High	Lower	Variable, often high	Variable	Mid
Staffing ratio	1:18–1:25	1:22–1:30	1:35–1:50	1:25–1:35	1:15–1:20	1:25–1:35
Service duration, 140 guests	35–45 min	15–20 min	40–60 min	Continuous	Continuous	30–40 min
Space required	Least	Least	Buffet + queue	Most	Least	Buffet + queue
Kitchen demand	Highest	High	Moderate	High	Moderate	Moderate
Food waste	Lowest	Highest	High	High	Moderate	High
Guest experience	Formal, individual	Communal, conversational	Choice, movement	Grazing, social	Mobile, no seating rhythm	Choice, seated
Dietary handling	Easiest	Hard	Moderate	Moderate	Hard	Moderate
Works in a field kitchen?	Difficult	Yes	Yes	Difficult	Yes	Yes

The two figures nobody converts: the staffing ratio and the service duration. Everything else on this table is discussed at every tasting; those two determine what the timeline looks like and they are treated as the caterer's internal business.

The duration arithmetic

💰 Run the Numbers: how long does dinner take?

Plated service. A server carries three to four plates and serves a table of eight in roughly 90 seconds, then returns to the kitchen or plating area. Round trip, including the walk, is 3–5 minutes per table depending on distance (Chapter 11's service path).

At 140 guests, 18 tables, one server per 25 guests = 6 servers:

$$\frac{18 \text{ tables}}{6 \text{ servers}} \times 4 \text{ min} = 12 \text{ min per course}$$

That is the theoretical figure. In practice it runs 1.5–2× longer — plating is not instantaneous, the kitchen releases in waves, and the first table is served while the last is still being plated.

Realistic: 18–25 minutes per course. Three courses with clearing between: 45–70 minutes of service, plus eating time.

Add two servers — 1:18 instead of 1:25 — and it falls to 13–18 minutes per course. Roughly 20 minutes saved across dinner, for the cost of two servers (~$520).

---

Family style. Platters go to the table; guests serve themselves.

At 18 tables with 3 platters each = 54 platters. Two servers can place a table's platters in about 40 seconds.

$$\frac{18 \text{ tables}}{3 \text{ pairs of servers}} \times 1.5 \text{ min} = 9 \text{ min}$$

Realistic: 15–20 minutes for the whole meal to be on the table, against 45–70 for plated.

---

Buffet. Throughput is roughly 100 guests per hour per single-sided line (Chapter 11 §11.3).

140 guests, one single line: 84 minutes. One double-sided line or two singles: 42 minutes.

And the last table sits down 42 minutes after the first, which is the buffet's real cost and the reason tables are released in sequence rather than all at once.

🔄 Check Your Understanding

1. A caterer proposes plated service at 1 server per 30 for 160 guests, 20 tables. Estimate the per-course service duration and say what you would ask for.
2. Why does family style take a quarter of the time of plated service?

Verify

1. 20 tables ÷ 5.3 servers × 4 min ≈ 15 min theoretical, so realistically 23–30 minutes per course — 70–90 minutes across three courses. Ask for 1:20 (8 servers). The three extra servers cost roughly $780 and save about 25 minutes of dinner, which is 25 minutes returned to dancing.
2. Because the unit of service changes. Plated service delivers one plate per guest — 140 individual deliveries. Family style delivers three platters per table — 54 deliveries for the same 140 guests, and the guests do the rest of the work themselves.

Choosing one

⚡ Quick Reference: which style for which event?

Situation	Style
Formal, and the couple ranked food highly	Plated
Vision document says "dinner party," communal, warm	Family style
Field kitchen, no commercial kitchen	Family style or buffet
Budget-constrained at high guest count	Buffet
Many dietary requirements	Plated (easiest to control)
Guests will not sit still; social, mingling event	Stations or heavy passed
Tight timeline, needs dinner done fast	Family style
Older guests, mobility considerations	Plated or family style (not buffet)
Very high guest count (250+)	Buffet or stations — plated becomes very slow

The one to be careful about: heavy passed hors d'oeuvres as a dinner replacement. It photographs well, it suits a mingling event, and guests reliably report being hungry. If it is chosen, the volume must be substantially higher than instinct suggests — typically 12–16 pieces per guest across the evening — and there must be somewhere to sit.

The hybrid that usually wins

Most good weddings do not use one style. They use two, and the combination solves problems that neither solves alone.

The one to avoid: buffet plus plated dessert. Guests queue, sit, eat, and are then served — which means the service staff sized for a buffet (1:40) must suddenly perform plated service, and they cannot.

The general principle: each service style is chosen for a moment, not for the event. Ask what each part of the evening needs — speed, formality, movement, choice — and pick per moment.

14.2 Menu Design

Four constraints, in order of how much they actually bind.

1. The kitchen. Chapter 13 established what Wildrye Farm does not have. A caterer working from a field kitchen can hold, finish, and plate; they cannot execute a dish that needs to be cooked to order. This eliminates whole categories — anything seared to temperature, anything that must be assembled hot at the last moment, anything requiring a pass.

2. The season. September is not June. A menu designed from an image taken in May will be more expensive and worse in September, for the same reason Chapter 17's floral will be.

3. The guest count. Some dishes scale and some do not. A dish that requires individual attention at 40 guests becomes a different dish at 140.

4. The couple. Last on this list deliberately, and first in the conversation.

⚡ Quick Reference: what travels and what does not

Holds well (field kitchen friendly)	Does not hold
Braises, stews, slow-cooked meats	Anything seared to temperature
Roasted vegetables	Delicate fish
Grains, pulses, gratins	Soufflés, anything risen
Whole roasted proteins, carved	Fried anything
Composed salads dressed at service	Dressed leaves held
Family-style platters	Individually plated hot components

The rule for a raw site: the menu should be dominated by things that are better after 40 minutes than after 4. That is not a compromise — braises, roasts, and grain dishes are among the best food anyone serves at a wedding, and a caterer who is asked for them will be relieved.

Season, and what it actually costs

The second constraint, and the one couples resist most because inspiration boards have no calendar.

⚡ Quick Reference: eating with the season

Month	Abundant and cheap	Expensive or poor
Spring	Asparagus, peas, new potatoes, lamb, early greens, rhubarb	Tomatoes, stone fruit, squash
Summer	Tomatoes, stone fruit, corn, beans, berries, herbs	Root vegetables, brassicas
Early autumn	Squash, apples, late tomatoes, corn, plums, mushrooms, brassicas	Asparagus, berries, delicate leaves
Winter	Roots, brassicas, citrus, game, preserved and cured	Almost all fresh produce; anything flown in

The Reyes–Whitfield wedding is mid-September, which is the single best month in most temperate markets — the overlap where summer produce is still available and autumn produce has arrived. A caterer told "September, and cook what's good" has more to work with than at any other point in the year.

What seasonality is worth: a dish built on in-season produce typically costs 20–35% less than the same dish built on out-of-season equivalents, and it is better. That is the largest single lever on food cost that does not reduce the amount of food.

And the conversation to have in month three: a couple whose board is full of May images planning a September wedding should be told, once, gently, that their menu will be different and better rather than different and worse. It is the same conversation as Chapter 17's floral substitution and it should be had at the same time.

🎤 From the Field: let the caterer design the menu

The single most common menu error is a couple selecting dishes from a list and a planner passing the list on.

A better brief, and it produces better food:

"Here's what we've got: a field kitchen, no commercial gas, propane holding, a 32-inch doorway, a hundred guests, mid-September, family style, and a budget of $11,800 all-in.

Here's what the couple care about: food is their first priority, they want it to feel like a very good dinner party, and they've said 'nothing that looks like wedding food.'

Here's what they don't eat: [list]. And here are the dietary requirements: [matrix].

What would you cook?"

A caterer given that brief will propose something they are good at, in season, that works in their kitchen, at the price. A caterer given a list of dishes will cost the list.

The difference is routinely $8–$15 a head and a noticeably better dinner, and it costs nothing but the willingness to ask an open question.

The tasting

Held 4–8 months out, usually for two to four people, sometimes at a cost that is credited against the booking.

What a tasting is for: confirming quality, agreeing seasoning and doneness, and — the part people miss — seeing the plating and the portion.

What a tasting is not: representative of service conditions. A tasting is four plates cooked to order in the caterer's own kitchen. Your wedding is 100 plates held and finished in a field. A good caterer will say so.

⚠️ Common Pitfall: the tasting that changes everything

Couples frequently leave a tasting having selected a dish that cannot be produced at scale in their kitchen, because it was superb as one of four plates.

The planner's job at a tasting is to ask, of each dish: "how does this change at a hundred, in a field?" A caterer will answer honestly and the answer is sometimes "it doesn't work, and here's what I'd do instead."

Ask it in front of the couple. It saves the conversation happening later, without you.

Course structure, and where the money is

A wedding menu is not one decision. It is four, and they are priced very differently.

⚡ Quick Reference: the four eating moments

Moment	Typical spend	What it is actually for
Cocktail hour	$12–$28/guest	Occupying an hour in which guests have nothing to do. Under-catering here is the most-noticed food failure at a wedding
Dinner	$55–$120/guest	The meal
Dessert and cake	$4–$14/guest	Frequently duplicated — see below
Late-night	$6–$12/guest	Keeping the party going (Ch.11's activation problem, applied to food)

Three findings that fall out of this table:

Cocktail hour is the most under-budgeted and most-noticed hour of the day. Guests arrive from a ceremony, stand for sixty to ninety minutes, drink on an empty stomach, and are hungry. Three passed items over an hour is not enough at any guest count — the working figure is 5–7 pieces per guest, and at a longer cocktail hour, more.

Dessert is frequently bought twice. A couple orders a wedding cake and a plated dessert. Most guests eat one. Cutting the plated dessert and serving the cake as dessert typically saves $6–$10 a head — at 100 guests, $600–$1,000 — and no guest has ever noticed the absence.

Late-night food is a party mechanism, not a nicety. It resets the room's energy at the point where an evening either continues or dissolves, and at $6–$12 a head it is among the cheapest interventions available. Chapter 22 treats it as an arc device.

💰 Run the Numbers: two menus, same total

100 guests, $11,800 all-in for food.

	Menu A — conventional	Menu B — reallocated
Cocktail hour, 3 passed items	$1,500	—
Cocktail hour, 6 passed items	—	$2,400
Dinner, family style	$8,200 | $7,600
Plated dessert	$800	—
Cake (bought separately, both)	—	—
Late-night food	—	$700
Service charge, tax (20%, 7.75% on food)	included in loaded rates	included
Total	$10,500** | **$10,700

**For $200, Menu B buys:** double the cocktail-hour food at the hour guests are hungriest, and a late-night moment at 10 p.m. **It gives up:** $600 of dinner richness and a plated dessert nobody would have eaten alongside cake.

This is the reallocation to propose at almost every wedding, and it is invisible unless the menu is treated as four decisions rather than one.

🔄 Check Your Understanding

1. Why is cocktail hour the most under-budgeted moment, and what is the working figure?
2. A couple has ordered a wedding cake and a plated dessert. What do you say?

Verify

1. Because guests arrive from a ceremony, stand for 60–90 minutes with nothing to do, and drink on an empty stomach — so it is the hour they are hungriest and the one most planners treat as a garnish before the real meal. 5–7 pieces per guest, more for a longer hour.
2. That they are buying dessert twice and most guests will eat one. Cutting the plated dessert and serving the cake typically saves $6–$10 a head — $600–$1,000 at this count — which buys the cocktail hour that is currently under-catered, or the late-night food that keeps the party going. Nobody has ever noticed the missing plated dessert.

14.3 Dietary Requirements

The area with the largest gap between how seriously it is treated and how seriously it should be.

⚡ Quick Reference: four categories, four responses

Category	Examples	Response
Allergy — medical	Nut, shellfish, sesame, dairy anaphylaxis	A protocol. §below. Not a menu change
Intolerance — medical	Coeliac, lactose	A specific dish, prepared to avoid cross-contamination
Religious or observant	Halal, kosher, Hindu vegetarian, Jain	A specific dish; may require sourcing or certification. Ask, do not assume
Ethical or preference	Vegetarian, vegan, pescatarian, dislikes	A good dish, not an afterthought

The distinction that matters: an allergy is a safety issue and everything else is a hospitality issue. They are handled by different systems, and conflating them is how people get hurt.

Collecting

On the RSVP, with a specific question rather than a blank field:

"Do you have any allergies or dietary requirements we should know about? (Please be specific — we'll pass this to our caterer.)"

A blank field produces "vegetarian" and "no nuts." A prompted field produces "severe tree nut allergy, carries an EpiPen" — which is a different piece of information and requires a different response.

Then build the dietary matrix, which goes to the caterer, appears on the BEO, and appears on the seating chart.

⚡ Quick Reference: the dietary matrix

Guest	Table	Requirement	Severity	Meal	Confirmed with caterer
R. Okafor	6	Tree nut allergy	Anaphylaxis	Standard, nut-free prep	✓ 12 Aug
S. Whitfield	1	Coeliac	Medical	GF menu	✓ 12 Aug
J. Mendez	11	Vegan	Ethical	Vegan main	✓ 12 Aug
A. Novak	3	Halal	Religious	Halal-sourced	✓ 12 Aug

Three columns people omit and should not: severity, the specific meal each person is receiving, and the confirmation date.

The allergen protocol

✅ Best Practice: the four-part allergen protocol

For any guest with a medically serious allergy — anaphylaxis, carries an auto-injector — a list on a BEO is not sufficient. Four things happen:

1. The caterer's chef knows, by name and table. Not "there's a nut allergy at table six." "Rachel Okafor, table six, seat four, severe tree nut, anaphylactic."

2. The plate is marked and hand-delivered. Most caterers use a coloured pick, a different plate, or a designated server who delivers it personally and confirms the guest by name. The plate does not travel on a tray with others.

3. Someone confirms with the guest at the table. "Ms. Okafor? This is your meal — it's been prepared nut-free." Ten seconds, and it is the step that catches the plate going to the wrong seat.

4. The couple and the planner know where the auto-injector is, and whether the guest is accompanied by someone who knows how to use it.

⚕️ This is operational practice, not medical guidance. A planner is not qualified to assess allergy severity or manage a reaction. What a planner does is ensure the information reaches the kitchen accurately, the plate is controlled, and — if something happens — emergency services are called immediately (Chapter 28). Do not attempt to judge whether a reaction is serious.

🔄 Check Your Understanding

1. Why is an allergy handled differently from a vegan requirement, given that both are "dietary requirements"?
2. What are the three columns most often missing from a dietary list?

Verify

1. Because an allergy is a safety issue and a preference is a hospitality issue. A vegan guest receiving the wrong plate has a disappointing evening; an anaphylactic guest receiving the wrong plate has a medical emergency. They require different systems: a protocol with named delivery and confirmation, versus a good dish and a correct count.
2. Severity (is this medical or preference), the specific meal each person receives (not "GF option" but which dish), and the confirmation date with the caterer. Without the third, nobody knows whether the kitchen has actually seen it.

14.4 The BEO

The banquet event order is the caterer's operational document: what is served, when, to how many, with what staffing and equipment. It is the single most important piece of paper the caterer produces, and it is usually issued 2–4 weeks out.

Read it line by line. It is usually wrong in at least one place.

⚡ Quick Reference: reading a BEO

Section	Check
Date, times, location	Against your timeline — including load-in and end time
Guest count	Against your guarantee, and note whether it is guaranteed or estimated
Menu, by course	Against what was agreed, including garnishes and sides
Dietary meals	Count, and by name where possible
Bar	If they are running it — packages, hours, last call
Staffing	Numbers and hours. This is where cuts hide
Equipment	What they bring; what they expect you to supply
Setup and service times	Against the run sheet
Vendor meals	Count and timing
Rentals through the caterer	Against your rental order, to catch double-ordering
Charges	Service charge, admin fee, tax base, and every extra
Cake cutting, corkage, attendants	Present or absent

⚠️ Common Pitfall: the four things usually wrong on a BEO

1. The guest count is the estimate, not the guarantee, or it is last month's number. Always confirm which.

2. Staffing is lower than proposed. A proposal at 1:18 becomes a BEO at 1:24, because the BEO is written closer to the event when the caterer knows their staffing. This is the single most common and most consequential BEO error, and it changes your dinner duration by twenty minutes.

3. The dietary meals are miscounted or generic. "3 vegetarian" when the matrix says 3 vegan, 2 vegetarian, and 1 coeliac.

4. Equipment is assumed. The BEO lists items the caterer expects to find. Cross-check against the rental order (Chapter 13), because either something is double-ordered or something is missing.

Read the BEO with the rental order and the run sheet open beside it. Three documents, one hour, and it catches all four.

Why the BEO is wrong, and why it is not the caterer's fault

Worth understanding, because it changes how you raise it.

A BEO is written by an operations person, two to four weeks out, from a sales file that was created eight months earlier. Between those two dates: the guest count changed, the rental arrangement changed, dietary requirements arrived, and the staffing was assigned from whoever is available that Saturday.

Nobody is being careless. The document is a synthesis of information that arrived through four channels at four different times, and the person writing it has eleven other events that month.

Three consequences for how you handle it:

Send a consolidated update at −5 weeks, before the BEO is written, containing the guarantee, the dietary matrix, the equipment split, and the timeline. A BEO written from good information is usually right. A BEO written from a sales file plus scattered emails is usually not.

Raise corrections as questions, not as errors. "Which count is on your system?" rather than "the count is wrong." The operations person may know something you do not, and roughly one time in six they do.

Confirm the reissue. A corrected BEO that is agreed verbally and not reissued is a BEO that the kitchen will not see.

🎤 From the Field: the staffing line is the one to read twice

Of the four common BEO errors, three cost money and one costs the evening.

A count error is caught at invoicing. A dietary error is caught at the table, awkwardly. An equipment error is caught at load-in, expensively.

A staffing reduction is caught at 7:40 p.m., when dinner is still going out, and by then there is nothing to be done. It is invisible on the day it is written and irreversible on the day it matters.

Read the staffing line first, every time, and compare it to the proposal.

📋 The Planner's Script: correcting a BEO

Context: you have found four errors. The caterer is good and you want them to stay good.

"BEO's arrived and it's mostly right — four things to fix.

1. Guest count shows 118; our guarantee is 103. Which is on your system? 2. Staffing shows 5 service; the proposal was 6 at 1:18. I've planned dinner at 18 minutes a course on six — can we hold six, or should I move the timeline? 3. Dietary shows '4 vegetarian'; the matrix has 2 vegan, 1 vegetarian, 1 coeliac. Sending the matrix again. 4. You've listed 100 dinner plates; Sundown-supplied per our agreement, so that's yours — just confirming we're not both ordering.

Everything else looks good. Reissue when you can and I'll circulate."

Note item 2. It is phrased as a question about the timeline, not as a complaint about staffing — which gives the caterer a choice between restoring the server and telling you dinner will take longer. Either answer is useful and neither is a fight.

14.5 The Guarantee

Chapter 5 introduced it; here is the mechanism.

⚡ Quick Reference: guarantee mechanics

When due	Typically 10–14 days out; check the contract
What it is	The number you contractually agree to pay for regardless of attendance
A floor, not a ceiling	You pay for the guarantee even if fewer come
Going over	Usually accommodated, often at a premium — commonly 120–150% of the per-head rate
The overset	Most caterers prepare 3–5% above the guarantee as a matter of course
Set it at	Confirmed yes + 2–3% (Chapter 5 §5.8)

💰 Run the Numbers: the cost of being wrong

100 confirmed, loaded rate $120, late additions at 150%.

Guarantee	Actual attendance	Outcome	Cost
103	100	Paid for 3 who did not come	+$360
103	103	Correct	$0
103	108	5 late additions at $180 | **+$900**
115	100	Paid for 15 who did not come	+$1,800
95	103	8 late additions at $180 | **+$1,440**

The asymmetry is smaller than people assume in dollars and much larger in visibility. Over-guaranteeing wastes money quietly. Under-guaranteeing produces either a premium charge or — if the caterer cannot accommodate — a guest without a meal, which is a failure everyone in the room can see.

Guarantee slightly high. Never guarantee the forecast, and never guarantee the invitation count.

The non-responders

The guarantee is due before the RSVPs are complete, always, and Chapter 5's chase window is what closes the gap.

⚡ Quick Reference: what to do with a non-responder at the guarantee deadline

Situation	Treatment
Chased twice, no reply	Count as not attending. Chapter 5 §5.8 — and the couple must have been told this is the policy in advance
Replied "probably," never confirmed	Count as not attending; flag to the couple by name
Local, close family, unreachable	Count as attending. The cost of being wrong is $120; the cost of a grandmother without a chair is not
Travelling from abroad, unreachable	Count as not attending — travel this far is planned, and silence means no
An entire household non-responsive	Count as not attending, and have the couple call once more. Households do not forget; they have a reason

The rule underneath: count silence as absence, except where the person's absence would be more costly than their meal.

And then add the 2–3% on top, which is precisely the cushion for the two or three of them who arrive anyway.

⚠️ Common Pitfall: the guarantee that was never actually submitted

The deadline arrives, the planner emails a number, and the caterer's operations team is closed for the weekend or the email goes to a sales address that is not monitored.

Submit the guarantee in writing to the person named in the contract, and get an acknowledgement. Not a read receipt — a human reply confirming the number.

An unacknowledged guarantee defaults to whatever is on the caterer's system, which is frequently the estimate from month two. In the Reyes–Whitfield BEO, that number is 118 against a real count near 100 — a difference of $2,160.

14.6 Placing Dinner in the Timeline

The chapter's contribution to Chapter 25.

🕐 From the Run Sheet: dinner, family style, 100 guests

Time	What	Duration
6:20	Guests invited to move from cocktail area	—
6:20–6:34	Transition, one entrance (Ch.11 §11.4)	14 min
6:34	Seated. Welcome; blessing	4 min
6:38	First platters out	—
6:38–6:56	Family-style service, main	18 min
6:56–7:35	Eating	39 min
7:35–7:45	Clear	10 min
7:45–8:00	Toasts	15 min
8:00–8:10	Dessert out and cake cut	10 min
8:10	Dessert and coffee	—
8:30	First dance	—

Two hours and ten minutes from "please take your seats" to the first dance, and that is with the fast service style.

The same dinner, plated at 1:25: service runs 60–70 minutes instead of 18, and the first dance is at 9:20 rather than 8:30. Fifty minutes of dancing lost to a staffing ratio.

That is the sentence this chapter exists to make sayable, and it is available in month three from a proposal's staffing line.

🔍 Why Does This Work?

Why does service style dominate the evening's shape more than any other catering decision?

Because dinner is the only immovable block in the middle of a wedding, and everything after it is compressed by its length.

The end of the night is fixed — by a curfew, a contract, or a venue's staff going home. The ceremony is fixed at the front. Dinner sits between them, and every minute it runs long is a minute taken from the only part of the evening that is elastic: the dancing.

A guest asked afterward what they remember will say the food or the party. A service style that protects the food at the cost of the party is a trade, and it should be made deliberately — which is why the ranking exercise in Chapter 4 matters here, and why "food first" and "the party first" produce genuinely different dinners.

14.7 The Extras

The charges outside the per-head price (Chapter 6 §6.4), from the catering side.

⚠️ Common Pitfall: vendor meals counted from memory

The vendor matrix (Chapter 12 §12.3) has a crew-size column for exactly this reason.

At Wildrye: Sundown 10, DJ 1, photographer 2, videographer 1, florist 2 (if staying), bar 2, planner + 2 assistants = 21 meals at $35 = $735.

A planner who estimates "about twelve" is $315 short, and the shortfall appears as a caterer feeding people who were not counted — which they will do, and invoice for.

And the timing matters. Vendor meals are served after the guests are served and before the toasts, in a designated area. A crew eating at 9:30 has been working since seven in the morning.

🔄 Check Your Understanding

1. Why are vendor meals served after the guests but before the toasts, rather than at the end?
2. A BEO lists 12 vendor meals. Your vendor matrix says 21. What has probably happened, and what does it cost?

Verify

1. Because the photographer, videographer, and DJ must be working during the toasts — that is the part they cannot miss. Feeding them after the guests are served means the room is settled and nothing is happening that requires them; feeding them at the end means either they eat cold food at 9:30 after fourteen hours or they miss the toasts. It is a fifteen-minute window and it is on the run sheet.
2. The BEO count came from the sales file — probably the vendors known in month three — rather than from the current vendor matrix. Nine meals at $35 is $315, and the caterer will feed them anyway and invoice for it. Send the matrix's crew-size column with the guarantee.

14.8 Practical Considerations

Convert every staffing ratio into minutes, and put the result in the timeline.

Brief the caterer with constraints and priorities, then ask what they would cook.

Ask at the tasting: "how does this change at a hundred, in a field?"

Build the dietary matrix with severity, specific meal, and confirmation date.

Run the allergen protocol for anything medically serious.

Read the BEO with the rental order and the run sheet open.

Guarantee at confirmed yes + 2–3%.

Count vendor meals from the matrix.

Common mistakes:

1. Not converting staffing into service duration. The chapter's whole argument.
2. Selecting dishes from a list rather than briefing the constraints.
3. Treating a tasting as representative of service conditions.
4. Conflating allergies with preferences.
5. A dietary list without severity.
6. Not reading the BEO against the rental order — double-ordering or a gap.
7. Missing the BEO's reduced staffing.
8. Guaranteeing the forecast or the invitation count.
9. Estimating vendor meals.
10. Forgetting the cake-cutting fee until it appears on the invoice.

Things to do this week:

• Build the service-duration calculator: guests, tables, ratio, service path → minutes per course
• Build the dietary matrix template
• Write your allergen protocol
• Get a real BEO and read it against the checklist

14.9 Chapter Summary

Key concepts

• Food is the caterer's job. Service is a schedule, and the schedule is yours.
• Six service styles, differing on cost, staffing ratio, service duration, space, kitchen demand, waste, dietary handling, and guest experience. The two figures nobody converts are the staffing ratio and the service duration.
• Plated at 1:25 runs 45–70 minutes across three courses. Family style runs 15–20 for the whole meal. A buffet moves ~100 guests/hour per single line, and the last table sits 42 minutes after the first.
• Adding two servers to a 140-guest plated dinner saves ~20 minutes for ~$520. That is 20 minutes returned to dancing.
• Menu constraints, in order of how much they bind: the kitchen, the season, the guest count, and — last on the list and first in the conversation — the couple.
• At a raw site, the menu should be dominated by things that are better after 40 minutes than after 4. Braises, roasts, grains. Not a compromise.
• Brief the constraints and the priorities, then ask what they would cook. Worth $8–$15 a head and a better dinner.
• A tasting is four plates cooked to order. Your wedding is a hundred plates held in a field. Ask, of each dish, how it changes.
• An allergy is a safety issue; everything else is hospitality. The allergen protocol: the chef knows by name and table · the plate is marked and hand-delivered · someone confirms with the guest · the couple and planner know where the auto-injector is.
• The BEO is usually wrong in at least one place. The four: guest count is the estimate not the guarantee · staffing is lower than proposed · dietary meals are generic or miscounted · equipment is assumed. Read it with the rental order and run sheet open.
• Guarantee at confirmed yes + 2–3%. A floor, not a ceiling. Over-guaranteeing wastes money quietly; under-guaranteeing produces a guest without a meal.
• Dinner is the only immovable block in the middle of a wedding, and every minute it runs long is taken from the dancing.
• Count vendor meals from the vendor matrix. At Wildrye it is 21, not "about twelve."

Action items

• [ ] Build the service-duration calculator
• [ ] Build the dietary matrix template
• [ ] Write the allergen protocol
• [ ] Read a real BEO against the checklist

Decision framework — which service style?

1. What does the kitchen actually support? (Raw site eliminates plated-to-order)
2. What does the vision document say about the feeling of dinner?
3. Where did food rank, and where did the party rank? (These trade against each other)
4. How many dietary requirements, and how serious?
5. What is the guest profile — mobility, age, willingness to queue?
6. Convert the staffing ratio into minutes, and check the resulting first-dance time.

If step 6 produces a first dance after 9 p.m., either the style or the staffing changes.

Spaced Review

Answer before opening.

1. (From Chapter 12) What are the four reference questions, and which is the one that matters?
2. (From Chapter 6) Compute the loaded rate for a $94 menu price with a 20% service charge that is distributed to staff, and 7.75% tax on food only.
3. (Bridging) Chapter 13 said a load-in is a dependency graph. This chapter says dinner's length is set by a staffing ratio. What do the two have in common, and what does it say about where a planner's specific value lies?

What's Next

In Chapter 15: Beverage and Bar, the second half of the food and drink budget. Open bar versus consumption versus package economics, consumption forecasting by demographic and event length, bar and bartender sizing, the licensing and liability material Chapter 9 flagged, and a responsible-service plan with a named refusal authority.

Before you go on, design the menu and read the BEO. Chapter 15 builds the bar plan that sits beside it.

📐 Project Checkpoint: the Reyes–Whitfield menu and BEO

Tier 3 — Illustrative. The Reyes–Whitfield wedding is a composite created for this book.

1. Choose the service style. Sundown's proposal (Chapter 12) said "$11,800 is workable if we go family style. Plated at this count in a field would need closer to $14,000."

Run the §14.1 decision framework. Then convert the staffing into minutes for both options — Sundown proposed 7 service staff at 1:18 for 118; recompute at 100 guests — and produce the first-dance time under each.

Food is ranked first. The party is ranked second. State the trade explicitly.

2. Write the brief. The open-question version from §14.2, including the field kitchen, the 32-inch doorway, September, 100 guests, the budget, the ranking, and the vision sentence.

3. Handle the tasting. Write the question you ask of every dish, and note which of Sundown's likely proposals would fail it.

4. Build the dietary matrix. Construct plausibly for 100 guests — a typical wedding has 8–14% with some requirement. Include at least one medically serious allergy, and write the four-part protocol for that guest by name, including who confirms at the table.

5. Read the BEO. Here is Sundown's, abridged:

Date 12 Sept · Guests: 118 · Family style · Service staff: 5 · Kitchen: 2 · Lead: 1 · On site 1:00 p.m.–12:30 a.m. · Dietary: 6 vegetarian · Equipment: client to supply 13 tables, 104 chairs, all linens, 100 dinner plates, 100 sets flatware, 220 glasses · Vendor meals: 12 · Service charge 20%, tax 7.75% on food.

Find every error. There are at least five. For each: what is wrong, what it costs, and the line you write.

6. Set the guarantee. Confirmed yes is 97 with three non-responders at the deadline. What do you guarantee, and what does each alternative cost?

7. Place dinner in the timeline. Ceremony 4:30, cocktail hour on the lawn, and the venue's amplified-music curfew is 10:30 p.m. Work backward. How much dancing is there?

File it in Reyes–Whitfield. Chapter 15 builds the bar.

Chapter 14 Exercises → exercises.md

Chapter 14 Quiz → quiz.md

Case Study: Forty-Two Minutes → case-study-01.md

Case Study: One Dinner, Four Ways → case-study-02.md

Key Takeaways → key-takeaways.md

Further Reading → further-reading.md