chef-menu-event-planning

# Chef Menu & Event Planning Events fail on logistics, not cooking: three dishes needing the oven at once, a host trapped at the stove, portions off by half. This skill is production planning — the menu is an engineering document. Read `references/banquet-math.md` for portion tables, timelines, and buffet layouts. ## Menu design laws 1. **The oven-burner budget.** Every dish reserves equipment+attention. Rule: per event, at most ONE dish demanding à-la-minute attention; everything else make-ahead, hold-warm, or room-temp. Draft menu → write equipment column → resolve conflicts BEFORE shopping. 2. **Make-ahead ladder:** desserts & sauces (1–2 days ahead) → braises/stews (better ahead — schedule the improvement) → salads-components (day-of morning, dress last) → starch & sear (final hour). Menus should climb this ladder: the more guests, the more dishes from the top rungs. 3. **Contrast architecture** (chain `chef-flavor-balance`): across the menu vary temperature, texture, weight, color, and cooking method. Two cream sauces = one too many; fried starter + fried main = fatigue. Classic arc: bright/acidic start → rich center → fresh reset (salad/sorbet slot) → sweet landing. 4. **One wow is enough.** One ambitious centerpiece + reliable supporting dishes beats five medium stunts. The centerpiece gets the attention budget; sides must be autopilot dishes you've made before. NEVER debut a dish at an event — rehearse once. 5. **Dietary sweep upfront:** ask about restrictions at invitation time, design the base menu so the strictest guest eats well without a "special sad plate" (strategy in `diet-restrictions-allergens`). ## Portion math (full tables in references) Per adult at a multi-dish table: protein 150–200 g raw total, sides 200–250 g, salads 100–150 g, dessert 100–120 g. Buffet/zakuski-style: more variety, same totals +10% safety. Long parties (4 h+) +20%. Kids ≈ half. When dishes are many, people eat less of each — the “but everyone must try everything” table over-caters by 50%: cook fewer dishes, better. ## The timeline method (the actual superpower) Build backwards from serving time, in writing: - T∓2 days: shop, desserts, sauces, brines. T−1: braises, marinating, salad components, table set. T−4 h: mise en place everything (bowls, labeled). T−1 h: starches, reheats begin, sear window. T−0: plate & serve. - Every entry has dish + action + equipment. If two entries collide on the same oven — the menu changes NOW, not at 6 pm. - Include a “host margin”: 30 min of nothing scheduled before guests arrive. If the timeline has no empty slot, the menu is too big — cut one dish (nobody ever noticed a missing side). ## Plating & serving (home-realistic) - **Plated courses:** warm plates (oven 60°C / hot-water rinse); sauce under protein; height beats spread; odd numbers; wipe rims; 80% of the plate's beauty is a clean rim and one fresh green element. Practice-plate ONE dish, serve the rest family-style — the hybrid that looks generous and stays sane. - **Family style:** big boards/platters, garnished (herbs, lemon wedges, flake salt) — abundance is its own aesthetic; serving spoons for everything; carve proteins in the kitchen unless the carve IS the show. - **Buffet physics:** plates at start, cutlery at end; sauce next to its dish; tall items back, saucy items with rims; a separate drinks station AWAY from food (kills the main bottleneck); label allergens on little cards — guests quietly thank you. - Temperature safety on buffets: 2-hour rule for the danger zone — split dishes into half-batches and swap fresh from oven/fridge instead of one big dying platter (details in `chef-food-safety`). ## Drinks & extras Chain `chef-beverage-pairing` for the drinks plan (per-guest math lives there). Bread and butter on the table buys the host 20 minutes. Coffee/tea service after dessert — planned, with the kettle descaled and cups located BEFORE the event, not during.