Ticket accuracy: where the wrong plate comes from

A plate goes back to the kitchen. The steak was ordered medium rare and arrived medium; or the salad came with the dressing the guest asked to leave off; or the table received a risotto nobody ordered. The kitchen blames the floor, the floor blames the kitchen, the dish is remade and the evening moves on. Next week, the same thing happens again.

Wrong plates rarely come from nowhere. Each one starts at a particular step: the order, the ticket or the pass. Ticket accuracy, the share of tickets that reach the kitchen correct and are cooked as written, depends on all three, and improving it starts with knowing which step each mistake comes from.

This guide covers where wrong plates come from, how to trace each one to its step, how to record mistakes so patterns appear, and the single change that fixes most of them in most kitchens. Every venue and figure in it is an example.

Ticket accuracy is the share of orders that reach the guest exactly as they asked for them. A kitchen with high ticket accuracy sends almost every plate out right the first time; one with low ticket accuracy remakes dishes every service, wastes food and keeps guests waiting.

It is a wider idea than the kitchen's own accuracy. A cook can cook a ticket perfectly and still send out the wrong plate, because the ticket itself was wrong. Order accuracy, the accuracy of what was entered at the table, is the first link in the chain.

Thinking about ticket accuracy as a chain, from the guest's words to the plate in front of them, stops the argument about who is to blame and starts the work of finding where the chain breaks.

Every wrong plate starts in one of three places. At the order: the server mishears, enters the wrong dish, forgets a change or puts it in the wrong place. At the ticket: the order is right, but the ticket shows it in a way the cook misses or misreads. At the pass: the ticket is right and the dish is cooked correctly, but it is plated wrongly, matched to the wrong table or sent out missing a part.

Each place needs a different fix. Training the kitchen will not fix order mistakes; better tickets will not fix pass mistakes. Without knowing where each mistake starts, a venue fixes the wrong thing.

The first job is therefore to trace each wrong plate back to its step, as soon after it happens as possible, while people still remember.

Order mistakes are often the largest group. A server takes an order at a noisy table, writes "no on" for no onions and enters it as a note the kitchen misreads. A guest changes their mind and the change never reaches the till. A server presses the wrong button on a busy screen and sends the wrong dish.

Some are mistakes of hearing, some of memory and some of the system. A till that makes a common change easy to enter, as a modifier the server taps, reduces all three. A till that forces the server to type every change invites mistakes of spelling and interpretation.

Order mistakes are also the cheapest to prevent, because they can be caught at the table before anything is cooked.

Ticket mistakes happen when the order is right but the cook does not see it correctly. A change printed at the bottom of the ticket, an allergy that looks like every other note, an abbreviation only the server understands, or two of the same dish with different changes shown as one line: each is a mistake the ticket design invites.

Modifiers on the ticket are the most common source. A change that does not appear directly under its dish, in a form that stands out, is likely to be missed by a cook reading in a second. Our guide to modifiers on the ticket: no onions, really covers how each change should appear.

Kitchen tickets are designed once and read thousands of times, so time spent on their design pays back every service.

Pass mistakes happen after the cooking is done. The right dish is plated wrongly, a side is forgotten, a sauce is missing, a plate goes to the wrong table or the wrong seat. Busy passes, unclear table numbers and runners who do not know the dishes all make pass mistakes more likely.

The pass is also where many mistakes from earlier steps can be caught. A pass that checks every plate against its ticket can stop a dish with onions before it reaches a guest who asked for none, even if the mistake started at the order.

That makes the pass both a source of mistakes and the last defence against all of them.

Missed orders are a special kind of mistake: the dish is never cooked at all. The order was entered but never sent, the ticket was printed but lost, or the ticket was sent to the wrong station. The guest waits, and the first sign of the problem is their question.

Missed orders do not appear as wrong plates, so they are easy to leave out of the count. Record them anyway, with their cause: not sent, lost, sent to the wrong place, or forgotten at a held course that was never fired.

A kitchen screen removes many of the causes of lost tickets, and a check at the pass for tables waiting too long catches most of the rest.

When a plate comes back, ask three questions in order. Was the order right? Look at what was entered against what the guest says they asked for. Was the ticket right, and clear? Look at the ticket and how the change appeared. Was the dish cooked and plated as the ticket said? Ask the cook and the pass.

The answers point to the step. If the order was wrong, it is an order mistake. If the order was right but the ticket was unclear or misread, it is a ticket mistake. If the ticket was right and clear but the plate was wrong, it is a pass or cooking mistake.

Do it without blame. The point is to find the step, not the person, and a team that fears blame will hide mistakes rather than trace them. The approach is a simple form of root cause analysis, applied to a plate.

A single mistake tells you little. A month of mistakes, each with its step and its cause, tells you a great deal. Keep a simple record: the date, the dish, what was wrong, the step it started at and the cause.

The record can be a sheet at the pass, a note in the till or a column in a spreadsheet. What matters is that every mistake is recorded, including the ones caught at the pass before they reached the guest, and the missed orders.

Review the record each week. Patterns appear quickly: one dish that is often wrong, one station, one hour, one kind of change, one server who needs more help.

Many mistakes on one dish often point to the dish itself: too many options, a confusing name, a change guests often ask for that is not set up as a modifier. Fix the dish, its options or its description.

Many mistakes with removals point to the ticket: removals do not stand out. Many mistakes with cooking points point to the order: the choice is not required, or the words for it vary. Many mistakes at one hour point to pressure: too many tables ordering at once, a stretched pass.

Many mistakes from one server usually point to training or to a section that is too large, not to carelessness. Look at the conditions before looking at the person.

In most kitchens, the single change that fixes the largest share of wrong plates is at the order: a read-back. Before the order is sent, the server reads back every dish with its changes and any allergy, and the guest confirms.

A read-back catches mishearing, forgotten changes and wrong dishes while the guest is still at the table, before anything is cooked. It takes seconds, and it turns the guest into the first check in the chain.

It works best with a till that makes changes easy to enter as modifiers, so what the server reads back is exactly what the kitchen will see. Combined with clear tickets and a checking pass, it fixes most of the chain.

Some mistakes start before the order, in the menu itself. Two dishes with similar names, such as a chicken salad and a chicken Caesar, are confused at the table and on the till. A dish with many options invites wrong choices. A description that does not say what comes with the dish leads guests to ask for changes the kitchen does not expect.

When the record shows many mistakes on one dish, look at the dish before the people. A clearer name, fewer options, a better description or a choice set up properly on the till can remove a whole category of mistakes for good, which no amount of training can.

Look at the till's layout too. Dishes grouped in an order that differs from the menu, buttons with shortened names or two dishes side by side with similar labels all make it easier to press the wrong one. A till laid out like the menu, with full names, is easier to use correctly at speed.

Mistakes are rarely spread evenly through a service. They cluster at the busiest hour, when servers are stretched and the kitchen is full, and at handovers, when one server passes tables to another or a new cook takes over a station.

Record the time of each mistake as well as its cause. If most fall between eight and nine, the fix may be more people at the busiest hour, fewer tables seated at once or a second person at the pass. If many fall at handovers, a short spoken handover, table by table, may fix more than any change to the tickets.

When guests order from their phones, order accuracy changes. Guests choose their own options, so mishearing disappears, but new mistakes appear: a guest who misreads a description, picks the wrong size or puts an allergy in a free-text note rather than telling the server.

Make the menu clear: descriptions that say what the dish is, options that are easy to understand, required choices that cannot be skipped. Ask guests to tell a server about allergies as well as noting them, and have servers check orders with allergies at the table.

A guest's own order is often more accurate than one taken by a busy server, as long as the menu helps them get it right.

Changes made after the order has reached the kitchen are a common source of wrong plates. A guest swaps a side, a server voids a dish entered by mistake, a table adds a dish to a course that has already been fired. Each change has to reach the right cook before the dish is made.

If changes are shouted across the pass or sent as a separate slip, they are often missed. The safest approach is for the change to show on the original ticket, with the old line struck through, so the cook sees what has changed at the moment they look. Record changes after sending as their own cause in your log, because they need their own fix.

A pass that checks every plate against its ticket is the last defence against every kind of mistake. The person running the pass looks at each plate, compares it with the ticket, checks removals and allergies especially, and sends it out only when it matches.

That check takes seconds per plate, and it needs a clear ticket and a clear view of the table's order. It also needs authority: the person at the pass must be able to stop a plate and send it back, whoever cooked it.

Record what the pass catches as well as what reaches the guest. Mistakes caught at the pass are still mistakes, and they show where the chain broke earlier.

Not all mistakes are equal. A steak cooked medium instead of medium rare is a disappointment; a dish containing an allergen served to a guest who declared it is a danger. Allergy mistakes, including near misses caught at the pass, should be treated as the most serious category in your record and reviewed every time.

Trace each one through the whole chain: how the allergy was recorded, how it appeared on the ticket, how the dish was prepared and how it was checked. Our guide to an allergy mistake: the next ten minutes covers what to do when one reaches the guest.

Every wrong plate costs a remake: the food, the cook's time, the station's capacity and the guest's patience. A remake at a busy hour can delay other tables, so one mistake becomes several late plates.

Count remakes each week, and estimate their cost: the food cost of the dishes remade, plus the time. A kitchen remaking a dozen dishes a night on its busiest nights is losing more than it might think, in food, in time and in guests who do not come back.

Falling remakes are one of the clearest signs that ticket accuracy is improving.

Training should follow the chain. Servers learn how to take an order accurately: listening, using modifiers, reading back, recording allergies properly. Cooks learn how to read a ticket fully before starting. The pass learns how to check each plate and when to stop one.

Practise with the patterns your record shows. If removals are often missed, practise orders with removals. If cooking points are often wrong, practise taking and reading them.

Share the record with the team, without names. A team that can see mistakes falling becomes a team that cares about keeping them low.

An invented bistro remakes about ten dishes on a busy night. The kitchen thinks the floor is careless; the floor thinks the kitchen does not read the tickets. The manager starts a simple record at the pass: every wrong plate and missed order, with its step and its cause.

After a month, the pattern is clear. More than half the mistakes start at the order, mostly forgotten changes and misheard cooking points. Most of the rest are removals missed on the ticket, which prints changes at the bottom. A handful start at the pass, nearly all at the busiest hour.

The bistro introduces a read-back at every table, sets cooking points as a required choice, changes its tickets so removals appear under their dish, and adds a second person to the pass at the busiest hour. A month later, remakes on busy nights have fallen to two or three.

In servearound, a dish's options are chosen from the choices set on the dish, its variants and add-ons, by the server on the till or by the guest on the table's QR code menu, and the till offers the dish's own ingredients to take off, so removals arrive in the same words every time. On the kitchen screen, each dish shows its options beneath it, its allergens, in red where they match the guest's allergies, each removal as a red "No" line and its note, with the guest's allergies at the head of the ticket. A dish voided after it was sent stays on the ticket, struck through, so the line stops cooking it.

A dish sent back is re-fired from the check as a remake, with a reason, and the guest is not charged again; a void can carry a reason too. Order analytics then show the void rate, the comp rate, remade lines and checks with a remake, kitchen analytics show the remake rate and the remakes at each station, and payment analytics show voids and comps by member of staff. See Order Fulfillment and Analytics.

The share of orders that reach the guest exactly as they asked for them, from the order through the ticket to the pass.

In many kitchens, at the order: misheard changes, forgotten changes and wrong dishes. Record yours to find out.

Ask whether the order was right, whether the ticket was right and clear, and whether the dish was cooked and plated as the ticket said.

A read-back at the table before the order is sent, with changes entered as modifiers.

Yes. A dish never cooked is a mistake too, and its causes are different.

Every plate against its ticket, especially removals and allergies, with the authority to stop a plate.

It removes mishearing, but guests can misread or put allergies in notes. A clear menu and a server's check help.

Remakes fall, the pass catches fewer mistakes and the record shows fewer repeats of the same pattern.

Ticket accuracy depends on a chain: the order, the ticket and the pass. Every wrong plate starts at one of those steps, and each needs a different fix. Trace each mistake to its step without blame, record every one, including those caught at the pass and the missed orders, and review the record weekly for patterns.

In most kitchens, the single change that fixes the most is a read-back at the table, with changes entered as modifiers. Add clear tickets that put every change under its dish, a pass that checks every plate, and training that follows the patterns your record shows.