Recipe Scaling for Events: Portion Math Beyond Multiplication

A recipe that serves 4 doesn't always serve 200 if you multiply every ingredient by 50. Seasoning, cooking time, equipment capacity, batch behaviour and waste — they all break linearity at scale. The chefs who run events well aren't faster at multiplication; they know which numbers to round, which to under-scale, and which equipment constraint is about to become the bottleneck. Here's the working framework.

The seven things that break when you just multiply

1. Salt and aggressive seasoning

Salt scales sub-linearly. A 4-portion stew that calls for 8 g of salt does not need 400 g for 200 portions — somewhere between 250 and 320 g will taste correct. The same is true of chilli, garlic, anchovy, fish sauce, smoked paprika, anything that intensifies as the dish concentrates over a longer cook (which is what happens at scale — bigger pots, longer cook time, more reduction).

Practical rule: scale "aggressive" seasonings to 70-85% of the multiplied amount initially, then taste and adjust. It is always easier to add salt than to remove it.

2. Cooking time

A casserole that braises 4 portions in 90 minutes does not braise 200 portions in 90 minutes. Larger volumes take longer to come to temperature, longer to reach equilibrium, and the centre of a 50-litre pot is genuinely cooler than the centre of a 5-litre pot for the first hour.

Practical rule: scaled-up braises and slow cooks typically need 30-60% more time, with active stirring or repositioning of large pieces. Scaled-up baking and roasting often needs less time per item because thermal mass evens out — but the oven also takes longer to recover after the door opens, so plan to load and not re-open.

3. Equipment capacity

Your stove has 6 burners. Your largest pot is 30 litres. Your oven holds 4 gastronorms. None of those numbers care about your recipe. If you scaled your demi-glace recipe by 25× and the result is 60 litres of reduction needed in one stockpot, you don't have a pot for it.

This isn't usually addressed in the recipe — it's an equipment audit that happens before scaling. Cap each component's scaled volume to what your equipment can actually handle in a reasonable time window; split into batches above that cap; schedule the batches into your prep timeline.

4. Cooling, holding, and reheating

Small batches cool fast; large batches don't. Scaling a recipe past about 15× typically means the dish moves into hot-hold (in a chafer, water bath, or warmer) for service, which changes texture. Pasta that was perfect al dente at 4 portions becomes soggy at 200 if held for the same service window. Sauces split. Vegetables overcook by carry-over.

The fix usually involves slightly under-cooking the component knowing it'll finish during holding — but this requires testing once at scale to calibrate. Don't guess on event day.

5. Waste behaviour

Small batches have low waste because you measure precisely. Large batches have predictable waste: the residue left in the pot after pouring, the ingredient you measured generously because the scale was busy, the sauce that sticks to the kitchen container during transfer to the chafer. USDA food waste research consistently shows banquet operations run higher per-portion waste than à la carte for exactly these reasons.

Practical rule: add a 5-8% buffer to scaled ingredient quantities for "operational waste" (not customer-facing waste, just normal handling loss at scale). Above 100 portions this becomes essential rather than optional.

6. Acid, leavening, and chemistry

Baking is the most obvious case. A cake that uses 1 tsp baking powder per 4 portions does not need 50 tsp for 200 portions — you'll get a stripped, bitter result. Leavening, acidic adjustments (vinegar, lemon), and yeast all scale sub-linearly. For pastry and bread at event scale, work from professional bakery recipes (calibrated for kilos) rather than scaled home recipes.

For savoury chemistry: emulsions (hollandaise, mayonnaise) become unstable above a certain volume — split into multiple smaller batches rather than one giant one, and hold separately.

7. Service speed

The recipe scales. The service window doesn't always. A 4-portion plating that takes 90 seconds per cover scales to 200 covers in 5 hours of plating — but your service window is 90 minutes. This means more plating stations, simpler plating, or buffet/family-style format rather than à la carte at scale.

This is a menu-design implication, not a recipe-scaling implication: choose dishes that can be plated quickly or held safely at volume. The recipe that wins on a 4-cover tasting menu is often the worst possible choice for a 200-cover wedding.

Scaling factors: the simple part

The arithmetic part of scaling is straightforward:

A recipe that bases at 4 portions, scaled to 60 covers, has a factor of 15. Multiply each ingredient line by 15, with the seven adjustments above as overrides.

For a multi-recipe event (8 dishes, 80 covers each, but some dishes for some covers only), the better mental model is:

• Each dish has its own target portion count for the event (not always equal to total covers — e.g. only 60 of 80 guests will eat the lamb if salmon is also offered)
• Each ingredient's total required quantity = sum across all dishes that use it, each scaled to its dish's portion count
• This aggregated quantity drives the shopping list, not the per-dish recipe view

The aggregation step is where sub-recipes matter: a salsa that appears in three different dishes needs to be ordered/prepped at the combined quantity, not at the per-dish quantity. Manual scaling gets this wrong consistently; structured scaling does it automatically.

The shopping-list cascade

Scaled recipes produce scaled ingredient lists. Combine those into a single shopping list for the event:

1. Scale each recipe to its target portion count for the event
2. Expand sub-recipes down to base ingredients (labneh ingredient list, not "1 portion labneh")
3. Aggregate by ingredient across all dishes (chicken thigh from dish A + dish C = total chicken thigh needed)
4. Apply yield % adjustment — your supplier delivers AP weight, your recipe needs EP. Order AP = EP needed ÷ yield %
5. Add 5-8% operational buffer for waste at scale
6. Group by supplier and category for placing orders

This is the part that's almost impossible to do reliably on a clipboard for an 8-dish 200-cover event. Either you under-order (and run out of garlic at 13:00 the day of) or you over-order (and bin food next week).

What this looks like in practice

What to do this week

1. Pick your most recent event. Look at the recipes you used and the portions served.
2. Re-cost them through a proper scaling process. Apply yield %, operational buffer, sub-recipe expansion.
3. Compare to what you actually ordered and used. Where did you over-order? Where did you under-order and emergency-buy? Both are quantifiable losses.
4. For your next event, scale up front using the structured process. Aim to land within ±5% of actual usage.
5. After the event, weigh waste per dish. Refine your scaling factors and buffer % for the next event.

This is a two-event learning loop. By event three your numbers will be substantially more accurate than guesswork, and your food cost on catering will drop several points.

The point

Scaling a recipe is multiplication. Scaling an event is a system: dependency mapping, equipment capacity audit, sub-recipe expansion, ingredient aggregation, yield-aware ordering, operational buffer, and service-time constraints. Each is a small adjustment; together they're the difference between a catering operation that makes money and one that does not.

The chefs who run profitable events aren't more talented. They're more structured. The recipe is the smallest part of the work.