The guest changed the order. Did the kitchen hear it?

Imagine a guest changing one sandwich after the waiter has sent the order. The waiter tells a colleague. The colleague calls into the kitchen. Two sandwiches arrive, and neither person at the pass knows which instruction is current.

To reduce kitchen order ticket errors, give each order one identifier, make item choices explicit and require acknowledgement of amendments. A new message should explain what changed and which earlier instruction it replaces.

Make the original instruction complete

A kitchen order ticket, often called a KOT, carries preparation instructions. It needs an order or table reference, item quantity, relevant choices and a sent time. Agree names for modifiers such as portion size or a requested omission. Avoid abbreviations that mean different things to different stations.

Square's modifier documentation describes options appearing on kitchen tickets. The broader lesson is to test what the kitchen actually receives, not only what the waiter sees on a screen.

Allergy requests require the restaurant's trained safety process and direct confirmation. A note on a ticket alone is not assurance that a dish can be prepared safely.

Use a change message with an acknowledgement

This is an original example for a routine preference change, not an allergy instruction.

Keep the earlier instruction visible in the history, marked as replaced where the system supports it. Do not send an unlabelled duplicate ticket and hope the kitchen recognises it as a correction.

Decide what to do when preparation has started

The service lead and kitchen lead need a shared rule for changes that are too late. Check whether the request can still be met safely, what additional time or cost applies, and who explains that to the guest. Do not promise an immediate replacement before checking the station.

If a remake creates waste, record the real reason. Toast's waste tracker includes preparation mistakes among trackable reasons. The waste-log guide helps separate ordering errors from overproduction.

Check the plate at the pass

Choose who matches the finished dish to the current ticket. That person checks the table or order reference and relevant choices before the runner takes it. A second shouted instruction should not silently overrule the recorded one.

Use the shift handover guide when the person owning an open order changes. Unfinished amendments must travel with the order, not stay in the outgoing waiter's memory.

Practise failure before a busy service

Run a pretend order, a normal change, a cancellation and a duplicate print. If the printer or network fails, follow a numbered paper fallback with one owner. Reconcile those records before re-entering anything, so the same food is not prepared twice.

Keep the drill short and use fictional guest details. The opening checklist provides a place for the device check and fallback supplies.