Choose what the food is replacing
An arrival canapé, sandwich lunch, fork buffet and late snack are different promises. Select one primary format before requesting quotes:
- Canapés before another meal: a short bridge, not the complete offer.
- Canapés as the meal: the pieces collectively form a substantial route.
- Sandwich buffet: filled bread plus named savoury, salad, fruit or sweet components.
- Fork buffet: named mains, starches, vegetables or salads and desserts.
Use the buffet calculator for a visible starting estimate. Its rates are Unflustered Host planning assumptions, not catering standards, nutrition advice or a supplier guarantee. Replace them with the real menu, guest replies and exact quote before ordering.
Keep a later snack, cake table or gift hamper as a separate release. Hidden extras can duplicate a full meal and also affect the commercial and HMRC cost records.
Preserve confirmed, working and maximum attendance
Use the guest scenario planner without entering names. In the fictional example, 44 adults are confirmed and six are pending. With a visible 50% pending-attendance assumption:
- confirmed minimum: 44 people;
- working scenario: 44 + ceiling(6 × 50%) = 47 people;
- maximum: 50 people.
Real headcount controls room capacity, chairs, plates, water, access and evacuation arrangements. The working scenario may support an order decision, but it does not turn 47 into a safe venue limit or prove what any person will eat.
Attach the RSVP deadline, supplier change deadline, minimum charge and consequence of shortage to the chosen scenario. When replies change, update the source count before changing the order.
Give every dish its own selector count
A guest may select two sides but only one main. A vegan label does not tell you how many people prefer that dish, and an omnivore may select it too. Record a separate likely-selector count for every exact dish using the current menu replies.
Dish target = likely selectors × chosen prepared unit per selector + named extra
Whole packs = ceiling(dish target ÷ exact prepared yield per identical pack)
Arithmetic surplus = whole packs × exact prepared yield − dish target
Keep pieces, prepared grams, prepared millilitres or clearly defined portions on the same basis from target to supplier yield. “One tray serves 10” is usable only when the supplier defines the portion and the tray is prepared and served in the same way.
Worked example: a fictional 47-person fork buffet
This example demonstrates arithmetic for the 47-person working scenario. Its menu, rates, selectors and tray yields are fictional evidence fields, not recommended UK catering quantities.
| Dish | Target | Exact example yield | Whole trays | Purchased | Arithmetic surplus |
|---|---|---|---|---|---|
| MAIN-01 other main | 36 selectors × 1 = 36 portions | 10 prepared portions/tray | 4 | 40 portions | 4 portions |
| MAIN-02 plant main | 11 selectors × 1 = 11 portions | 4 prepared portions/tray | 3 | 12 portions | 1 portion |
| SIDE-01 potato dish | 42 selectors × 180 g = 7,560 g | 2,000 g prepared/tray | 4 | 8,000 g | 440 g |
| SIDE-02 vegetable dish | 39 selectors × 120 g = 4,680 g | 1,500 g prepared/tray | 4 | 6,000 g | 1,320 g |
| SWEET-01 dessert | 40 selectors × 1 = 40 portions | 12 portions/tray | 4 | 48 portions | 8 portions |
The two main rows cover 47 intended selections: 36 + 11. The side counts overlap because a person can choose both. Purchased surplus is not proof that food should be prepared, displayed, saved or treated as a suitable fallback.
Make the caterer prove the order basis
For every item, request the exact product or recipe identity, prepared tray yield, portion definition, ingredient and allergen information, substitution process, delivery state, storage instructions, preparation or reheating method, service equipment and minimum order.
FSA guidance for food businesses says allergen information must be accurate, procedures should update it when recipes or ingredients change, and staff should know how to answer questions and serve food to the correct customer. A price-matched substitute is therefore not an automatic like-for-like quantity or suitability match.
Block the affected row when a supplier changes ingredients, pack size, recipe, prepared yield or method. Confirm the new evidence and recalculate; do not preserve the old number because the dish name is unchanged.
Keep dietary data private and suitability operational
Dietary and access answers may reveal health, religion or other special-category information. The ICO’s own event notice shows one lawful process, but another employer must identify and document its own lawful basis, Article 9 condition where required, access controls and retention period. Do not copy the ICO’s consent choice as a universal answer.
Give the caterer the minimum information needed to deliver the agreed controls—often neutral counts or order IDs rather than a staff list. Keep identity-to-requirement mapping with the minimum authorised team. Do not place names or medical details on a shared quantity sheet or public buffet card.
Quantity coverage and suitability are different. A dish can have enough portions overall while a person has no suitable substantial route. Confirm the exact current information with the relevant guest and caterer before closing the order.
Plan delivery, storage and buffet batches
Attach delivery time, receiving owner, count and temperature checks required by the caterer’s method, cold and hot capacity, serving surfaces, utensils, batch IDs, refill owner and close state to the order. The calculator cannot prove that 17 trays fit the venue or its equipment.
Release food in traceable batches rather than merging old and new histories. Preserve exact instructions and the caterer’s food-safety system. The FSA’s party and event guidance provides official hygiene and allergen routes, but this page does not invent a universal display time, holding temperature or reheating method.
Use the Christmas buffet service ledger for batch release and the office party checklist for venue, responsibility and incident boundaries.
Print the office-party food order register
| Dish ID | Exact dish / unit | Selectors | Unit each | Target | Exact tray yield | Trays | Surplus | Suitability evidence | Batch / owner |
|---|---|---|---|---|---|---|---|---|---|
Rehearse three changes: all six pending replies become confirmed, one tray yield changes and one suitable main is substituted with an unsupported recipe. Another organiser should update the affected rows, stop the unsupported dish and preserve every real headcount and private-data boundary without verbal coaching.
Questions people ask
How much food do I need for an office Christmas party?
Choose the food format and attendance scenario first. Then calculate each exact dish from likely selectors, an explicit prepared unit and the real yield of one caterer tray or identical pack. There is no reliable universal amount for every office event.
Should I order office-party food for invited or confirmed staff?
Preserve confirmed, working and maximum attendance, then choose the scenario against the supplier deadline and consequence of shortage. Keep real maximum headcount for venue and service capacity regardless of the food-order assumption.
How much buffet food is needed for 50 office guests?
Do not multiply every alternative by 50. Count likely selectors for each main and side, use exact prepared units and round against the caterer’s actual tray yields. The 47-person worked example demonstrates the method but is not a recommended menu.
Do vegetarian or vegan options need separate selector counts?
Every exact dish needs its own selector count, including choices that may be selected by people without that dietary preference. A vegetarian or vegan description does not prove allergen suitability.
What if the caterer changes a dish or tray size?
Block that row, obtain the new recipe or product, allergen information, prepared yield and instructions, then recalculate. Do not reuse the old tray count simply because the replacement has the same menu name.
Should employee dietary requirements appear on the order sheet?
Use neutral operational counts and IDs where possible. Keep identity-to-requirement information inside the employer’s authorised process, document the lawful basis and special-category condition where required, and restrict access and retention.
Sources and checks
- GOV.UK — running a food business: allergies — current accurate-information, recipe-change, correct-customer, cross-contamination and staff-training requirements for food businesses
- Food Standards Agency — allergen checklist for food businesses — updated 23 July 2026; manager, kitchen and front-of-house allergen information and cross-contamination prompts
- Food Standards Agency — eating out, parties and events — official food hygiene, rating, allergy and event-guidance routes; exact caterer evidence remains controlling
- ICO — rules on special-category data — necessity, proportionality, Article 9 conditions and data-minimisation boundary for sensitive requirements
- ICO — event, seminar and workshop privacy notice — authoritative example of purpose, dietary and access data, controlled sharing and retention; its lawful basis is not presented as universal