The short version
Event-planning formulas — one drink per guest per hour, six ounces of protein per person, six chairs per banquet round — are averages across hypothetical people. Your guests aren't hypothetical. With real preference data, the math changes, the spend drops, and the event works for the room you actually have. Here's the framework, plus worked examples for the planning moments that matter most.
The industry formula lies to you, quietly
Pick up any wedding-planning book, catering primer, or dinner-party guide and you'll find the same template:
- 1 drink per guest per hour
- 6 oz of protein per person
- 0.5 cups of each side per person
- 150 sq ft per table of 8
- 3 passed appetizers per guest during cocktail hour
These numbers aren't wrong, exactly. They're averages across an imaginary guest list where everyone drinks, everyone eats meat, nobody has dietary restrictions, nobody uses a mobility aid, and everyone stays for the full event. In reality, your list has people who don't drink, don't eat certain things, can't climb stairs, need to leave by 9 — and the averages quietly over-budget for some while under-serving others.
The math that accounts for your real guests is just as simple. It just requires one extra input: the distribution of preferences in your actual guest list.
The core formula
The replacement template is straightforward:
(total guests) × (percentage who participate in this item) × (per-person amount) × (duration) + contingency
The percentage-who-participate is the part the industry formulas skip. Examples:
- For alcohol, the percentage who drink. Usually 60–80% of adults at a typical event; lower at religious-observant weddings, recovery-heavy gatherings, or pregnancy-heavy seasons of life.
- For meat-based mains, the percentage who eat meat. Roughly 90–95% for typical adult groups in the US, lower for younger and urban-heavy guest lists.
- For stairs or second-floor venues, the percentage who can comfortably navigate them. If your dad just had hip surgery and your grandma is 86, your real number isn't 100%.
The percentage is a single number pulled from your actual guest list. You can collect it from RSVPs, a pre-event questionnaire, or a preferences app like Pref. (Pref's whole point is making this data portable — guests share once, hosts and planners see exactly the cohort split they need for the math.)
Four planning moments where preference math saves you real money
1. Alcohol for a wedding
The most-overbuied category at weddings. The old “drink-per-guest-per-hour” math assumes 100% of guests drink at the same rate — which the actual bar tab never reflects. Factor in the 20–30% of adults who don't drink on a given night, the distribution of beer-vs-wine-vs-spirits preference, and the drop-off in hour four, and the alcohol budget can shrink by 25–35% without a single guest going thirsty.
See how much alcohol for a wedding — the preference-based formula for the worked math, including the dry-bar and signature-cocktail considerations.
2. Food for a dinner party
At the 6-to-12-guest dinner-party scale, the dietary distribution is usually visible in advance (it's your friends; you know them). The mistake most hosts make is cooking the full protein amount times the full head count, then over-buying sides because they've heard that's safer. Running the real math — real protein only for real meat-eaters, extra side portions for the vegetarians who will eat more of them — gets you a better, fuller table with less leftovers guilt.
For the specific calculation and the “half-cup per side per guest” nuance, see the full breakdown.
3. Thanksgiving (and other holiday meals) with mixed restrictions
The Thanksgiving table is where preference-aware planning does its best work, because the structure of the holiday — a turkey plus many sides — is inclusive by default. With two small menu choices (gluten-free stuffing instead of wheat stuffing, one plant-based main alongside the bird), 95% of Thanksgiving tables can feed every dietary profile in the extended family from the same spread. The trap is over-reacting with a separate “special plate” for the vegan cousin.
The full holiday-planning worked example covers the turkey math, the side substitutions, and the cross-contact protocols for allergic family members.
4. Seating charts that account for real humans
Seating software gives you a grid. The grid doesn't know that your uncle's hearing aid struggles with echoing rooms, that your college roommate is shy around her mother-in-law, that the vegan couple wants to sit near the gluten-free table for solidarity, or that your grandma needs to be within eyeshot of the exit. The actual seating chart is an optimization problem with dozens of preference constraints — and a thoughtful planner treats those constraints as the primary input, not as exceptions to the grid.
A dedicated worked example of preference-aware seating is on the calendar for this pillar — we'll link it here when it ships.
What preference data to collect, specifically
You don't need everyone's full life story. For a typical event, five pieces of data per guest are enough:
- Drinks: does this person drink alcohol at events? (yes / sometimes / no) Plus a beer/wine/spirits lean if they do.
- Food restrictions. Dietary practice (vegan, vegetarian, pescatarian, kosher, halal), allergies, intolerances, strong dislikes.
- Access needs. Stairs, mobility aids, vision or hearing accommodations, sensory sensitivities.
- Arrival / departure constraints. Kids to put to bed at 8pm? Partner driving from out of town? Religious observance that ends the night at sunset?
- Tier of relationship. Close family, close friend, colleague, plus-one. Drives who needs to be within earshot of whom.
Those five data points per guest, collected once, drive the entire event plan. That's Pref's whole thesis in one paragraph: the data lives with the guest, the host or planner pulls exactly the slice they need, the math improves.
The loop: collect, calculate, decide, adjust
A full preference-aware planning loop for a medium-to-large event looks like this:
- Collect.Ask — via RSVP, a short questionnaire, or a preferences app — for the five data points above. Don't ask for more than you'll use.
- Calculate.Run the numbers against the formulas in the linked posts. For bigger events, a spreadsheet that lets you toggle “what if 10% of RSVPs come in vegetarian” is worth the hour of setup.
- Decide.Buy, book, or reserve from the calculated numbers plus the 10% contingency. Resist the urge to over-buy “just in case” — the preference-based numbers already account for your specific guests.
- Adjust.As RSVPs come in, the distribution shifts. Recalculate once at the 80% RSVP mark and once at the 95% mark; do not adjust continuously (you'll go crazy).
The output is an event that feels like it was built for the guests you have — because it was.
Why this matters
Most of the wedding industry, the party-planning industry, and the catering industry is built around the assumption of an average guest, because they don't know your specific guests. You do. The difference between a generic event and an event that fits the room is the difference between average planning and preference-aware planning.
The three worked examples linked below are the quickest way to see the system at work. Start with the one closest to the event you're currently planning — the math transfers cleanly to the others.
- How Much Alcohol for a Wedding: The Preference-Based Formula
- How Much Food to Cook for a Dinner Party (A Real Calculation)
- Thanksgiving With Mixed Dietary Restrictions: The Real-World Plan
For the broader philosophy of hosting from which this planning framework descends, see The Art of Being a Thoughtful Host: A Field Guide. For how individual preferences — vegan, celiac, sober, service animal — work at scale, browse the preferences catalog.
