A kitchen order ticket tells the team what to make. On paper it might hang on a rail by the stove. On a kitchen display it appears as a ticket with a timer. Both can work when everyone has agreed who reads the ticket and when a dish is ready. The useful question is where your orders get stuck today.
Watch one shift from the point where orders arrive. A server might walk the same request to two stations. The cook might have a row of tickets and still ask which table has waited longest. The counter might call a token while the last dish is still on the line. Write down the issue each time it happens. Start with the recurring issue that affects service the most.
Decide what a ticket should do
A ticket needs a service reference and a clear list of dishes. Use a table for dine-in or a token at the counter. Teach staff to read the reference out loud when two similar orders are in front of them. The way the team identifies the order matters as much as the technology.
Agree on the moment the kitchen starts work. A server taking an order can check before sending it. A cashier taking payment first can agree when to send prep the ticket. If someone calls a side dish verbally while the ticket already has it, make sure the cook knows it belongs to the same order.
Paper is familiar and can physically travel with a plate. A screen keeps the queue and timing visible in one place. If you use both, decide where the screen is the working record and where a paper ticket travels with the order. One person should be able to say when the order is complete.
Pick a station for your first screen
Choose the part of the kitchen where the team needs the clearest queue. At a takeaway that might be packing. At a dine-in restaurant it might be the hot line. Put a tablet or laptop where people can see it without turning away from a task. Check glare under the lights you actually use during service.
Put several practice orders through in a row. Ask the cook which ticket they would start first and why. In Nimki, each kitchen ticket has a timer. Ask the cook to compare two timers and find a dish they can finish while another ticket is cooking. Do the same exercise with the waiter, who needs to know what the kitchen sees after Send.
Once one screen works, map the next station. A bar usually needs a different view from the hot line. A bakery might want a screen near its packing bench. Define a simple owner for each station. When a mixed order contains food and a drink, test what each person sees before service.
Agree on ready, returned and sold out
A single ticket can have dishes that finish at different speeds. Agree when to mark one dish ready and when to mark the whole ticket ready. In Nimki the kitchen can do either. Use a practice order with a quick starter and a slower main. Let the team work through both actions and tell you what should happen next.
Decide who handles a ticket sent back. In Nimki, a kitchen user can send it back with a reason. Practise giving a reason short enough to read at a glance. “Check table number” is more helpful than “wrong order”. Make sure the waiter or cashier knows when they are expected to respond.
When something sells out, have the kitchen mark it sold out as soon as the last portion is assigned. Test an item that returns later in service as well. Decide who undoes the sold-out state and who tells the front of house. A team that agrees on this avoids promising a dish on the way to the table.
Walk an order to the guest
For table service, ask a teammate to act as the waiter. Seat a table and send a small order from their phone. Follow it to the kitchen. Mark dishes ready as they finish. Back at the table, check the bill so far and send it to the counter. Note anywhere the person has to stop and ask what to do.
At the takeaway counter, send two similar orders and give them different tokens. Arrange for the second order to finish first. Ask the packer to check the contents and call the right token. The customer collecting that order should be able to hear it and recognise it. Decide who calls again when nobody comes forward.
Take the same exercise into a live but quieter service. Measure progress by the questions staff ask and the mistakes they catch. Look for repeated clarifications about where a dish goes or whether it’s ready. Tidy the menu names or station routine before you add another screen.
Write the handover for the next shift
Put the new routine where the team can see it. Write down who opens the kitchen screen, where it sits and how the station recognises an order. Include who marks ready and who calls a token. A list that fits on a small card is easier to use during a shift than a long set of instructions.
Keep a sample handover with one new order and one unfinished order. Let the incoming cook find the ticket, say what is ready and name what is still cooking. If you use a printout at the pass, try handing over one that has been on the rail for a while. Ask how the team knows its current state.
Review after a few comparable shifts. Talk to the cook, the server and the cashier separately. Check which repeated questions disappeared and which ones remain. Change one part of the workflow at a time so you can tell whether it helped. A well-placed screen with a clear station routine can do more than several screens introduced at once.
Before you commit, give the device the same check you would give a printer. Make sure the station can read it at arm’s length. Check power, brightness and where a charging cable will sit. Ask the cook to find one ticket while working at the usual pace.