Modifiers on the ticket: no onions, really

A guest orders a burger with no onions, and says it twice. The server types it in. The ticket reaches the grill, where the cook reads "BURGER" in large letters and, at the bottom, under the fries and two other dishes, a line of small print saying "no on". The burger arrives with onions. The guest sends it back, the kitchen remakes it, and the table's mains are ten minutes late.

Nobody in that story did anything unusual. The server entered the change, and the cook read the ticket. The problem was where the change appeared and how it looked. Modifiers on the ticket are read in a second, at a glance, by a cook with four other tickets in front of them, and if a change is not where the eye goes, it is not seen.

This guide covers how changes to a dish should appear on the ticket so they are seen at the station, the difference between choices, additions, removals and notes, why an allergy must stop the ticket rather than trail at the bottom of it, and how to check whether your tickets work. Every venue and figure in it is an example.

Cooks read tickets fast. In a busy service, a grill cook looks at a ticket for a second or two, takes in the dish names and quantities, and starts cooking. Anything that does not stand out in that second is likely to be missed until the plate is at the pass, or in front of the guest.

Modifiers on the ticket get missed for a few common reasons. They appear in the same size and colour as everything else. They sit at the end of the ticket rather than under the dish they change. They are abbreviated in ways only the person who typed them understands. Or they are buried in a free-text note that mixes the important with the trivial.

Each of those is a design problem, not a staff problem. A ticket that puts each change where the eye goes, in a form that cannot be misread, gets the change seen.

Not every change is the same, and a good ticket treats them differently. There are four main kinds of change a guest can make to a dish.

Choices are decisions the menu asks for: the size, the cut, the cooking point of a steak, the choice of side. They are expected, and the dish cannot be cooked without them. Additions are extras the guest adds: an extra egg, a side of greens, a sauce. Removals take something out of the dish: no onions, no cheese, the dressing left off. Notes are anything else, in the guest's or the server's words: "sauce on the side", "cut in half for a child".

Each needs its own treatment. Choices are routine, additions change what is plated, removals are where mistakes hurt, and notes need reading in full.

The single most important rule is that every modifier appears directly under the dish it changes. A ticket that lists three dishes and then, at the bottom, "no onion, extra cheese, medium rare" leaves the cook to work out which change goes with which dish.

Under the dish, a modifier is read in the same glance as the dish name. "Burger, medium rare, no onion, extra cheese" leaves nothing to guess. When a table orders two of the same dish with different changes, each should appear as its own line: one burger as it comes, one burger with no onion, not "2 burger, 1 no onion".

This is the foundation of order accuracy in the kitchen. A change that is attached to its dish cannot be applied to the wrong one.

Removals are where modifiers matter most. A missing addition is a small disappointment; a missed removal can be a dish the guest cannot eat, and if the removal was for an allergy, a dish that can harm them.

A removal should appear on its own line, starting with a word such as "No", in a strong colour or weight that stands out from the rest of the ticket. "NO ONION" in red on its own line is seen; "(-onion)" in brackets after the dish name is not.

Avoid abbreviations for removals. "No on" might mean no onion or nothing at all; "NO ONION" leaves no doubt. If the reason for the removal is an allergy, the ticket should say so, because the kitchen handles an allergy differently from a preference: separate utensils, a clean board and a check at the pass.

Choices should be shown clearly but quietly, because they appear on most tickets. A cooking point, a size or a chosen side can sit on a line under the dish, in normal weight, so the cook reads it with the dish name.

Additions should be visible, because they change what is plated. An extra egg or a side of greens added to a dish must be on the plate when it reaches the pass, so the addition should be listed under its dish, not in a separate list at the bottom.

Where a choice is required, such as a cooking point for a steak, the order should not be sent without it. A steak with no cooking point forces the cook to stop and ask, which is exactly the shout a good ticket avoids. Our guide to modifiers: letting guests change a dish, safely covers how to set up modifiers so the required choices are always made.

Cooking points are the choices most often misread, because the words vary. One server writes "MR", another "med rare", a third "pink", and a guest who asks for "medium, but not too pink" leaves the cook guessing. A steak cooked to the wrong point is one of the most common remakes in any grill kitchen.

Agree one set of words for cooking points, such as rare, medium rare, medium, medium well and well done, and use them everywhere: on the menu, on the till and on the ticket. Set them up as a required choice on every dish that needs one, so the server taps a point rather than typing it.

Train servers to turn what the guest says into the agreed words, and to check anything unusual with the guest before sending it. "Medium, but not too pink" becomes medium rare or medium, confirmed at the table, not left for the grill to interpret.

Free-text notes are useful for the changes the menu does not cover: "sauce on the side", "cut in half for a child", "birthday, candle on the dessert". They let the guest's words reach the kitchen.

They are also where problems hide. A note that mixes an allergy with a preference, such as "no nuts please and extra sauce", gives both the same weight. A note that repeats a modifier already chosen adds clutter. A note that says "see server" sends the cook away from the station.

Keep notes short, clear and for things the modifiers cannot express. Train servers to use the modifiers first, and never to put an allergy only in a free-text note. Notes should appear under their dish, in a style that tells the cook to read them, but they should never be the only place a critical change appears.

An allergy is not a modifier. It is a warning that changes how the whole table's food is handled, and it must stop the ticket, not trail at the bottom of it.

The guest's allergy should appear at the top of the ticket, across its width, in a colour that stands out, before any dish is read. A cook who reads "ALLERGY: SESAME" before reading the dishes cooks every dish with that in mind. A cook who reads it after plating has already made the mistake.

Each dish that contains the allergen should also be marked, so the cook does not have to remember which dishes contain sesame. That marking depends on accurate allergen information for every dish. Our guide to allergy notes: the record that must not fail covers how to record allergies so they reach the kitchen.

An allergen matrix is the record of which allergens each dish contains, dish by dish and allergen by allergen. It is the source of truth behind every allergen marking on the menu and the ticket.

If the matrix is wrong, the ticket is wrong. A dish whose recipe changed to include a nut-based sauce, but whose allergen record was never updated, will appear on the ticket as safe for a guest with a nut allergy. The ticket design can be perfect and still pass on a dangerous mistake.

Keep the matrix current: update it whenever a recipe, a supplier or an ingredient changes, and check it regularly against what the kitchen actually uses. Our guide to build an allergen matrix that stays correct covers how, and the background on food allergy shows why the stakes are so high.

Order accuracy starts before the ticket. If the change is entered wrongly, the clearest ticket in the world will show the wrong change clearly. The point of order, whether a server's till or a guest's phone, must make changes easy to enter correctly.

The best setup offers the common changes as modifiers the server or guest can tap, rather than typing. A burger's choices, a steak's cooking point, the sides and the most common removals can all be set up in advance, so they arrive on the ticket in a consistent form.

Required choices should be required: the order cannot be sent without a cooking point for the steak. Removals should be easy to find, from the dish's own ingredients, so the server does not have to type "no onion" and hope the spelling is clear.

A ticket is one step in a chain: the guest's request, the server's entry, the ticket, the cook's reading, the plating and the pass. A mistake at any step reaches the guest, so order accuracy needs checks along the way.

The server should read back changes to the guest, especially removals and allergies. The cook should read the whole ticket before starting. The pass should check every plate against the ticket before it leaves, looking especially for removals and allergies.

The pass is the last line of defence. A pass that checks each plate against the ticket catches the burger with onions before it reaches the guest who asked for none. That check is only possible if the ticket shows the change clearly.

Guests change their minds after ordering, and servers make mistakes they notice later. When a change is made after the ticket reaches the kitchen, it must reach the kitchen in a way that cannot be missed.

A change shouted across the pass may not reach the cook who is plating. A new ticket for the same dish may be cooked as a second dish. The safest approach is to show the change on the original ticket: the old line struck through and the new one added, so the cook sees both what was there and what has changed.

If a dish has already been started, the kitchen needs to know whether to start again. Clear communication between the floor and the kitchen matters more here than at any other point.

On paper kitchen tickets, the options are limited. The printer prints what the till sends, usually in one size and one colour, and the layout depends on the till's settings. Many kitchens improve paper tickets by setting the till to print modifiers under their dish, removals in capitals and allergies at the top.

On a screen, kitchen tickets can do more: removals in a strong colour, allergies in a coloured band at the top of the ticket, dish allergens marked against the guest's allergies, and changes after sending shown as struck-through lines. A screen also keeps tickets readable, where paper fades, gets splashed and falls off the rail.

Whichever you use, test the ticket under real conditions: read it from where the cook stands, in a second, in the heat and noise of service.

Good tickets still need trained people. Servers need to know how to enter changes: modifiers first, notes only for what the modifiers cannot express, and allergies always recorded properly. Cooks need to know what each part of the ticket means and to read the whole ticket before starting.

Practise with hard orders: a table of six with two allergies, three removals, a required choice and a change after sending. Walk through how each appears on the ticket, how it is cooked and how it is checked at the pass.

New staff should learn the ticket in their first shift. A cook who has never seen how an allergy appears on your tickets may miss it the first time it matters.

To know whether your tickets work, measure the mistakes. Record each dish sent back or remade and the reason: a wrong change, a missed removal, a missed allergy, the wrong dish or the wrong cooking point.

A pattern shows where the problem lies. Many missed removals point to how removals appear on the ticket. Many wrong cooking points point to the point of order, where the choice is not required. Many mistakes on one station point to training or layout there.

Treat any allergy mistake as serious, even a near miss caught at the pass. Each one should be reviewed: how the allergy was recorded, how it appeared on the ticket, how it was cooked and how it was caught.

Share the results with the team each month. When cooks and servers see that missed removals fell from twelve to three after a change to the ticket, they understand why the details matter, and they keep to the routine.

An invented brasserie finds that about one dish in sixty is sent back because a change was missed, most of them removals. Its paper tickets print every change at the bottom of the ticket, in the same size as everything else, and allergies in the same free-text note as preferences.

The brasserie changes three things. Every change is printed under its dish. Removals appear on their own line in capitals, starting with "NO". Allergies are entered as allergies, not notes, and appear at the top of the ticket. Servers are trained to use modifiers first and to read back removals and allergies to the guest.

After a month, the number of dishes sent back for missed changes falls sharply, and the pass catches most of the few that remain before they leave the kitchen. The cooks say the tickets are easier to read, because each change is where they look.

In servearound, a dish's options are set on the dish itself: variants, such as a size or a cut, whose price replaces the dish's price, and add-on groups priced on top, each required or optional and allowing one choice or several. Guests choose them on the table's QR code menu; servers choose them on the till, which also offers the dish's ingredients to take off and a note for the kitchen on any dish or the whole round.

On the kitchen screen, each dish appears with its quantity, its options on their own line beneath it, its allergens from the menu, in red where they match the guest's allergies and amber otherwise, each removal as a red "No" line and its note. The guest's own allergies, from their profile, sit at the head of the ticket, and a dish voided after it was sent stays on the ticket, struck through and marked as voided, so the line stops cooking it. See Order Fulfillment and the menus module.

Directly under the dish they change, so the cook reads them in the same glance as the dish name.

On their own line, starting with "No", in a strong colour or weight, with no abbreviations.

No. An allergy changes how the whole table is handled, so it should appear at the top of the ticket, with each affected dish marked.

A record of which allergens each dish contains, which is the source of every allergen marking on the menu and the ticket.

When they replace modifiers or hide allergies. Use them only for changes the modifiers cannot express.

Offer common changes as modifiers, require the essential choices, read back removals and allergies, and check every plate at the pass.

The change should show on the original ticket, with the old line struck through, rather than relying on a shout or a new ticket.

Record every remake and its reason, look for patterns and review every allergy mistake or near miss.

Modifiers on the ticket must be seen in a second, by a cook with other tickets in front of them. Put every change directly under its dish, show removals on their own line in a strong colour, keep choices quiet and additions visible, and keep free-text notes for what the modifiers cannot express.

An allergy is not a modifier: it belongs at the top of the ticket, with each affected dish marked from an allergen matrix that is kept current. Build order accuracy into the point of order with required choices and easy removals, check every plate at the pass, and measure remakes so you know where the mistakes really come from.