What is the best way to train staff to avoid remakes?

Training alone does not stop remakes. The real fix is to redesign the kitchen’s workflow so that mistakes cannot happen. A kitchen display with automatic routing and real-time tracking removes the chance for errors. Train the team on the new system, and they will see fewer remakes without extra effort.

Can a kitchen display really cut remakes by 80%?

Yes, if it is set up correctly. The display must show every order in real time, route tickets automatically, and colour-code by wait time. The result is a kitchen where nothing gets lost, mixed up, or delayed—so remakes become rare.

How do we track the reason for each remake?

Log every remake for a week, noting the cause—undercooked, wrong ingredients, missing sauce, etc. Once you have the data, you can see where the failures cluster and fix the process. The key is to track the reason , not just the number.

Will a kitchen display slow down service?

No, if it is designed for speed. A good kitchen display shows orders in real time, routes them automatically, and highlights delays—so the team can work faster, not slower. The result is fewer remakes and faster tables.

What if our kitchen is too small for a display?

Even a small kitchen can benefit. Start with one screen at the pass, then expand as needed. The key is visibility—if the team can see every order, they can work more efficiently, no matter the space. Start by installing a kitchen display and routing tickets automatically. The cost is not in the software—it is in the time you waste now, every single shift. See the plans and pricing .

Kitchen remakes cost £4.50 each—here’s how to stop them

Every remake costs £4.50—here’s how to stop them happening at all

A remake is not a mistake. It is a £4.50 loss every time it happens. That is £135 for every 30 covers, or £2,700 a week if you serve 600. The cost is not just the food—it is the labour of the chef who makes it, the server who takes it back, and the customer who waits. And it is not just the money: it is the reputation. A remake is a broken promise, and customers notice.

The obvious fix is to train staff to get it right first time. But training alone does not stop remakes. The real cause is not carelessness—it is the kitchen’s workflow. If the pass is chaotic, if tickets get lost, if stations are overloaded, then even the best-prepped order will fail. The solution is not to blame the team; it is to redesign the system so that orders cannot go wrong.

Start with the kitchen display. A screen that shows every order in real time, colour-coded by how long it has been waiting, forces the team to see the problem before it becomes a remake. No more tickets getting buried under a pile of new orders. No more chefs guessing what is next. The display tells them exactly what to do, in the right order, so that nothing slips through the cracks.

But a kitchen display alone is not enough. The next step is to route tickets automatically. If a burger goes to the grill station and a salad to the prep line, then the team knows where to focus. No more arguments over who is doing what. No more orders getting forgotten because they were not in the right place. The system handles the routing, so the team can handle the cooking.

Finally, track the remakes. Not just the number, but the reason. Was it undercooked? Overcooked? Wrong ingredients? Missing sauce? Once you know where the failures happen, you can fix the process. Maybe the grill needs a timer. Maybe the prep station needs a checklist. Maybe the sauce bottle is empty. The point is to make the kitchen so predictable that a remake becomes impossible.

The result is not just fewer remakes—it is faster service, happier customers, and a kitchen that runs like clockwork. The cost is not in the training or the software; it is in the time you waste now, every single shift.

Read how to cut remakes without slowing the pass.

The three reasons remakes happen—and how to fix them

Remakes do not happen by accident. They happen because of three predictable failures in the kitchen workflow:

Orders get lost. A ticket slips under another, or a chef forgets it in the rush. The customer waits, the food goes cold, and then it has to be remade.
Orders get mixed up. A burger and a steak swap places, or a side is added to the wrong table. The customer notices, and the kitchen has to start again.
Orders take too long. A dish sits in the pass for 10 minutes because the wrong station is working on it. By the time it gets to the customer, it is ruined.

Each of these has a technical name—ticket flow, order accuracy, prep time—but the solution is the same: make the kitchen’s workflow visible. If the team can see every order, where it is, and how long it has been waiting, then none of these failures can happen.

The fix is not to add more staff. It is to redesign the system so that the team cannot fail. A kitchen display shows every order in real time, so nothing gets lost. Automatic routing sends each ticket to the right station, so nothing gets mixed up. And colour-coding by wait time ensures that nothing takes too long.

The cost of a remake is not just the food. It is the labour of the chef who makes it twice, the server who takes it back, and the customer who waits. And it is the reputation. A remake is a broken promise, and customers remember.

How to track remakes—and why most restaurants get it wrong

Most restaurants track remakes by counting them. But counting alone does not tell you why they happen. You need to know the reason—undercooked, overcooked, wrong ingredients, missing sauce—to fix the process.

Start by logging every remake for a week. Not just the number, but the cause. Was it a mistake in the kitchen? A communication error at the pass? A missing ingredient? Once you have the data, you can see where the failures cluster.

For example, if 60% of remakes are undercooked, then the issue is not training—it is timing. The grill needs a better system to track doneness. If 40% are wrong ingredients, then the prep station needs a checklist. If 20% are missing sauce, then the bottles need to be restocked more often.

The key is to track the reason, not just the number. A remake is not a failure of the team; it is a failure of the system. And systems can be fixed.

The hidden cost of remakes: it’s not just the food

A remake costs £4.50. That is the food, the labour, and the lost customer goodwill. But the real cost is the time. Every remake means a chef has to stop what they are doing, remake the dish, and then get back on track. That is time that could have been spent on the next order.

And it is not just the kitchen. The server has to take the remake back, apologise to the customer, and then explain the delay. That is time that could have been spent on the next table. The customer has to wait longer, which means they are less likely to come back.

The hidden cost is the opportunity cost. Every remake is a lost sale, not just because of the money, but because of the experience. A customer who gets a remake once is less likely to return. A customer who gets a remake twice will never come back.

The fix is not to accept remakes as part of the cost of doing business. It is to redesign the kitchen so that they cannot happen.

How to cut remakes by 80% without adding staff

The fastest way to cut remakes is to make the kitchen’s workflow visible. A kitchen display shows every order in real time, so nothing gets lost. Automatic routing sends each ticket to the right station, so nothing gets mixed up. And colour-coding by wait time ensures that nothing takes too long.

Here is how to do it:

Install a kitchen display. Every order appears on screen as soon as it is placed, with a timer showing how long it has been waiting. No more tickets getting buried under a pile of new orders.
Route tickets automatically. Burgers go to the grill, salads to prep, desserts to the oven. The system handles the routing, so the team can focus on cooking.
Colour-code by wait time. Orders that have been waiting too long flash red. Chefs see the problem before it becomes a remake.
Track the reasons. Log every remake for a week, and you will see where the failures cluster. Fix the process, not the people.

The result is a kitchen that runs without mistakes. No more remakes. No more wasted time. No more lost customers.

See how it works in a real kitchen.

The trade-off: speed vs accuracy—and why you should pick neither

Most kitchens choose between speed and accuracy. Fast service means more orders, but more mistakes. Careful cooking means fewer remakes, but slower tables. The trade-off is a false choice.

The solution is to make the kitchen so efficient that speed and accuracy are the same thing. If every order is visible, routed correctly, and tracked in real time, then the team can work faster and more accurately. No more choosing between the two.

The key is visibility. If the team can see every order, where it is, and how long it has been waiting, then they can work smarter, not harder. The result is faster service, fewer remakes, and a kitchen that runs like clockwork.

The edge case: when remakes are not the problem

Not every remake is a failure. Sometimes, a customer changes their mind. Sometimes, a dish is ruined by an accident. And sometimes, a remake is just part of the service—like a coffee that needs reheating.

The question is not whether remakes happen. It is whether they are avoidable. If a remake is caused by a mistake in the kitchen—wrong ingredients, undercooked food, missing sauce—then it is a failure of the system. If it is caused by a customer’s change of heart, then it is just part of doing business.

The fix is to track the reason. Log every remake for a week, and you will see which ones are avoidable and which are not. Then, focus on fixing the system, not the people.