Kitchen tickets that never need a shout

Kitchen tickets are the instructions a kitchen cooks from. Every order taken on the floor becomes a ticket, printed on paper or shown on a screen, and every plate that leaves the pass started as a line on one of them. When a ticket is clear, complete and in the right order, a cook can read it at a glance and start cooking. When it is not, the cook has to stop, walk to the pass, or shout a question across a busy kitchen to a server who is three tables away.

Every shout costs time. The cook stops working, the server stops serving, and the ticket waits while someone works out what "burger no" was supposed to mean. On a busy night, a handful of unclear tickets can add minutes to every table's wait and lead to the remakes that cost even more.

This guide sets out what belongs on a kitchen ticket and in what order, so a station can cook from it without asking a single question. It covers the header, the dishes, modifiers on the ticket, allergies, seats, course firing, notes, the kitchen screen layout and how order accuracy on the floor decides whether the ticket is right in the first place.

A kitchen ticket has one job: to tell the cook exactly what to make, for whom, and when. Everything on it should serve that job, and anything that does not should be left off. A ticket cluttered with prices, server notes about the guest's mood and a full repeat of every option is as hard to cook from as one that leaves out the steak's temperature.

The ticket is read under pressure. Cooks glance at it between tasks, often from a distance, with heat, noise and several other tickets competing for attention. It must be readable in a second or two, with the most important information where the eye lands first.

It is also a record. Once the dish is made, the ticket shows what was ordered, when and by whom, which helps resolve disputes and spot patterns in mistakes. That record is only useful if the ticket was accurate in the first place.

The top of every ticket should answer three questions instantly: which table is this for, when did it arrive, and who sent it. The table number should be the largest thing on the ticket after the dishes themselves, because it is what the pass uses to match plates to tables.

The time the ticket arrived in the kitchen is essential. On paper, it is printed at the top. On a screen, it is often shown as a running clock, counting how long the ticket has been waiting, which is even more useful. A cook who can see that a ticket has been waiting 14 minutes knows it needs attention now.

The server's name helps when a question does arise, so the kitchen knows whom to ask without guessing. The number of guests at the table helps the pass plan plating and timing. Keep the header short: table, time, server and covers are usually enough.

The body of the ticket lists the dishes. Each dish should have its own line, with the quantity first and the dish name in plain, consistent words. "2 sea bream" is clearer than "sea bream x2" or "SB (2)". Use the names the kitchen uses, not the marketing names on the menu, if they differ.

Group dishes by course, with the course clearly marked. Within a course, many kitchens list dishes in the order they will be cooked or plated, or grouped by station. Whatever the order, it should be the same on every ticket, so cooks know where to look.

Keep dishes for other stations off the ticket, or clearly separated. A grill cook does not need to read the salad order to find the steak. Routing each dish to the station that cooks it, so each station sees only its own dishes, is one of the main advantages of a kitchen display.

Modifiers are the changes and choices attached to a dish: how a steak is cooked, a sauce on the side, no onions, extra cheese, a gluten-free bun. They are where most ticket mistakes happen, because they are easy to miss, easy to misread and easy to forget to enter.

Show modifiers on the ticket directly under the dish they belong to, indented or marked so they cannot be mistaken for a separate dish. Use consistent wording: "no onion", "sauce on side", "medium rare". Show removals clearly, so "no nuts" stands out from "with nuts". On a screen, a different colour or style for modifiers helps.

Keep the choices on the menu structured, so servers and guests choose from a list rather than typing free text. "Medium rare" chosen from a list arrives the same way every time; "MR pls" typed in a hurry may not. Free-text notes still have a place, but the common modifiers should be choices.

An allergy is the most important information a ticket can carry, and it must be impossible to miss. When a guest has told the server about an allergy, the ticket should say so prominently, at the top or across the ticket, in a style that no other information uses. "Allergy: sesame" in large text, highlighted, is the minimum.

The allergy should be attached to the specific dish or guest it affects, not just to the table. A table of six where one guest has a shellfish allergy needs the kitchen to know which dish is theirs. Seat numbers make that possible.

Make sure the kitchen has a clear process for allergy tickets: who checks the dish, what equipment is used, and how the plate is marked so the server takes it to the right guest. Rules on allergen information vary by country; in the UK, for example, the Food Standards Agency publishes allergen guidance for food businesses. Our guide to building an allergen matrix that stays correct covers the record behind the ticket.

Seat numbers tell the kitchen and the pass which guest each dish is for. They matter most for large tables, allergies and dishes that look alike. Without them, a server arriving at a table of eight with four steaks cooked to different temperatures has to auction the plates: "who had the medium rare?"

Record seats when the order is taken, using a consistent numbering, such as clockwise from the seat nearest the door. Show the seat number beside each dish on the ticket. At the pass, plates can then be labelled or arranged by seat, so the server can place each one in front of the right guest without asking.

Seat numbers also help the bill. When guests pay separately, a check that knows which dish belongs to which seat can be split in seconds.

Course firing is how the kitchen times each course. Starters are usually sent as soon as they are ordered; mains are held until the server fires them, once the starters are nearly finished. The ticket must make it clear which courses are to be cooked now and which are waiting.

A held course should appear in a way that cannot be mistaken for an active one: greyed out, in a separate area, or marked "held". When the server fires the course, the ticket should change visibly, with the time it was fired, so the cook knows to start. On paper, many kitchens print a separate "fire" ticket; on a screen, the held ticket changes state.

Without clear course firing, kitchens either cook mains too early, so they arrive while starters are still on the table, or too late, so the table waits. Both are among the most common complaints about service.

Free-text notes are useful for the unusual: a birthday candle on the dessert, a dish to be served to a child first, a guest who would like their dish cut up. They should be short, specific and attached to the dish they concern.

They become a problem when they replace structured choices or carry information the kitchen does not need. "Lovely couple, regulars, be nice" belongs in the guest's record, not on the grill's ticket. "Make it good" is not an instruction. A note that says the same thing as a modifier, such as "no onions" written in a note as well as chosen as an option, adds clutter.

Train servers to use notes only for what cannot be said with a choice, and to keep them brief. A good test is whether the cook could act on the note without asking a question.

Orders change. A guest swaps a dish, a table cancels a course, a dish comes back to be remade. Each change must reach the kitchen clearly, or the kitchen cooks the wrong thing.

When a dish is removed, the ticket should show it struck through or marked "void", not simply disappear, so a cook who has already started knows to stop. When a dish is added, it should appear as a clear addition, with its own time. When a dish is remade, the new ticket should be marked "re-fire" or "remake", so the cook knows it is urgent and the pass knows it is replacing a plate.

Changes are where verbal shouts are most common: "table 12 changed the bream to the steak!" A system that pushes every change to the ticket removes most of those shouts.

On a kitchen display, the kitchen screen layout decides how quickly cooks can read tickets. Tickets should appear in a predictable order, usually oldest first, so the ticket that has waited longest is the first one the cook sees. Each ticket should be large enough to read from the station, with the table, the time waiting and the dishes visible without scrolling.

Use colour sparingly and consistently. A ticket that turns amber as it approaches its target time and red when it passes it tells cooks where to focus. Allergies should have their own unmistakable style. Too many colours, for too many reasons, make the screen harder to read rather than easier.

Let cooks act on tickets quickly: a tap or a key to start, to mark ready, to bump, and a way to recall a ticket bumped by mistake. Our guide to how much a kitchen display system costs covers screens, mounts and bump bars.

When guests order from their own phones, their orders become tickets too, and the same rules apply. The ticket should look exactly like one entered by a server: table, time, dishes, modifiers, notes and any allergy, in the same places. Cooks should not have to read two kinds of ticket.

There are a few differences to plan for. Guest orders can arrive at any moment, so courses need clear handling: either the guest orders course by course, or later courses are held until a server fires them. Guests sometimes add notes a server would have handled differently, so the kitchen needs a way to accept or decline an order with a clear reason, and the guest needs to hear about it quickly.

The person on the pass reads tickets differently from a cook on a station. A cook needs to know what to make; the pass needs to know what each table is waiting for, which stations are behind and when a table's dishes will all be ready together. In a classic kitchen brigade, this role belongs to the expediter or the head chef, who calls tickets and checks every plate before it leaves.

Give the pass a view of the whole order, with every station's progress. On a screen, that is usually a board showing every ticket, oldest first, with each dish's state. On paper, it is the full ticket on the pass rail, with station tickets separate. Either way, the pass should never have to shout to find out whether the grill has started table 12's steaks.

Not every kitchen uses screens, and paper tickets can work well if they are designed carefully. Use a clear, large font. Print the table number and time at the top in bold. Leave space between dishes and courses. Print modifiers indented under their dish. Print allergies in a way that stands out, such as reversed text or a box.

Keep the printer where it can be reached easily and seen, keep paper stocked, and have a rail where tickets are hung in order. Make it someone's job to check that every ticket printed and that none have fallen behind the rail.

The weaknesses of paper remain: tickets can be lost, smudged or hung out of order, and paper cannot count how long a ticket has waited. Many kitchens move to screens for exactly those reasons.

A ticket can only be as accurate as the order behind it. Most ticket problems start on the floor: a modifier not entered, a dish rung in for the wrong table, a seat number missed, a change made verbally but never entered. The kitchen then cooks exactly what the ticket says, and the guest receives the wrong dish.

Improve order accuracy at the source. Train servers to repeat orders back to guests, especially large or complicated ones. Use structured choices for common modifiers. Send orders directly from the table or the till to the kitchen, without rewriting them. Where guests order from the table, the order reaches the kitchen exactly as they chose it.

Track remakes by reason. If many remakes come from missing modifiers or wrong dishes, the problem is on the floor, not in the kitchen. Our guide to order management from table to pass covers every handover in the order's journey.

Test your ticket design with the people who use it. Ask cooks to read sample tickets from their stations and say what they would cook. Time them. Ask what is missing, what is confusing and what they ignore. Their answers are the best guide to what belongs on the ticket.

Test with the hardest orders: a table of ten with allergies, modifiers, held courses and a change halfway through. If the ticket for that order is clear, the ordinary ones will be too.

Review the design every few months, and whenever the menu changes significantly. New dishes may need new modifiers, and new stations may need new routing.

Here is an illustrative ticket, before and after a redesign. The details are examples.

Nobody needs to ask a question. The allergy is attached to the right dish and seat, the mains wait until they are wanted, and each plate can go to the right guest.

In servearound, tickets go to the station that cooks them, oldest first, each showing its table, its time in the kitchen, every dish with its options, and the seat each plate is for. A guest's allergy is called out across the ticket, removed ingredients show as "no" lines, and a voided line is marked as voided rather than disappearing.

Dishes sit on the check as not sent until the server sends them, so starters can go now and mains be held and fired with one press when the table is ready. Held tickets are kept out of the active board until they are fired. A dish sent back as a remake arrives marked re-fire, each dish can carry its own note for the kitchen, and tickets move through new, in progress and ready by touch or from a bump bar. See fulfillment.

No. The kitchen does not need them, and they add clutter.

Directly under their dish, in consistent, structured wording chosen from a list wherever possible.

They help most for large tables, allergies and dishes that look alike. Many venues use them for every table so the habit sticks.

Show them prominently, attached to the dish and seat, and have a clear kitchen process for allergy orders.

Usually not. Each station should see its own dishes, with the pass seeing the whole order.

An order entered wrongly on the floor. Fix order accuracy at the source.

Kitchen tickets should let a station cook without asking a single question. Put the table, the time waiting and the server at the top, list each dish on its own line in a consistent order, show modifiers on the ticket clearly under their dish, make allergies impossible to miss and add seat numbers so every plate reaches the right guest.

Use course firing so held courses cannot be mistaken for active ones, keep notes short and useful, push every change to the ticket, and design the kitchen screen layout for reading at a glance. Above all, protect order accuracy on the floor, because the clearest ticket in the world cannot fix an order entered wrongly.