Start with the accepted meal, not a coloured sticker
The dietary-requirements plan should already record what the guest says they can eat, the required preparation controls and the exact current ingredients. Plating does not repair a missing agreement or unsupported “free from” promise.
Give the private event sheet a guest ID such as G-A and the plate a separate ID such as PLATE-C1. The plate marker proves only which ledger row to read; it does not prove that the food is suitable.
| Identity | What it means | What it must not reveal |
|---|---|---|
| G-A | Private event-only recipient reference | Name, diagnosis or unnecessary health detail |
| PLATE-C1 | Exact controlled plate and its current revision | A generic promise such as “safe plate” |
| DISH-M2 / SIDE-V3 | Exact approved component and batch history | An interchangeable category such as “vegan thing” |
| MARKER-C1 | Visual and tactile link to PLATE-C1 | The only evidence used for release |
Keep the working sheet private, collect the minimum information needed for this event and dispose of or retain it only under the household's agreed privacy practice. This article never needs a personal name.
Define the complete plate before service
A plate row includes the main, every side, gravy or sauce, garnish, bread, butter or alternative, condiment, serving utensil and any deliberate omission. “Same dinner without the stuffing” is incomplete if the gravy, garnish or shared spoon has not been checked.
| Field | Required evidence | Blocked example |
|---|---|---|
| Guest acceptance | G-A accepted revision R3 and its stated controls | Host inferred requirements from a label |
| Component set | Every dish and omission named by stable ID | “Normal sides” |
| Ingredient revision | Current packet or complete recipe evidence retained | Last-minute substitute unchecked |
| Preparation history | Agreed separation, clean equipment and batch identity preserved | History lost after a utensil swap |
| Plate and route | Clean plate, marker, landing point and direct recipient route staged | Anonymous plate waits beside ordinary service |
| Final handover | Food checker releases; runner reads back plate ID and recipient ID | Runner chooses by appearance |
FSA consumer advice says hosts should check ingredients, keep food covered and separate, clean equipment and surfaces thoroughly and avoid cross-contamination. Removing an offending ingredient from a finished plate or relying on ordinary heating is not a recovery method.
Choose an order that protects evidence
There is no universal instruction to plate every controlled meal first. Choose the order that the real kitchen, the guest-agreed controls and the current food evidence support. If a clean separated zone and route can be maintained, completing and handing over the controlled plates before ordinary plating may reduce later ambiguity. If the required separation cannot be maintained, change the menu or use an agreed sealed alternative rather than making a promise the kitchen cannot support.
- Close unrelated preparation and clear the supported plating zone.
- Verify the current plate ledger revision and retained ingredient evidence.
- Stage only the named clean plates, markers and dedicated utensils for that controlled run.
- Add components in the recorded order, checking each dish ID before it crosses the plate boundary.
- Complete the garnish, gravy, condiment and omission checks—blank is unknown, not “none”.
- Final checker releases one plate; runner carries it directly to its intended recipient.
- Close the row before another plate or ordinary service uses the route.
Do not let a delayed ordinary side hold a complete controlled plate in an anonymous queue. Either preserve the supported waiting state agreed for the exact food or mark the plate BLOCKED and rebuild the service decision.
Worked ten-person plating and release ledger
This fictional ten-place rehearsal has eight standard rows and two separately controlled rows. It demonstrates identity conservation, not a menu or medical plan another household should copy.
| Plate row | Component state | Marker and route | Release state |
|---|---|---|---|
| PLATE-C1 → G-A | M2 + V1 + V2 + P1; gravy G2; garnish NONE recorded | MARKER-C1; LAND-CONTROL → SEAT-A | READY only after checker reads R3 and runner reads back C1 / G-A |
| PLATE-C2 → G-B | M3 + V1 + V3 + P2; gravy decision blank | MARKER-C2; route staged but closed | BLOCKED—GRAVY UNKNOWN; do not copy G2 from C1 |
| PLATE-S1–S8 | Standard component set R2 | Ordinary service route opens after controlled handovers close | QUEUED; no row may borrow C1 or C2 utensils |
| Exception E1 | Runner notices C1 and C2 markers have been swapped | Both plates return to their separate labelled landing points | STOP C1 + C2; checker resolves identity from ledger, not food appearance |
The ledger begins with ten intended recipients and ends with ten resolved recipient states: eight queued standard rows, one releasable controlled row and one blocked controlled row. A blocked plate is not silently counted as served.
Keep markers attached to evidence
Use a marker system the intended helpers and guest can distinguish in the real light and room: a large printed plate ID, a stable place card, or another agreed visual and tactile method. Colour alone can be misread, and a marker placed beside several plates can move.
- Marker carries the plate ID and revision, not a diagnosis or personal name.
- Marker remains physically linked to the plate until direct handover.
- Guest or agreed recipient reference is stored on the private ledger.
- Runner confirms both plate ID and destination before lifting.
- Recipient is told which plate is theirs and retains the final decision to accept it.
- Any detached, duplicated, obscured or swapped marker stops the affected plate.
Do not publish a seating plan that exposes private dietary information. SEAT-A is an event route reference, not a public map of a guest's health or beliefs.
Control the last metre and the last spoon
Carry the plate through the route tested in the serving-dish capacity plan and keep it out of the dirty-return flow in the Christmas Day kitchen reset. The final metre includes the landing point, doorway, chair movement, table edge and any person likely to add gravy, garnish or a shared spoon.
| Change signal | Required state | Next action |
|---|---|---|
| Ingredient or pack substitution | BLOCKED—REVISION CHANGED | Recheck exact label and guest acceptance; issue a new plate revision |
| Utensil moved between dishes | BLOCKED—HISTORY UNKNOWN | Stop affected dish and plates; named food owner resolves or replaces |
| Unrecorded garnish, butter, sauce or gravy | BLOCKED—COMPONENT UNKNOWN | Do not add it or scrape it off; rebuild from the supported decision |
| Plate marker detached or swapped | BLOCKED—IDENTITY UNKNOWN | Return to separate landing point; resolve from ledger |
| Recipient changes seat | ROUTE CHANGED—RECONFIRM | Update private destination and runner read-back before carrying |
Food-business allergen guidance is cited for its useful dish-specific ingredient and service controls, not as private-home legal advice. The home plan still depends on the guest conversation, exact ingredients and controls the household can genuinely maintain.
Hand over a complete job without handing over the food decision
Build the runner assignment in the Christmas job handover validator. Its job is narrow: collect an explicitly released plate, read back its ID and destination, follow the current route, hand it directly to the intended recipient and report completion or an exception.
The runner does not choose substitutions, decide that two plates look equivalent, add missing gravy, remove a garnish, resolve a lost utensil or reassure a guest about ingredients. Those decisions return to the food checker and, where needed, the guest.
Close the row only after the intended recipient receives the matching plate and knows it is theirs. A plate left on a side surface is still in transit.
Run the cold plate-swap rehearsal
- Use ten clean empty plates or safe cold stand-ins, two controlled plate IDs, ten private guest IDs and the real service route.
- Stage every named dish, gravy, garnish and omission as a labelled card; no food or health information is required.
- Have the food checker release PLATE-C1 while PLATE-C2 remains blocked by one blank component.
- Give the runner the current handover card, then swap the two markers, move G-A to another seat and place an unrecorded garnish card beside C1.
- The runner must stop both affected plates, refuse the garnish, return the changed route and resolve identity from the ledger without guessing.
- Restart with a new revision and confirm that all ten intended recipients end in exactly one handed-over, queued, blocked or replaced state.
The cold rehearsal proves only that IDs, markers, read-backs, route capacity and stop rules can work in the staged layout. It does not prove ingredient suitability, allergen control, cooking, holding, temperature, medical safety or a guest's acceptance of the real meal.
- Every controlled plate has an accepted complete component set.
- Every plate marker remains attached and legible without relying on colour alone.
- Every runner reads back plate ID, revision and private destination.
- Every change signal blocks release until its owner resolves it.
- Every intended recipient appears in exactly one current ledger state.
Questions people ask
Should dietary plates be served first?
Only when the guest-agreed controls, clean zone, exact food and direct route support that order. There is no universal first-plate rule. If the kitchen cannot maintain the required separation, change the menu or use an agreed alternative rather than improvising.
Can I identify a dietary plate with a coloured sticker?
A marker can link the plate to its ledger row, but colour alone is weak and the marker is not suitability evidence. Use a stable plate ID and revision that helpers can distinguish in the real light, and stop if it moves or becomes unclear.
Can I remove an unsuitable garnish from the plate?
Do not treat removal as recovery for an allergy or other agreed cross-contact control. Stop the plate and rebuild the decision using clean supported equipment and the guest-agreed plan.
What should the plate runner know?
Only the minimum needed: released plate ID, current revision, private recipient ID or destination, route, no-additions rule and exception return. The runner does not need a diagnosis or personal name.
Does a cold plate rehearsal prove the meal is suitable?
No. It tests IDs, markers, sequence, route and read-back. Suitability still depends on the guest conversation, current ingredients, real preparation and service history, official guidance and the guest’s decision.
Sources and checks
- Food Standards Agency — food allergy and intolerance advice for consumers — current household ingredient checks, communication, separation, cleaning, cross-contamination and why removal or heating is not recovery
- Food Standards Agency — allergen guidance for food businesses — dish-specific ingredient information, labelled containers, clean utensils and service controls; used as process context, not private-home legal advice
- Food Standards Agency — avoiding cross-contamination — current household guidance on clean preparation surfaces, separate equipment and safe handling
- GOV.UK — fire safety when celebrating — official England guidance on keeping guest escape routes clear; not a plate-route dimension standard