Operations

Kitchen Order Ticket (Comanda)

The kitchen order ticket (comanda in Spanish) is the document that records a guest's order in a restaurant. It is the communication channel between the floor and the kitchen, and managing it well is key to operational efficiency and guest satisfaction.

Full definition

The kitchen order ticket (KOT, or comanda in Spanish, from the French commande, "order") is the physical or digital document that records the dishes and drinks ordered by a guest or table, serving as a work instruction for the kitchen and bar and as the basis for the bill. It is the heart of the operational flow in any restaurant: when order tickets work well, service flows; when they fail, you get mistakes, delays, returned dishes and unhappy guests. Traditionally, the order ticket was a triplicate or quadruplicate paper docket handwritten by the server, with copies going to the kitchen, the bar and the till. Today, most professional restaurants use digital ordering systems (handheld order pads, tablets or touchscreen POS terminals) that send the order instantly to screens in the kitchen and bar, eliminating legibility errors and the server's trips back and forth.

The order ticket contains critical information: table number or guest identifier, the time the order was taken, the server's name or code, the list of dishes and drinks with their modifications (gluten-free, how the meat is cooked, allergens, extras), the number of covers and, in some cases, special service instructions (birthday, VIP guest, severe allergy). A good order ticket must be clear, complete and correct: clear so the kitchen knows exactly what to prepare; complete so no information about modifications or allergens is missing; and correct so the guest gets what they ordered. The typical ticket flow is: taking the order at the table, sending it to the kitchen/bar, preparation by section or station, the call when dishes are ready ("service!"), serving the guest and finally closing the ticket for billing. Each restaurant has its own ticket rules: some allow changes after sending, others don't; some group starters and mains on a single ticket, others split them by course; some use colours or codes to flag urgency or allergies.

Ticket management also has a direct impact on the restaurant's KPIs: average time from order to service is a measure of kitchen efficiency; the percentage of tickets modified or voided points to communication problems with guests; and analysing tickets reveals best-selling dishes, frequent combinations and consumption patterns.

Formula

Ticket time = Time the dish is served – Time the order was taken

Explanation

Ticket time (or service time) measures the efficiency of the flow from the moment the guest orders until they receive their dish. It is calculated by subtracting the time the order was taken from the time the dish is served at the table. For a more detailed analysis, it can be broken down into: transmission time (from the server taking the order to it reaching the kitchen — practically zero with digital systems but several minutes with paper), preparation time (from the kitchen receiving the order to the dish being ready) and delivery time (from the dish being ready to it reaching the table). The benchmark varies by type of dish: cold starters should be served in 5–8 minutes, hot starters in 8–12 minutes and mains in 12–18 minutes (if served after starters, the time from the original order may be 25–35 minutes, which is fine because it includes eating the starters).

Monitoring average ticket time by type of dish lets you spot bottlenecks: if mains take 25 minutes on average but fish dishes take 35, the fish section has a capacity or process problem. It is also worth measuring the rate of modified tickets (orders changed after being sent to the kitchen) and the rate of voided tickets, both indicators of communication problems between floor and kitchen or of front-of-house training needs.

Worked example

It's 9:15 pm on a Friday. Carlos, a server, takes the order for table 7 (4 covers) on his tablet: 1x Caesar salad (no anchovies, allergy), 1x carpaccio, 2x sirloin (1 medium, 1 well done), 1x grilled sea bass, 1x wild mushroom risotto (vegetarian). Drinks: 1 bottle of Ribera del Duero crianza, 4 mineral waters. Notes: "the lady's birthday, candle on dessert".

Carlos taps "Send" and the ticket appears instantly on the kitchen screen (hot dishes), on the cold section's screen (salad and carpaccio) and on the bar printer (wine and water). The chef de partie on the cold section sees the anchovy allergy warning highlighted in red and prepares the Caesar with regular croutons but no anchovies. When the starters are ready, the cook taps "Ready" and a notification appears on Carlos's tablet. Meanwhile, the hot section has read the ticket and started on the two sirloins at their different degrees of doneness.

After 12 minutes Carlos collects the starters, and 8 minutes after the table finishes them, the kitchen calls the mains. By the end of the night, the system has recorded 847 ticket lines from 42 tables, with an average service time of 14 minutes for mains and only 2 changes after sending. Without the digital system, those 847 lines would have been 847 chances of a legibility error or a lost docket.

Why does it matter?

The order ticket matters because it is the critical link between what the guest wants and what the guest gets. A restaurant can have exceptional ingredients, talented cooks and friendly servers, but if the ticket fails, none of that reaches the guest correctly. Ticket errors have several impacts: dishes that go out wrong and have to be remade (product cost and time), excessive waits because of poorly communicated orders (guest dissatisfaction), allergies not passed on that can cause serious incidents (legal and health risk), and poor coordination between sections that creates bottlenecks in the kitchen. According to industry studies, restaurants with well-implemented digital ordering systems reduce order errors by 60–80%, service time by 15–25% and improve table turnover by 10–15%.

Digital tickets also generate valuable management data: which dishes sell most and when, which servers process the most orders, which tables take longest to order, which modifications are most frequent (perhaps suggesting the menu should offer that variant as standard). This data turns the order ticket from a simple slip of paper into a business intelligence tool. Finally, the order ticket is the basis of real-time stock control: every dish ordered automatically deducts its ingredients from inventory according to its recipe costing, so you always know what is in storage and when you need to reorder. This integration of order tickets, recipe costing and inventory is the core of modern restaurant management.

How does Zindra help?

Zindra's POS handles the entire digital ordering flow: order-taking on a tablet or phone, instant sending to kitchen screens by section, timing control, notifications when dishes are ready, and automatic deduction of ingredients from inventory according to recipe costings. Reports show average service times, best-selling dishes and efficiency analysis by server and by section.

Download the complete dictionary

Every hospitality term with formulas, examples and benchmarks in a handy PDF.

Want to run your restaurant on data?

Try Zindra free and keep food cost, staff, inventory and much more under control from a single platform.