Party quantity tables fail because they key on headcount. Guest-hours β guests Γ hours, with a fatigue curve β is the unit caterers actually use, and it explains every "the food ran out at hour three" disaster.
The fatigue curve
Consumption is not linear: guests eat and drink fastest in the first two hours (arrival hunger, social drinking), slow through the middle, and pick up slightly at "one for the road" time. The catering adjustments:
| Hour | Appetizer pieces per guest | Drinks per guest |
|---|---|---|
| Hour 1 | 3β4 | 2 |
| Hour 2 | 2β3 | 1 |
| Hours 3+ | 1β2 each | 0.5β1 each |
Style multipliers
- Cocktail party: appetizers are the meal β full 6β8 pieces per guest-hour.
- Dinner party: 3 pre-dinner pieces per guest, then plate rules (Β½ lb bone-in protein per person).
- BBQ/buffet: theδΈι΄ β 4 per guest-hour, plus the plate rules for the main window.
- Kids' parties: multiply appetizers Γ1.5 (teens), halve the variety (they eat the same five things).
The worked example
Twelve guests, three hours, cocktail style: hour one = 12 Γ 3.5 β 42 pieces; hour two = 12 Γ 2.5 β 30; hour three = 12 Γ 1.5 β 18. Total β 90 pieces β which the food calculator produces in one screen, ice included.
The history upgrade
After your third party, start a note: what you bought, what survived, what died. Your crowd's actual consumption curve beats every industry table β the tables exist to get you to that first data point, and your history is the instrument that follows.