Service systems
Nobody cooks a plate twice on purpose. Re-fires are the ticket system failing in chef whites - and the fixes start with vocabulary, not technology.
Service systems
The night was busy but not exceptional: 140 covers, full brigade, nothing the kitchen had not done before. Yet by 9pm the bin told a different story - a steak fired twice because the first went to the wrong table, three mains dead in the window while a lost ticket was rewritten from memory, a re-fired fish because "no sauce" was scrawled where only the chef who wrote it could read it. Nobody made a bad dish all night. The system serving them the information made a dozen bad calls, and the kitchen paid for each one in food, gas and minutes.
Re-cooks are the most expensive routine waste in a kitchen because everything is spent twice: the ingredients, the energy, the station time, and the goodwill of the table waiting for the replacement. And unlike trim waste or spoilage, they are almost never a cooking problem. They are an information problem wearing chef whites.
What went wrong
Trace any re-fire back and the failure is usually in the handover between front of house and the line. Handwriting that compresses "no dairy, sauce on the side" into two ambiguous marks. Modifiers that live in a server's head rather than on the ticket. Allergy flags that arrive verbally at a station that was mid-plate when they were shouted. Whatever cannot be read the same way twice will, on a long enough Saturday, be read the wrong way once - and the wrong reading costs a full plate.
The second failure is sequencing. A paper rail shows what exists, not what is late, what is fired, or what is waiting on another station. Courses collide, one slow starter strands three fast ones in the window, and food dies at the pass not because anyone was slow but because nobody could see the whole board at once. The plates that die in the window are re-cooks by another name - counted in the same bin, caused two metres further along the same information chain. We took that pattern apart in the real causes of kitchen pass bottlenecks.
The fix
Front of house belongs inside the same system, because half the failures start there. Order-taking has its own drill - allergies and modifiers captured in fixed fields, table numbers confirmed at the till, reading the order back to the guest on anything complicated. Thirty seconds of confirmation at the table is the cheapest quality control in the building; the same ambiguity, discovered at the pass, costs a plate and an apology.
The overlooked line in the re-cook bill is overhead: every plate cooked twice runs the burners, the fryers and the extraction for two services' worth of one sale, and sends double the grease up the same canopy. A kitchen that cuts re-fires cuts its cooking hours at the margin - which is the same arithmetic that sets a cleaning interval, as we set out in reducing food waste in a high-volume kitchen.
Questions
Anything cooked again for the same sale: a plate fired to the wrong table, a missed modifier, a dish that died in the window waiting for the rest of its course, or food remade after a customer bounce-back. Kitchens that only count the last category dramatically undercount - the wrong-table steak and the stranded starter cost exactly the same as a complaint, they just never reach the dining room.
The honest answer is: fix the free things first. A standard modifier vocabulary, one agreed allergy-flag position and a re-fire log cost nothing and remove a large share of errors on their own. A KDS earns its keep when volume, delivery channels or multiple stations make paper routing the bottleneck - at that point the handwriting, lost-ticket and sequencing failures it removes usually repay it within months.
One clipboard or a spare tablet at the pass, four tick-box reasons: wrong table, missed modifier, died in window, kitchen error. Whoever calls the re-fire ticks the box - two seconds, mid-service. The precision matters less than the honesty; after a fortnight the distribution tells you whether the fix is vocabulary, sequencing, menu engineering or training, and the food-cost total tells you what fixing it is worth.
Phoenix Duct Clean · by the numbers
TR19 Grease extraction cleaning banded to the hours your kitchen really cooks - assessed, cleaned and certificated for insurer and fire risk assessment.