Kitchen operations · Prep & mise en place
Saturday is the most predictable night of the week, and still the night prep dies - because adjectives fail under pressure. The systems that hold replace every 'plenty' with a number and every panic with a protocol.
Why prep breaks
A Saturday night rush is the most predictable event in hospitality - same day, roughly the same volume, every single week - and yet it is the night prep systems die. The failure is rarely quantity. It is precision. "Plenty of sauce" and "a good amount of garnish" are prep instructions that survive a Tuesday and collapse at 7:45 on Saturday, when a chef reaches for the third backup container that someone was sure existed. A prep system that survives the rush replaces every adjective with a number.
The number is the par level: for each prepped item, the quantity a full Saturday service consumes plus a defined safety margin, written down per station. Pars are built from sales history, not memory - last six Saturdays' dish counts translated into portions of each component - and they are reviewed monthly, because menus drift and a stale par is just a confident guess. Once pars exist, the daily prep list writes itself: par minus what is genuinely in the fridge, checked by eye and label rather than recollection.
The system
A single kitchen-wide prep list guarantees that the least glamorous items - the garnishes, the dressings, the backup portions - get orphaned. Each station owns its list, sequenced so the longest lead-time items start first and the fragile items finish last. The list is physical, ticked as completed, and signed - because a signature turns "I think it's done" into "it's done".
In the rush, nobody has time to open lids and sniff. Standardised container sizes per item mean a glance at the shelf is a stock count; day-dot labels with name, date and station mean rotation needs no judgement; and a fixed home for every item means the backup sauce is where it was last Saturday and every Saturday. The walk-in is arranged as a map: first-to-use at the front, FIFO physically enforced, nothing on the floor, nothing anonymous.
Rush-proof prep is staged, not hoarded. Components are prepped to par, but finished only in waves the service can sell inside each item's quality window - dressed salads that hold twenty minutes are made through service; the braise that improves overnight is made Thursday. The prep list should encode this: prep day, finish window and holding method per item, so Saturday's 5pm push is assembly, not cooking.
The difference between a wobble and a collapse at 8pm is whether running low triggers a protocol. Each high-velocity item carries a trigger point - at two portions of the top seller's sauce, the call goes out - and a named response: who drops what, where the reserve lives, what the substitution is if the reserve is gone. Written once, rehearsed once, it removes the Saturday-night improvisation that wrecks three other stations to save one.
The rush is lost or won in the reset that precedes it. Saturday afternoon's checklist - fridges restocked to par, stations mapped, bins empty, floors dry, containers closed and dated - hands the evening brigade a kitchen at zero. And the reset has a structural layer: a kitchen running its heaviest sessions every weekend is depositing grease at the fastest rate in its ductwork and canopy, which is why heavy-use kitchens sit at the short end of the TR19 Grease cleaning intervals - typically around three months for 12-to-16-hour days. A line that gets hotter and smokier as Saturday builds is a prep system fighting its own air; check the extraction cleaning interval matches the trade you actually do now.
Keeping it alive
The cheapest prep-system audit is Sunday's walk-in. What ran out on Saturday tells you which pars are low; what is still there in quantity tells you which are high; what is unlabelled tells you where discipline slipped when pressure rose. Ten minutes with a notebook, four Sundays in a row, and the system re-tunes itself to the trade you actually have. Prep systems do not survive Saturday because they are clever. They survive because someone keeps them honest on Sunday.
Questions
A par is the quantity of each prepped item a full service consumes plus a defined safety margin, written per station. Build it from the last six same-weekday sales translated into component portions, not from memory, and review it monthly - a stale par is just a confident guess.
Give every high-velocity item a trigger point and a named protocol: at a set number of portions remaining, a specific person drops a specific task, the reserve's location is known, and a substitution is pre-agreed. Collapses happen when running low triggers improvisation instead of a plan.
Yes. TR19 Grease sets cleaning frequency by use, and its indicative bands put heavy-use kitchens - 12 to 16 hours of daily cooking, which weekend-heavy sites hit in bursts - at roughly three-month intervals. The interval should be set by a measured survey of your actual grease load, not by the calendar.
Phoenix Duct Clean · by the numbers
Weekend-heavy kitchens load grease fastest. We survey and clean extract systems to TR19 Grease overnight - no extra charge for out-of-hours, so the work never costs a Saturday.