Order management from table to pass

Order management is the work of getting an order from the guest's mouth to the guest's table: taken correctly, sent to the right station, cooked at the right moment, checked at the pass, carried to the right seat and charged correctly on the bill. It happens hundreds of times every service, mostly without anyone noticing. When it goes wrong, everyone notices: the guest who waits forty minutes for a main that was never sent, the steak that arrives well done, the dessert charged to the wrong table.

Most order problems are not cooking problems. They happen at the handovers, the moments when the order passes from one person or system to another: from the guest to the server, from the server to the till, from the till to the kitchen, from the station to the pass, from the pass to the runner and from the runner to the guest. Each handover is a chance to drop, change or delay the order.

This guide follows one order through a service, handover by handover. For each one, it explains what can go wrong, how often it does, and who should own it. It covers taking an order, sending an order to the kitchen, kitchen tickets, course firing, the pass, running food, changes and remakes, and the bill, and it ends with how to measure order accuracy across the whole journey.

Order management is the system, human and technical, that moves an order through the venue. It includes the way servers take orders, the point of sale that records them, the routing that sends each dish to the station that cooks it, the tickets the kitchen reads, the timing of each course, the checks at the pass and the way plates reach the table.

Good order management is invisible. Orders arrive at the kitchen complete and clear, courses are timed to the table, plates reach the right guests and the bill matches what was served. Poor order management is noisy: questions shouted across the kitchen, plates auctioned at the table, dishes remade and bills corrected.

The aim of this guide is to make each handover explicit, so that every one has an owner and a standard. Most of the improvement comes from that alone.

The order begins with taking an order: the conversation between the guest and the server. This is where the most important information is gathered, and where it is most easily lost. A guest mentions an allergy in passing, asks for a sauce on the side, or changes their mind after the server has moved on. If the server does not capture it, nothing later in the chain can recover it.

Train servers to listen for the details that matter: allergies, cooking preferences, substitutions, timing requests and who is sitting where. Repeat back large or complicated orders. Ask about allergies directly rather than waiting to be told. Note the seat for each dish, so the order can be served and split correctly later.

Where guests order from their own phones, this handover changes. The guest enters the order directly, with every option chosen from a list, which removes many transcription errors. But the conversation still matters: guests with allergies or questions need a person, and servers should still welcome every table and offer help.

The server owns this handover.

The second handover is entering the order into the point of sale. In some venues, servers write orders on a pad and enter them later at a terminal; in others, they enter them at the table on a handheld device. Each step between the guest and the system is a chance for an error: a modifier forgotten, a dish entered for the wrong table, an order left on the pad.

The fewer steps, the fewer errors. Entering orders at the table, on a handheld, removes the walk to the terminal and the rewriting. Structured choices for modifiers, rather than free text, mean "medium rare" arrives the same way every time. Seat numbers entered with each dish carry through to the kitchen and the bill.

Watch for orders that are entered but not sent. Many systems let a server build an order before sending it, which is useful for coursing but dangerous if the server forgets. A clear view of what has been sent and what has not prevents the table that waits forty minutes for an order that never left the terminal.

The server owns this handover, supported by a system that makes errors hard.

Sending an order to the kitchen is the moment the order leaves the floor. The system must route each dish to the station that cooks it, with every option, note and allergy, and the kitchen must receive it reliably. On paper, that means a printer at each station; on screens, a ticket at each station's display.

Routing is where many problems start. A dish routed to the wrong station is not cooked, or cooked late. A printer that runs out of paper or jams loses tickets silently. A screen that loses its connection stops receiving orders. Each of these produces the same result: a table waiting for food that nobody is cooking.

Check routing whenever the menu changes, so every new dish goes to the right station. Make sure printers are stocked and screens are connected before every service. And make sure servers can see that an order has reached the kitchen, so they do not have to walk to the pass to check.

The system owns this handover, and a named person, often the head chef or manager, owns checking that it works.

Once the order reaches the station, the cook has to read it. Kitchen tickets must be clear enough to cook from at a glance: the table, the time it has waited, each dish on its own line, modifiers directly under their dish, the seat for each plate and any allergy impossible to miss. Our guide to kitchen tickets that never need a shout covers what belongs on a ticket.

Tickets that are unclear send cooks to the pass to ask, or lead them to guess. A guess is how the wrong dish gets cooked. Ticket design is therefore part of order management, not a detail of the kitchen.

The order of tickets matters too. Cooks should work the oldest tickets first, and the ticket that has waited longest should be the most visible. Screens that show each ticket's waiting time help; on paper, a disciplined rail does the same job.

The station cook owns this handover, supported by tickets designed for reading.

Most restaurant meals are served in courses, and timing them is a handover in its own right. Starters are cooked as soon as they are ordered; mains are held until the server fires them, once starters are nearly finished. If the mains are fired too early, they arrive while starters are still on the table. If they are fired too late, the table waits.

Course firing depends on the server watching the table and the kitchen responding. The server must remember to fire the course, and the kitchen must see clearly which courses are held and which are active. On paper, a separate "fire" ticket is common; on screens, a held course changes state when it is fired.

Train servers to fire courses at the right moment, and give the kitchen a clear view of what is held. Track how often mains arrive while starters are still on the table; it is one of the clearest signs that course firing is not working.

The server owns firing; the kitchen owns responding.

The pass is where the kitchen's work comes together. The person running it, often the head chef or an expediter, checks each plate against the ticket, waits for all of a table's dishes to be ready, and sends them out together. In a classic kitchen brigade, this is one of the most senior roles in the kitchen.

The pass is also a common bottleneck. If the person on the pass cannot keep up, plates wait under the lights, dishes go cold, and tables receive their food late even though it was cooked on time. A clear view of every ticket and every station's progress helps the pass keep the kitchen in step.

Check each plate before it leaves: the right dish, the right modifiers, the right garnish, and an allergy plate clearly marked. A mistake caught at the pass costs a minute; a mistake caught at the table costs a remake and a guest's goodwill.

The person on the pass owns this handover.

Once plates leave the pass, they have to reach the right guests. Runners or servers carry them to the table and place each one in front of the guest who ordered it. Without seat numbers, this becomes an auction: "who had the medium rare?" With them, each plate goes straight to its guest.

Plates waiting at the pass for someone to carry them are a common delay. Assign runners at busy times, or make sure servers check the pass regularly. A plate that waits five minutes for a runner loses its heat and its quality.

Allergy plates need special care: carried separately, placed in front of the right guest, and confirmed with them. Our guide to building an allergen matrix that stays correct covers the record behind every allergy order.

The runner or server owns this handover.

Orders change during service. A guest swaps a dish, cancels a course, or sends a plate back. Each change has to travel the whole chain again: from the guest to the server, into the system, to the kitchen and back to the table. Changes made by word of mouth are the most likely to be lost.

Every change should go through the system, so the kitchen sees it on the ticket. Voided dishes should be marked as voided rather than disappearing, so a cook who has already started knows to stop. Remakes should be marked clearly, so the kitchen treats them as urgent and the bill does not charge twice.

Track remakes by cause: entered wrongly, ticket misread, cooked wrongly, guest changed their mind. The causes show which handover needs attention.

When a dish runs out, the order management system has to stop orders for it at every point where orders are taken: every terminal, every handheld and every guest's phone. If it does not, orders for a dish that no longer exists keep arriving at the kitchen, and each one has to be sent back to the table.

Our guide to 86 an item so nobody orders it at five past covers how to take a dish off everywhere at once, who may do it and what guests should see instead.

The bill is the last handover. It should reflect exactly what was served, with any voids, comps and changes applied, split the way the guests want to pay. If every earlier handover went well, the bill is simple. If not, this is where the errors surface: dishes charged that never arrived, changes that were not recorded, splits that do not add up.

Check large bills before they reach the table. Make it easy to split by item, using the seat numbers recorded when the order was taken. Our guide to splitting the bill for a table of eight covers the methods.

Order accuracy is the share of orders that reach the guest exactly as they asked, at the right time, and are charged correctly. It is the best single measure of order management, because it captures every handover at once.

Measure it through remakes, comps and complaints, recorded by cause. For a few weeks, record every dish that had to be remade or comped, and which handover caused it. The pattern usually points clearly to one or two weak handovers: orders entered wrongly, tickets misread, courses fired late or plates sent to the wrong seat.

Measure time as well. Ticket times show how long the kitchen takes; following a sample of tables from seating to food arriving shows how long the whole journey takes. Our guide to ticket times covers how to measure the kitchen's part.

Write down who owns each handover, and make sure everyone knows:

Ownership turns "someone should have noticed" into "this was my job". It is the simplest and most effective change most venues can make.

Many order problems can be prevented before the first guest arrives. A short briefing before service, with the floor and the kitchen together, sets up every handover for the night. Cover the dishes that are limited or already off, the specials and their allergens, any large or complicated bookings, who is running the pass and which servers have which sections.

Keep it short and the same every day, so it becomes a habit rather than a meeting. Five minutes spent agreeing what is on, what is off and who owns what saves far more than five minutes of questions during service.

Use the briefing to share what went wrong the night before, too. If three plates went to the wrong seat, say so, and remind everyone how seat numbers work. Small, regular corrections keep standards from drifting.

The right systems make every handover easier. A point of sale that lets servers enter orders at the table, with structured modifiers and seat numbers, removes transcription errors. Routing that sends each dish to its station removes lost tickets. A kitchen display that shows each ticket's waiting time and held courses makes timing visible. A menu that takes sold-out dishes off everywhere at once stops impossible orders.

The best systems also share one order across the floor, the kitchen and the bill, so nothing is re-keyed at any handover. Our guide to choosing a POS covers the questions to ask.

Here is an illustrative case of a venue tracing its order problems. The figures are examples.

Most of the improvement came from the handovers outside the kitchen, which is typical.

In servearound, the point of sale opens checks on the same floor plan the host seats from, and what a guest orders from the table's QR code menu joins the same check. Dishes sit on the check as not sent until they are sent, so it is always clear what has reached the kitchen; starters can go now and mains be held and fired with one press. Each dish names its station, so every order lands on the right board, with its options, notes, seats and any allergy on the ticket.

The kitchen display moves tickets through new, in progress and ready, a remake arrives marked re-fire, and an order from the table can be declined with its reason. A dish taken off at the till is off every terminal and guest menu at once. Checks can be split, merged, transferred or moved, and the booking, the order and the bill are one record, so there is nothing to reconcile. See fulfillment, or get in touch to walk through an order on your own floor.

At the handovers outside the kitchen, especially entering the order and firing courses. Record remakes by cause to see where yours happen.

Where the system supports it, it removes the step of rewriting orders at a terminal, which removes many errors.

In busy kitchens, someone must run the pass. In smaller ones, the head chef often does it.

Use a system that shows clearly what has and has not been sent, and train servers to check before leaving the table.

Order accuracy, measured through remakes and comps by cause, alongside ticket times.

Weekly during any change, then monthly. Patterns appear quickly once remakes are recorded by cause.

Order management is the journey of every order from the guest to the table and the bill, and most problems happen at the handovers rather than in the cooking. Taking an order, entering it, sending an order to the kitchen, reading kitchen tickets, firing courses, running the pass and carrying plates to the right seat are each a handover with its own risks.

Give each handover an owner and a standard, use systems that remove rewriting and make every change visible, and measure order accuracy by recording remakes and comps by cause. The pattern will show where to start, and fixing the weakest handover usually helps every table in the room.