Choose the eating occasion before the dishes
Write what guests can reasonably expect: pre-dinner nibbles, a substantial canapé reception, a meal-replacement buffet, a seated supper, dessert after guests have eaten elsewhere or a deliberately late main service. Add the arrival waves, main food window, midnight plan, later finish and any accepted overnight state.
Do not allow attractive variety to blur the promise. Nibbles do not become dinner because there are six bowls, while a complete evening buffet does not automatically need another full meal at 00:15. State the decision in the invitation.
Use current product labels, complete recipes, guest requirements and exact storage and cooking instructions. A dish name or theme does not establish suitability, quantity, usable yield or safe service.
Four arrival and canapé menus
| Menu | Structure | Works when | Prove first |
|---|---|---|---|
| 1. Pre-dinner nibbles | Two savoury bowls, vegetables with one identified dip and water or alcohol-free drinks | Guests have been explicitly told this is not a meal | Invitation wording, exact ingredients, utensils and a short controlled service state |
| 2. Cold canapé reception | Three savoury families, one substantial cold item and one portioned sweet | The event promise and guest routes can be met without hot service | Cold capacity, item identities, exact pieces, landing space and refill batches |
| 3. Hot-and-cold canapé evening | Cold arrival wave, two supported hot releases and a sweet close | The oven and helper plan can release small batches from exact instructions | Appliance slots, carried route, release evidence, utensils and dirty returns |
| 4. Bowl-food route | Two small savoury bowls, one complete equivalent and a compact dessert | Guests can hold and eat the exact dishes in the planned room state | Stable bowls, spoons, portion release, seating options, collection and washing-up |
Canapé arithmetic depends on whether the pieces welcome guests or replace a meal. Use a visible format and duration assumption, then convert every exact item into current whole-pack yields. Do not merge hot and cold batches into one history.
Four buffet menus
| Menu | Structure | Useful constraint | Failure to avoid |
|---|---|---|---|
| 5. Sandwich and salad buffet | Two identified sandwich families, one complete alternative, two salads, fruit and sweet | A short cold menu with measured fridge and table space | Mixed platters whose ingredients, selectors and refill histories disappear |
| 6. Baked-potato bar | One supported potato route, three separately identified toppings, salad and dessert | A hot base plus visible independently controlled choices | Assuming every topping is suitable or every potato batch fits at once |
| 7. Pie or tray-bake supper | Two complete savoury routes, two compatible sides and portioned dessert | Fewer large-format dishes suit the actual pans and oven | Ordering by tray name rather than current usable portions and instructions |
| 8. Soup, bread and topping station | Two soups, controlled breads and toppings, followed by a simple sweet | The room supports bowls and the kitchen supports the exact hot route | Unproved holding, unstable bowls, shared ladles or unidentified toppings |
Build each buffet dish as a separate row. “One buffet for 24” hides who is likely to select each main, which sides overlap, what the exact packs yield and when each batch leaves controlled storage.
Four supper and midnight menus
| Menu | Structure | Primary promise | Midnight decision |
|---|---|---|---|
| 9. One-pot supper and complete alternative | One main, one equivalent route, two compatible sides and dessert | A deliberately short seated or bowl-food meal | Water and a small separately calculated sweet or savoury release only if needed |
| 10. Build-your-own supper | One base, two fillings, toppings and sides kept as identified components | Guests choose from a complete visible component map | Close components from their real histories; do not reopen the whole bar automatically |
| 11. Dessert and hot-drinks party | Two complete dessert routes, fruit, hot drinks, water and alcohol-free choices | Guests have been told to eat dinner before arriving | The dessert is the midnight food; no second unplanned meal is implied |
| 12. Late supper after an organised display | One supported make-ahead main route, complete equivalent and compact dessert | The actual return time, storage and final cooking or reheating route are controlled | Delay or cancellation activates a supported alternative, not indefinite holding |
A build-your-own table does not move the control decision to guests. Preserve exact information, preparation, utensils and contact boundaries per component. A public-display return time is projected until the organiser, travel and actual group state support it.
Give every requirement a complete equivalent route
Collect only the practical food information needed, through a private route. For each recorded requirement, test whether the proposed dishes cover the same promised eating occasion. One side salad is not automatically equivalent to a substantial main and fruit is not automatically equivalent to every dessert route.
| Route | Complete evidence | Keep distinct |
|---|---|---|
| Plant-based | Current labels or complete recipes cover the promised main, sides and later wave | Preparation, pans, utensils, service position and substitution |
| Food hypersensitivity | Accurate ingredients and known preparation allow an informed guest decision | Private requirement, contact controls, packaging and release owner |
| Child route | The responsible adult accepts the exact food and preparation for that child | Age-specific preparation, texture, portion and supervision |
| Late arrival | A named supported batch remains within its exact storage and instruction route | Arrival state, batch history and actual release |
The Food Standards Agency encourages useful ingredient and allergen information so guests can make informed choices. Registered food businesses have specific duties; this household menu guide does not classify the event or provider. Check the exact organised, commercial or venue context separately.
Build a fictional 24-person menu across three waves
This example has 20 people arriving by 20:00, four arriving later and all 24 potentially present at midnight. The approved promise is a meal-replacement buffet followed by a small sweet midnight release. It demonstrates conservation, not recommended dishes or portions.
| Wave / dish | Role | Likely selectors | Current-yield field | Batch decision |
|---|---|---|---|---|
| Evening MAIN-01 | Complete savoury route A | 16 | ___ portions per exact tray or recipe | Two batches only if instructions and capacity support them |
| Evening MAIN-02 | Complete savoury route B | 8 | ___ portions per exact tray or recipe | Separate identity, vessel, utensil and release |
| Evening SIDE-01 | Prepared potato side | 20 | ___ g usable per exact pack | Small refill from controlled reserve |
| Evening SIDE-02 | Salad | 15 | ___ g usable per exact pack or recipe | Named chilled batches |
| Evening SWEET-01 | Dessert | 18 | ___ pieces per exact pack or recipe | Covered reserve until dessert state |
| Midnight SWEET-02 | Small separate release | 14 | ___ pieces per exact pack or recipe | Not the evening dessert surplus |
The two mains total 24 selectors. The side totals are independent because guests may select several or none. The midnight row has 14 selectors rather than repeating 24 automatically. Use the quantity worksheet to convert each accepted target into exact whole packs.
Preserve every food history through midnight
Map each item through acquisition, use-by evidence, storage, preparation, cooking or no-cook route, service vessel, release, refill and final state. Follow exact current instructions and keep raw and ready-to-eat routes separate. Use small named batches only where the product, facilities and plan support them.
Midnight does not reset a storage, temperature, service or opened-container history. Never top a fresh batch onto an older platter and erase the distinction. At close, decide unopened, supported leftover, discard or another valid state from actual evidence—not from arithmetic surplus.
Test the real fridge, oven, hob, worktops, serving table, guest routes and dirty returns. Keep the games clear state and the timeline connected to every batch release.
Print the New Year’s Eve menu register
| Wave / dish ID | Menu role | Selectors | Exact product or recipe | Usable yield / packs | Requirement control | Storage / batch / final state |
|---|---|---|---|---|---|---|
Build one current menu, then move the four late arrivals to declined, substitute one pack, remove one fridge shelf and delay the final wave past midnight. Another person must change only affected selectors and packs, preserve every batch history and refuse any route whose exact evidence no longer works.
Questions people ask
What food should I serve at a New Year’s Eve party?
Choose whether the event offers nibbles, substantial canapés, a buffet, seated supper, dessert or a late main service. Then select a short menu with complete equivalent routes that fits the actual guests, storage, kitchen, room and timeline.
What are easy New Year’s Eve buffet ideas?
A sandwich-and-salad buffet, baked-potato bar, two-tray supper or soup station can reduce variety, but only when exact ingredients, usable yields, preparation, utensils, storage and service batches are supported.
What food should be served at midnight?
Only add a midnight wave if it fulfils a defined need. It might be a small sweet, a planned savoury snack or the delayed main meal. Calculate its own likely selectors rather than repeating the whole event headcount automatically.
How do I cater for late arrivals?
Give late arrivals a separate timing group and a named supported food batch. Preserve its exact storage and preparation history; do not hold an uncontrolled plate or count those guests twice.
How many dishes should a New Year buffet have?
There is no universal number. Use the smallest set that fulfils the stated meal promise, gives known requirements complete equivalent routes and can be stored, prepared, identified, served and cleared in the real event.
Can buffet leftovers become the midnight snack?
Only after a deliberate allocation supported by exact identity, suitability, storage, service history and current instructions. Arithmetic surplus or food remaining on an uncontrolled table is not enough evidence.
Sources and checks
- Food Standards Agency — how to safely host a street party — party food hygiene, chilled food, cooking, separation, use-by and allergen-information prompts
- Food Standards Agency — providing food at community and charity events — updated 4 September 2026; current registration, allergen, hygiene, use-by and chilled-food boundaries for organised contexts
- Food Standards Agency — chilling — current household and food-business cold-storage, cooling and fridge-temperature route
- Food Standards Agency — allergen guidance for food businesses — individual-dish buffet information and cross-contamination controls for food businesses; the household legal context remains separate
- NHS — foods to avoid giving babies and young children — age-specific food and preparation boundaries; the responsible adult and exact child remain controlling