A guide to organizing the hotel kitchen display by station and by revenue center
A hotel kitchen takes tickets from the restaurant, the bar, room service and sometimes the pool bar, all at once. This guide explains how to organize the display so each station sees its own lines, each revenue center has its own target time, and no ticket gets lost among the rest.
At eight in the evening your hotel kitchen receives a ticket from table twelve, a snack from the bar, a club sandwich for room 305 and two burgers from the pool bar that closes in twenty minutes. It is one kitchen, one grill and one cold-station cook. If everything lands on the same screen in the same color and the same order, the room service order goes cold on the pass while the chef chases table twelve. The problem is not the kitchen. It is how the display is organized.
One kitchen, several ticket origins
A restaurant without a hotel has a dining room and maybe a bar counter. A hotel kitchen has all of that plus room service, the pool bar, the lobby coffee shop and, in season, groups and banquets. Each origin has its own rhythm, its own delivery time and its own customer: the guest dining at leisure, the one waiting in the room with the television on, the one in a swimsuit who has no intention of waiting half an hour for nachos.
Most kitchen displays were designed for the first case: a dining room. They sort by entry time and show everything in a single column. Connect four revenue centers to them and the result is one queue where the room ticket competes with the table ticket, and the loudest one wins, which is almost always the server standing at the window.
Organizing the display well means accepting that there are two separate axes: the station that prepares, and the revenue center that ordered. Both matter, and the display has to show both without one hiding the other.
Station and revenue center are two different axes
The station answers the question “who prepares it?”: grill, cold station, hot line, pastry, drinks counter. The revenue center answers “who ordered it and where does it go?”: restaurant, bar, room service, pool, coffee shop. The same salad is prepared by the cold station, but it can go to table eight or to room 412, and in each case the target time, the packaging and the way it is settled are different.
When the display only knows stations, the kitchen prepares well but delivers badly: the dish comes out on time and then waits at the pass because nobody knew it was for a room. When it only knows revenue centers, the kitchen delivers well but prepares badly: the grill cook sees whole tickets and has to hunt for the line that is his. A hotel display needs both axes at once.
The station axis: what each cook sees
Each station should see only the lines that belong to it, with the ticket number and the origin visible. The grill cook does not need to see the salad, but does need to know that his steak belongs to the same ticket as that salad, so they go out together. That takes a shared ticket identifier across stations and a pass screen that reassembles everything before it leaves.
The revenue center axis: what the pass sees
The pass, or the person expediting, needs the opposite view: complete tickets, grouped by origin, with the time elapsed and the target time for each revenue center. That is where someone decides whether room service goes first because it is already at twenty minutes, or table twelve goes first because the guest asked for the check.
What a well-organized display looks like
There is no single correct layout, but there are elements every hotel kitchen display should have. These are the ones that make the biggest difference in practice.
- One color or label per revenue center, fixed and known by everyone: room service always looks the same, regardless of the hour or the cook on shift.
- The room number in the header of every room service ticket, and the table number on restaurant tickets. Never both in the same field.
- A timer per ticket that changes state when it crosses the target time of its revenue center, not one single time for the whole kitchen.
- Notes and modifiers on the same line as the dish, in a size that can be read from a meter away with busy hands.
- A “ticket complete” indicator at the pass that only lights up when every station has marked ready.
- The requested delivery time when the guest asked for one, for example breakfast to the room at 7:30.
What almost never helps is duplicate printing per station without a pass screen: every cook has a slip, nobody has the full ticket, and the server ends up assembling the order from memory. The kitchen page (Kitchen display) describes how a ticket is split across screens and how the pass puts it back together.
Routing rules: which line goes to which station
Routing is the table that says, for every item on the menu, which station it is sent to. It seems trivial until there is a dish that needs two stations, or a pool bar that in low season is served from the main kitchen and in high season from its own grill. The rule has to live in the system, not in the chef’s head.
| Line type | Primary station | Secondary station | Who sees it at the pass |
|---|---|---|---|
| Grilled cuts and fish | Grill | Hot line (sides) | Restaurant or room service by origin |
| Salads and cold starters | Cold station | None | All revenue centers |
| Bar snacks | Hot line | Cold station (sauces) | Bar and pool bar |
| Desserts | Pastry | None | All revenue centers |
| Mixed drinks | Drinks counter | None | Only the center that ordered |
| Breakfast to the room | Hot line | Cold station (fruit and bread) | Room service, with requested time |
Two practical rules. First: if a dish changes station by season or by time of day, that rule is configured with a date and time, not announced on the whiteboard. Second: when the pool bar (Pool bar) closes, its pending tickets must move visibly to another revenue center, not vanish from the screen.
Room service asks for something different
Of all the origins, room service (Room service) suffers most on a badly organized display, because the guest is out of sight. A diner in the restaurant raises a hand; a guest in room 305 just waits, and when the waiting gets old, calls the front desk, which has no idea where the order is. The display has to compensate for that invisibility.
That means three things. The room service ticket must carry the room number and the guest’s name exactly as they appear on the folio, so the room charge is already verified when the order is taken. It must have a target time that includes the trip to the room, not just preparation. And it must have an “on the way” status the front desk can check without calling the kitchen.
One detail that gets forgotten: room service gets packed. If the display does not distinguish the origin, the cook plates a burger that was headed to a room, and someone has to rebuild it in a container while the guest waits. That double preparation is silent waste and lost time.
An illustrative example with times
The figures below are made up to show the calculation. They do not describe any real property. They only serve to see what changes when the display separates origins.
Picture a three-hour dinner shift in which the kitchen receives 100 tickets: 60 from the restaurant, 25 from the bar and 15 from room service. With a single queue sorted by entry time, the average ticket takes 22 minutes, and room service, which arrives when the restaurant is full, averages 34 minutes including the trip. The bar, whose snacks should leave in 10, averages 18.
Now picture the same kitchen with target times per revenue center and automatic priority when a ticket crosses its time: restaurant 15 minutes, bar 10, room service 25 with the trip. With the same 100 tickets and the same cooks, the restaurant averages 14, the bar 9 and room service 24. The overall average drops to 14 minutes: (60 × 14 + 25 × 9 + 15 × 24) ÷ 100 = (840 + 225 + 360) ÷ 100 = 1,425 ÷ 100, which rounds to 14.
Nobody cooked faster. What changed is that the display stopped sorting by who arrived first and started sorting by who is falling behind what the guest was promised.
Mistakes we see in hotel kitchens
- One printer for everything, and a chef who “just knows” which slip is from the pool by the type of dish.
- The room number handwritten in the ticket note, where it sometimes reads 305 and sometimes 308.
- A single target time for the whole kitchen, which makes the bar always look on time and room service always look late.
- Modifiers typed into a free-text field that the station screen truncates when it does not fit.
- Pool bar tickets “marked ready” when they leave the kitchen, with nobody recording that they reached the lounger.
- A pass that shows lines by station instead of the whole ticket, forcing the server to count plates.
All these mistakes share one thing: the system does not know where the ticket came from, so the kitchen guesses. And guessing works on quiet days, never on a Saturday with a full house.
A hotel kitchen display needs two axes at the same time: the station that prepares and the revenue center that ordered. Each center has its color, its target time and its header (table or room), and the pass reassembles the stations before the ticket goes out.
What to do this week
- Write down on one sheet the real routing table of your kitchen: every menu item and the station that prepares it today. You will find at least two that go wherever the cook on shift decides.
- Define a target time per revenue center, together with the kitchen team and the front desk, and include the trip in the room service one.
- Assign a fixed color per origin and put it on the ordering devices and at the pass too, not only on the kitchen display.
- Check how the room number reaches the kitchen today. If it is typed into a note, it is data that can fail and needs to be tied to the folio.
- Measure the average time per origin for one week, even with a wall clock and a notebook, so you have a baseline before changing anything.
- Bring the expediter, the chef and the night-shift front desk agent together to review which tickets ran late and why.
Inn Restaurant separates tickets by station and by revenue center from the moment they are taken, with the room number tied to the guest folio and each origin’s target time on the kitchen display and at the pass. If you want to see what a full-house night looks like on that screen, the 15-minute demo is booked on the contact page (contact).
More guides
How to calculate the cost of a dish with a standard recipe in the hotel restaurant
Without a standard recipe there is no theoretical cost, and without theoretical cost the hotel controller cannot say whether the restaurant makes or loses money on each dish. This guide walks through the four steps with an illustrative example and the cases that only show up in a hotel.
How to design a room service menu the kitchen can sustain at two in the morning
The menu that works at one in the afternoon with six cooks does not work at two in the morning with one. This guide shows you how to cut it down, what times to promise the hotel guest and which dishes should never go up to the room.
How to do the hotel’s weekly beverage inventory in under an hour
Beverage inventory gets postponed because it sounds like an afternoon lost. With bottle counting and per-glass equivalences, the hotel’s bar and restaurant can finish it in under an hour.
Your hotel’s restaurant already sells well. Now the hotel needs to know it.
Fifteen minutes, with your menu and your tables. Nothing to install.