Christmas worked example

Christmas Dinner for Twelve: Quantities, Split Service and Capacity Plan

Twelve diners turn a menu into a service system. Quantities must fit current packs, cold storage and exact equipment; finished food may need smaller identified vessel loads; two seating candidates need complete routes; and the final window must still work when one helper disappears.

Calculate twelve transparent side targets

This worked case enters twelve diners in the Christmas dinner quantity calculator, keeps the six visible editable rates and adds no named leftovers.

DishEditable rateTwelve-person targetBasis
Potatoes250 g3,000 gRaw potatoes
Vegetables160 g1,920 g combinedCombined raw vegetables
Stuffing75 g900 gPrepared stuffing
Gravy150 ml1,800 mlPrepared gravy
Pigs in blankets2 pieces24 piecesWhole pieces
Sauce30 ml360 mlPrepared sauce

The 1,920 g vegetable target is one combined total. It does not authorize 1,920 g of carrots plus 1,920 g of parsnips plus another 1,920 g of greens. Change eaters and rates dish by dish for the real guest list.

Use exact pack arithmetic without promising leftovers

These retailer pages were captured on 3 September 2026 and must be rechecked against the live listing and physical pack before purchase.

TargetCaptured productArithmeticBoundary
3,000 g raw potatoesTesco Maris Piper Potatoes 2.5 kgceil(3,000 ÷ 2,500) = 2 packs5,000 g bought; 2,000 g raw arithmetic surplus—not cooked leftovers
24 pigs in blanketsTesco 12 Pigs in Blankets 240 gceil(24 ÷ 12) = 2 packs24 bought pieces; zero piece-rounding surplus

The raw-potato surplus is large enough to trigger a deliberate decision: find a smaller accepted pack combination on the same raw basis, allocate a named raw-food purpose under its real storage and date conditions, or accept the spend without calling it Boxing Day food. Do not increase the cooked batch merely to empty the bags.

Dry stuffing mix and gravy granules remain incompatible with prepared-gram and prepared-millilitre targets until exact current instructions provide the supported yields.

Prove one twelve-place table against two six-place tables

Build two full revisions in the room and table proof. Candidate A is one real twelve-place arrangement. Candidate B is two real six-place tables with a defined social, access and service connection.

DecisionCandidate A: one tableCandidate B: two tables
PlacesTwelve complete settings, chair states and agreed access needsSix complete settings on each table; private seat IDs allocated deliberately
FurnitureEvery leaf, support, lock and maker limit checkedBoth tables independently stable; no improvised bridge
Guest routeAll occupied chairs, doors and bathroom or escape routes passInter-table route remains open with both groups seated
ServiceReach or owner-led service proven for all twelveDuplicate small loads or sequenced owner service proven
Dirty returnStarts only after incoming service closesBoth return routes merge at one named non-conflicting point
StatusBLOCKED until full rehearsalBLOCKED until full rehearsal

Two tables are not an automatic overflow solution. They can double water, serving, plate and communication movements. Choose only a candidate that passes at one shared guest and service revision.

If Candidate B passes, continue into the two-table Christmas dinner service plan to give both cells complete water, vessel, runner, refill, controlled-plate and dirty-return evidence.

Make cold storage decide the menu ceiling

Measure every exact pack and final container in the four-snapshot fridge planner.

SnapshotTwelve-person pressure pointReduction if blocked
S1 shoppingLarger pack count plus normal household foodChange shop sequence or menu before purchase
S2 defrostingExact main and containment may dominate protected spaceChoose only a supported main and defrost route that fit
S3 make-aheadFinished containers can exceed their raw-pack footprintRemove a make-ahead dish or change supported batch/container plan
S4 leftoversMore portions need lids, labels and real cold positionsAdmit only evidence-backed batches; do not reserve imaginary space

If any snapshot has a definite conflict, the twelve-person menu fails before oven scheduling. Area under 100% is still not proof that real boxes fit; stage every shelf state physically.

Split service loads, not food histories

A twelve-person finished batch may not belong in one public bowl or jug. Use the serving-vessel register to prove smaller working fills on the exact finished basis.

Worked intentionProposed service splitEvidence still required
1,800 ml prepared gravyThree 600 ml public or sequenced loadsExact variants and yields, cold-tested jug fills, hot suitability, pan method and refill histories
3,000 g raw potatoesNo bowl split yetActual finished yield on the same basis before any vessel allocation
1,920 g combined raw vegetablesSeparate named vegetablesEach exact finished yield and vessel; never pour all vegetables into one total by arithmetic
24 pigs in blanketsTwo smaller platter loads proposedActual completed pieces, working footprints, utensils and reserve service history

Three 600 ml gravy loads sum to the 1,800 ml intention, but that arithmetic does not prove a recipe, holding method or table time. Keep reserve and public batches separate and never top new food onto an older remainder.

Prove oven and hob states from exact products

Twelve side targets do not create a schedule. Copy exact product, complete recipe, cookware and appliance instructions, then resolve the oven and hob as linked resources.

  • The main block remains UNKNOWN until its exact cut, size, tray, method and checks exist.
  • Potato and stuffing targets remain UNKNOWN until finished methods and tray footprints exist.
  • Both captured pigs-in-blankets packs require current physical-label checks and a proven tray state.
  • Every pan’s base, body, handle, lid, utensil, control and loaded transfer must fit its whole hob state.
  • One lost ring blocks every dependent pan row; use only a preverified alternative.
  • No batch is split merely to fit unless the exact food method supports that batch size and route.

Use the one-oven method and hob capacity plan. Keep unsupported timings and sharing permission unknown.

Design the final window for one fewer helper

Twelve guests can tempt the host to assign many narrow errands. Give each helper one complete job with a trigger, scope, resources, finish evidence, stop rules and fallback, then prove the final retained plan with one helper removed.

Carry those accepted jobs into the final-30-minute control sheet, where actual food checks, vessel readiness, table state, plate release and the guest update share one current revision.

JobNormal ownerHelper-loss fallback
Table and waterTable owner closes one selected room revisionComplete earlier or reduce decorative work; food lead does not absorb it during checks
Vessels and refillsService owner verifies IDs, working fills and triggersUse fewer smaller owner-led loads; remove optional public vessels
Controlled platesPlate runner carries only released IDsFood checker performs direct handover after other service pauses
Guest updateCommunications owner sends approved copyOne prewritten conditional message; no guessed time

Never remove a food check, dietary control, clean route or honest status update to compensate for the lost helper. Remove optional dishes or decoration and sequence the remaining complete jobs.

Run the twelve-person system rehearsal

  1. Recheck both dated product pages and physical packs; preserve raw, prepared and piece bases.
  2. Stage Candidate A with twelve places, then Candidate B with two complete six-place tables using identical guest and service needs.
  3. Physically pack all four fridge snapshots with exact products and final containers.
  4. Build instruction-led oven and hob states, leaving every missing product, method or duration UNKNOWN.
  5. Stage all empty or safely cold-weighted vessel loads and direct controlled-plate routes.
  6. Remove one helper, block one ring, fail the main check and close one table route.
  7. The team must reduce optional work, propagate unknown times, preserve batch identities and issue one conditional update.

The rehearsal tests arithmetic, furniture, storage, equipment, routes, loads, ownership and handovers. It does not prove prices, availability, appetite, cooking, holding, temperature, allergen control or food safety.

Questions people ask

How many potatoes do I need for twelve people?

The editable starting assumption gives 3,000 g raw potatoes. Two captured 2.5 kg packs would buy 5,000 g, creating 2,000 g raw arithmetic surplus; recheck current packs and choose the accepted combination deliberately.

How much gravy do I need for twelve?

The editable starting assumption gives 1,800 ml prepared gravy. Three proposed 600 ml service loads reconcile that intention, but exact recipes, dietary variants, pan methods, jug fills and refill histories still need proof.

How many pigs in blankets do I need for twelve?

The editable starting rate gives 24 pieces. Two captured 12-piece packs match the target arithmetically with no piece-rounding surplus; physical labels and exact instructions still control.

Is one table or two tables better for twelve?

Neither by default. Stage both complete arrangements with all places, access needs, vessels, service, dirty returns and escape routes, then choose only a fully passing revision.

Can I cook the twelve-person menu in smaller batches?

Only when the exact food, cookware and appliance instructions support the batch sizes and the storage, timing and service histories remain complete. Do not split a method merely to make the equipment plan fit.

Sources and checks

Planning with someone?

Send them this page. The link opens the original guide or blank tool, not your entered details or results.