Run one transition through three observable states
Start with the selected room revision from the Christmas table proof. Mark the route, service landing, dirty-return point and every occupied place. Then give the transition three states that everyone can see.
| State | What may move | Exit evidence |
|---|---|---|
| STARTER-OPEN | Accepted starter vessels, direct plates and starter refills | Every place has finished, retained or declined starter service; no starter load remains in flight |
| RESET-OPEN | Identified dirty returns, controlled-utensil holds and named place-reset objects | Returns are admitted, required places are complete, landing is clear and the route owner closes reset traffic |
| MAIN-OPEN | Only explicitly released main plates, vessels and runners | The main service plan controls each later close or refill |
Close starter service before clearing begins
The table owner asks whether each place has finished, wants to retain an item or has declined the remaining starter service. Do not infer completion from a pause, an empty-looking plate or another guest standing up.
- Stop new starter refills and close every starter runner release.
- Account for each starter vessel, plate, utensil and private marker.
- Separate items a guest is still using from the return collection.
- Keep any controlled serving utensil linked to its exact dish ID and history.
- Record spills, dropped objects or unidentified items as exceptions instead of hiding them in a stack.
- Declare STARTER-CLOSED only when nothing from starter service remains in flight.
A starter plate is not automatically a signal that the guest is ready for the main. The table owner closes this course; the food lead separately decides when main food has the required evidence.
Admit dirty returns without crossing the main route
Use the zones and admission rules from the Christmas Day kitchen reset. Give each starter return one current destination before it leaves the table.
| Return class | Destination | Stop condition |
|---|---|---|
| Ordinary crockery and cutlery | Named dirty-return landing within its tested stack limit | Landing full, unstable, unidentified or blocking another route |
| Glassware retained for main | Remains at the same accepted place | Damage, spill, guest request or changed table revision |
| Controlled vessel or utensil | HOLD-CONTROL with exact dish ID and owner | Marker detached, identity uncertain or mixed with ordinary returns |
| Food remainder | Named food decision point | Unknown history, unsupported destination or missing owner |
| Spill or breakage | Isolated exception area under the household response | Any person, food or route remains exposed |
Never send dirty starter plates through an active main-food landing. If both movements need the same narrow route, the lower-priority movement waits in its rehearsed supported state.
Reset each place from the accepted main definition
A reset is not “make the table look complete.” It is a comparison between the current place and the accepted main-place definition.
| Place field | Reset question | Evidence |
|---|---|---|
| Seat and access | Is the occupied chair state and required access still the proved revision? | Chair, personal item and necessary route checked |
| Plate or place | Will a main plate arrive directly, or does this place need staged crockery? | Matches the current plating and service plan |
| Cutlery | Which exact clean items does this menu and guest decision require? | Present, suitable and not borrowed from another place |
| Glass and water | Is the retained glass acceptable and the water route still available? | Guest choice and table-owner check |
| Private control | Does a controlled plate have its private recipient route? | Marker, plate ID and private destination remain linked |
| Shared footprint | Do the planned main vessels and utensils fit the tested table state? | Exact empty or safely weighted rehearsal passed |
Do not add decorative objects during RESET-OPEN unless they belong to the proved main footprint. A free-looking patch of table may be the landing required by a jug, bowl or direct plate handover.
Keep main readiness independent of table speed
The table can be reset while main food remains ACTIVE or BLOCKED. Carry the food, vessel, plate, route and communication rows from the final 30-minute dependency sheet.
- The food lead applies the exact recipe, packet or supported official checks.
- The vessel owner matches actual released food with a verified vessel, utensil and route.
- The plate owner keeps controlled components and private recipient destinations explicit.
- The table owner proves the current place set, service landing and guest route.
- The route owner confirms reset traffic is closed and no dirty return remains in flight.
- The communications owner gives a conditional update when any dependency remains blocked.
Do not invent a holding duration so the table can catch up, and do not hurry an unsupported food row because guests are seated. If the table becomes ready first, preserve it. If food becomes ready first, use only the exact supported plan and instructions while the blocked table dependency is resolved.
Worked two-table transition ledger
This fictional cold rehearsal extends the two-table service plan. It tests objects, identities and routes; it is not a food-holding plan.
| Checkpoint | TABLE-A | TABLE-B | Combined decision |
|---|---|---|---|
| Starter close | A-STARTER-CLOSED | One retained spoon; B still open | RESET-OPEN remains blocked for B collection |
| Controlled utensil | UT-C1 moved to HOLD-CONTROL | No controlled return | Identity preserved; ordinary stack cannot accept UT-C1 |
| Dirty route | A return load admitted | B return load waiting at supported table landing | One shared route admits one identified load |
| Place reset | Six main places READY | Five READY; B4 cutlery missing | TABLE-B remains RESET-OPEN |
| Main release | Food row BLOCKED—CHECK NOT ACCEPTED | Controlled plate C2 marker linked | No main load released to either table |
| Restart | A route and places rechecked | B4 resolved; B reset traffic closed | MAIN-OPEN still waits for independent food evidence |
Table A finishing first does not let its main service cross Table B’s active dirty route. The route revision and food release must support the next movement, even when every A place looks ready.
Give helpers bounded reset jobs
Use the job handover validator for each complete assignment. “Clear the table” is not complete enough because it omits scope, destinations, exceptions and finish evidence.
| Job | Scope | Finish evidence | Must return |
|---|---|---|---|
| Starter closer | Confirm each place state and declare no starter load in flight | STARTER-CLOSED read back | Guest still using item, unclaimed dish or new request |
| Return runner | Carry one identified return load on the current route | Named landing owner accepts it | Blocked route, unstable stack or unidentified item |
| Place checker | Compare assigned places with the main-place definition | Every field READY or explicit exception returned | Missing object, changed chair or uncertain private control |
| Route closer | Account for reset traffic and clear the service landing | RESET-TRAFFIC-CLOSED read back | Any dirty load or person remains in flight |
Helpers report state; they do not decide that food is safe, alter a controlled plate, substitute an item or open MAIN-OPEN because the planned time arrived.
Rehearse a blocked return and delayed main release
- Stage the real starter and main place definitions, both table states, empty or safely cold-weighted vessels, controlled markers and all route landings.
- Run STARTER-OPEN to STARTER-CLOSED using one owner per table and account for every object.
- Admit identified dirty loads, hold controlled utensils separately and reset each place against the main definition.
- Block the dirty-return route, swap one controlled-utensil marker and issue a delayed main-food release card.
- The team must stop the affected loads, preserve identities, keep MAIN-OPEN closed and issue only the approved conditional guest update.
- Resolve the route and marker, close reset traffic, then keep waiting until the independent main-food evidence is accepted.
- Repeat with one helper removed and revise any assignment that no longer has a supported owner.
The cold rehearsal tests course states, object accounting, table definitions, routes, exceptions, handovers and communication. It does not prove cooking, food temperature, holding, cleaning effectiveness, allergen control or the suitability of a hot vessel.
After the main, continue with the Christmas dessert service reset so leftovers, chilled access and controlled dessert variants receive their own evidence instead of inheriting this transition.
Questions people ask
How do I clear the Christmas table between starter and main?
Close starter service first, then give every returned object a named destination. Reset each place against the accepted main definition, close all reset traffic and reopen the incoming route only when table, route, vessel, plate and food evidence are ready.
Should guests keep the same cutlery for Christmas dinner?
Use the accepted menu and place definition to decide what clean, suitable items are required. Do not borrow from another place or reuse a controlled utensil whose identity and history matter.
Can the main come out while starter plates are still being cleared?
Only if the real service and return routes are separate and the tested plan supports both movements. Otherwise close dirty-return traffic and clear the incoming landing before releasing main loads.
What if the table is ready but Christmas dinner is delayed?
Keep the proved table state and give guests a conditional update. Do not invent a holding time or upgrade a food row because the table is ready; follow exact instructions and wait for the named food evidence.
How do I reset two Christmas tables?
Close and account for each table independently, preserve separate return histories and use one shared route only for one identified load at a time. Neither table opens main service until its reset closes and the shared food dependencies support release.
Sources and checks
- Food Standards Agency — cleaning — current household guidance on clean utensils, dishes, surfaces, cloths and avoiding sink clutter
- Food Standards Agency — avoiding cross-contamination — current household guidance on clean areas, separate equipment, spills and supported handling
- Food Standards Agency — food allergy and intolerance advice for consumers — household ingredient checks, separation, cleaning, cross-contamination and guest communication
- GOV.UK — fire safety when celebrating — official England guidance on keeping guest escape routes clear; not a table or service dimension standard