Vegetarian and Vegan Christmas Dinner Quantities: A Mixed-Table Planner

Allocate named people before calculating food

“Five meat, two vegetarian and one vegan” is not yet a quantity plan. It does not say whether the vegetarian guests are happy with the vegan main, whether an omnivore wants to choose it too, whether somebody needs separate allergy controls, or what the exact product or complete recipe will yield.

Start with one row per accepted allocation. For every guest, record:

• their stated preference or requirement: use the guest’s own description instead of inferring it from a category;
• medical and cross-contact controls: keep allergy, intolerance and coeliac requirements separate from vegetarian or vegan preference;
• the exact accepted main: product, complete verified recipe or agreed guest-supplied dish—not merely “veggie option”;
• the planning share: a full share or another amount explicitly chosen for that known person;
• confirmation and fallback: who agreed it, what must be rechecked and what happens if that exact dish changes.

A planning share is not a nutritional standard and this page gives no universal gram weight for nut roast, Wellington, tofu, seitan or any other plant main. The real guest, exact serving claim and complete meal are stronger evidence than a generic per-person figure.

Run a second conservation check after grouping the rows: the sum of accepted guest shares must equal the sum of dinner shares across all mains. A mismatch exposes a missing row, a double allocation or a split that does not return to the guest’s chosen requirement. A guest with requirement 1 and accepted allocations of 1 meat + 1 plant is overallocated and must fail; 0.5 + 0.5 across two accepted mains returns exactly to 1.

Keep preference, vegan labelling and allergy safety separate

Current GOV.UK food-labelling guidance says there is no legal definition of vegan food in UK law, although labels must be accurate and not misleading. A vegan label means no ingredients of animal origin were intentionally used; it does not guarantee that animal-origin ingredients or allergens are absent through cross-contamination.

That creates three separate questions for every proposed plant main:

1. Does the guest accept the dish? A vegetarian may accept a vegan main, but should be asked. A vegan guest cannot be silently assigned a vegetarian dish that contains milk, egg or another animal-origin ingredient.
2. Does the exact label or recipe meet the stated preference? Recheck the physical product, full recipe and every substitution. “Plant-based” in a product name is not enough evidence by itself.
3. Do the ingredient, precautionary-allergen and kitchen controls meet the guest’s medical needs? Vegan does not mean allergen-free. A nut roast may contain nuts; a vegan product may carry a milk or egg precautionary statement; a shared utensil may break an otherwise suitable plan.

GOV.UK distinguishes a vegan claim from a “free-from” claim and says vegan labelling does not guarantee freedom from a particular allergen. Food Standards Scotland advises asking the guest, checking prepacked ingredients, keeping allergens separate, cleaning surfaces and utensils, and retaining an ingredient record. Use the fuller dietary-requirements process before writing “accepted” in the allocation sheet.

Build the guest-to-main allocation sheet

List the exact mains under consideration, then ask each guest which one they will actually eat. Do not buy first and ask later. Use these statuses consistently:

• Accepted: the guest has agreed the exact dish and any required ingredient or preparation controls.
• Provisional: a product, recipe, label, yield or cross-contact decision still needs checking. Do not count it as final coverage.
• Rejected: the guest will not eat it or it cannot meet their requirements.
• Uncovered: no accepted main allocation currently reaches that guest’s chosen requirement.
• Overallocated: accepted shares exceed that guest’s chosen requirement, usually because the same person was counted in two full dish totals.

If an omnivore wants the plant main, give them a plant-main row. If a vegetarian and vegan guest both accept one exact vegan main, they can share its yield calculation. If two guests need different controls around the same product, keep their control notes separate even when the quantity total is shared.

Do not use a backup as a second automatic allocation. A sealed guest-agreed fallback may be sensible when a requirement is hard to reproduce at home, but it remains a named contingency with its own label, storage and equipment plan—not an excuse to buy a full duplicate menu for everybody.

Convert accepted shares into exact packs or recipe batches

Once every guest is covered, total one dish at a time. Keep the unit consistent: label-sized servings with label-sized servings, or verified recipe portions with recipe portions.

The final number is arithmetic, not predicted food remaining. Appetite, carving, cooking loss, recipe execution and how a manufacturer defines “serves” can change what reaches the table. A numerical pack surplus is not automatically a safe or useful leftover.

A deliberate leftover portion in the target is planned capacity, not food guaranteed to remain. It does not become protected future food merely because it appears in the arithmetic. Protect the assigned dinner shares first; after service, only identified food with a suitable known history can enter the Christmas leftovers plan, following its exact storage, cooling, use-by and reheating evidence.

Protect every assigned main share before service. An optional taster is covered only when its explicit share was recorded inside dinner demand; never take it from the arithmetic surplus or from a guest’s protected allocation.

The exact yield must be greater than zero. Packs or batches are whole non-negative numbers; the resulting capacity must cover the target, and a minimal round-up leaves a surplus from zero up to—but not including—one more pack or whole recipe batch. Add dinner and deliberate-leftover shares in the same serving unit, then round the combined target once. Do not round the dinner and leftovers separately and add the two rounded results.

Use the exact current pack’s stated servings or a complete verified recipe yield. Do not derive servings from product weight, the size of a photograph or an unrelated recipe. If the product says “serves 2”, one pack supplies two label-sized shares for this comparison. For a range such as “serves 4–6”, preserve the complete wording and use the lower figure only when its serving unit and product state genuinely match the ledger; a target reached only at the upper end remains unresolved. If the wording is only “serves up to 6”, record the upper-bound wording but do not use six as guaranteed yield; leave conservative coverage unresolved or obtain stronger exact-product evidence. Never turn unquantified wording such as “leftovers included” into a numeric leftover allowance.

A recipe batch stays whole in this sheet. Do not schedule half a batch merely because the arithmetic produces 0.5. Use the complete verified recipe as written, or create and verify a separate scaled recipe with its own yield and instructions before treating it as evidence.

Carry the resulting whole-pack decision into the storage-first Christmas shopping plan, where a substituted pack triggers a fresh yield, ingredient, storage, equipment and cost check.

Worked example: nine adults at one mixed table

This example demonstrates allocation arithmetic, not a menu recommendation. Nine adults are eating Christmas dinner. Five have confirmed fictional meat product M. Two vegetarian guests and one vegan guest all confirm that complete verified vegan recipe A suits their preference and stated ingredient controls. One omnivore also chooses that vegan main.

Complete verified vegan recipe A yields two recipe-sized portions per whole batch. Four accepted dinner shares are assigned to it and no plant-main leftovers are requested, so ceil(4 ÷ 2) = 2 whole recipe batches. The host does not make a separate vegetarian main, because both vegetarian guests have accepted this exact complete recipe.

Both names and yields are fictional method data, and the meat product deliberately has no weight in this example. A real ledger must name and date the exact product or recipe evidence. If the chosen main is turkey, use the exact-label turkey serving-claim checker rather than copying this fixture.

Let a failed label check reopen the allocation

Suppose a substitute ingredient for vegan recipe A arrives and its precautionary label conflicts with the controls Guest G has agreed for a sesame allergy. Guest G rejects the changed recipe. That row becomes uncovered; the other three guests’ acceptance does not make that recipe suitable for Guest G.

The plant-main arithmetic is now three accepted shares against a two-portion whole recipe batch. Two batches would create a numerical one-share margin, but that margin cannot cover Guest G because the changed recipe failed the agreed control. The host must agree another exact dish and preparation route for Guest G or restore a recipe that guest accepts. The sheet must not relabel an unsuitable surplus as coverage.

Every substitution reopens five fields:

1. guest acceptance and preference;
2. ingredients, allergen emphasis and precautionary statements;
3. usable serving yield;
4. storage and appliance instructions;
5. cost and pack-rounding surplus.

If a recipe changes, recheck the whole recipe rather than only the headline ingredient. If the home kitchen cannot provide the guest’s required controls, say so early and use an agreed alternative instead of an unsupported “free from” promise.

Count shared sides once, against their actual eaters

Do not build a complete meat menu and then duplicate every side for the plant-main group. For each potato, vegetable, stuffing, gravy, sauce and dessert, ask who will actually eat that exact version.

• If all nine guests accept one exact potato recipe, count nine likely eaters once.
• If the meat gravy and vegan gravy are separate, give each its own named eaters and exact yield.
• If one stuffing contains meat and another does not, do not call the second one vegan until every ingredient and preparation condition supports that description.
• If an allergy-controlled side needs separate preparation or service, keep its quantity and utensil handover identifiable even when its ingredients resemble the shared dish.
• If an omnivore wants both gravies or two main samples, record the chosen shares rather than assuming everybody will sample everything.

Use the Christmas dinner quantity calculator for shared-side eater profiles, editable starting amounts and exact-yield pack rounding, with the general quantities guide beside it. This mixed-table sheet decides the accepted main allocations first; neither route replaces the exact recipe, product or dietary evidence for each dish.

Make storage and one-oven capacity approve the menu

A mathematically covered guest can still have an impossible meal if the accepted dish has nowhere to go or cannot be cooked under its instructions. For every main, carry forward:

• the exact unopened and after-opening storage instructions;
• the measured fridge, freezer or cupboard position;
• the exact cooking, standing and serving instructions;
• the oven shelf, hob ring, microwave or no-cook route;
• the separate equipment and serving controls agreed with the guest;
• the named fallback if a pack changes or one appliance slot disappears.

Use the four-snapshot fridge-space planner for the real packs and containers, then physically test them. Use the one-oven conflict method before putting durations into the timeline calculator. A second main is not genuinely available if it depends on the same occupied shelf at an incompatible setting.

When raw meat is also present, follow current official guidance and keep it covered and separate from ready-to-eat food and vegetables. Plant-based food is not automatically ready-to-eat: its exact storage, preparation and cooking instructions still control. Clean hands, surfaces and equipment after raw-food contact, and preserve the guest-agreed allergen controls. A plant main does not become safe through proximity to a label or through sharing an unclean utensil.

Print the two blank ledgers and write on the paper copy

These tables are static and are not editable in the browser. Use the browser’s Print command and choose paper or “Save as PDF”, then complete them by hand. The print preview includes the article; select the two blank-ledger pages if you only want the worksheets. Add rows on another printed sheet rather than compressing several guests or products into one cell.

Keep the physical packs, complete recipes and guest-agreed dietary record beside the ledgers. A filled row records a planning decision; it does not certify nutrition, allergy safety, storage, cooking or future leftovers.

Close every guest, dish and handover before shopping

Run this check while another main is still easy to change:

• Every named guest has accepted main shares that total their chosen requirement.
• Preference and medical controls are in separate fields.
• Every accepted main names an exact current product or complete verified recipe.
• Vegan, vegetarian, plant-based and free-from are not treated as interchangeable claims.
• Every dish target separates dinner allocations from deliberate leftovers.
• Every pack or batch calculation uses an exact usable yield in the same unit.
• Numerical surplus is labelled as arithmetic, not predicted food remaining.
• Shared sides are counted once against their actual accepted eaters.
• Every substitute triggers a fresh guest, label, yield, storage, equipment and cost check.
• Every main has a measured storage position, instruction-led appliance route and serving handover.

Version and human check: this is version 0.1, dated 19 August 2026. Before production reliance, complete it for a nine-person mixed table containing at least one vegan guest, one vegetarian guest, one omnivore choosing the plant main and one allergy conflict. Use two current physical plant-main packs and one complete recipe, then substitute one product. Ask a second person to confirm every guest remains covered, shared sides were not doubled, the pack arithmetic reproduces and the decisions transfer into shopping, fridge and oven plans.

Questions people ask