Restaurant Prep List System

Reliable prep is not inspiration. It is math plus ownership plus a feedback loop. Every batch item should have a documented yield, a realistic shelf life, and a pull time that matches how fast you move it. Plate builds should separate mise tasks so stations know what “ready” means before service.

Build pars from history, not hope. Start with two weeks of daily notes on run outs, waste, and 86 frequency by item. Adjust pars by day of week before you blame the line for over prep. Promotions and events need explicit adders so the list does not rely on a manager whispering “make extra.”

Assign stations and due times. Prep without owners becomes the person who showed up earliest. Escalate misses early: if midday prep slips, expo should know before the board fills.

When the system stabilizes, automate the rhythm inside your ops tool so open and midday blocks are consistent across locations. That removes personality variance between strong and average leads.

Restaurant Codex links Operational prep tasks to recipe and batch specs in the Knowledge Base so execution matches training. LMS modules can refresh technique when a spec changes, not six weeks later when a guest complains.