Restaurant Daily Prep Lists That Work

Ask a line cook what went wrong on a bad service and the answer is almost always a prep failure: they ran out of something critical, they were still finishing prep when the first tickets came in, or they made too much of an item that did not sell and had to throw it out at close. All three of these failures trace back to the prep list — either it was wrong, it was not followed, or it did not exist.

The prep list is the operational backbone of a kitchen. It translates projected sales into specific tasks, assigns those tasks to specific people with specific deadlines, and creates accountability for whether each task is completed correctly and on time. A kitchen that runs on good prep lists runs smoothly. A kitchen that runs on instinct and habit runs chaotically and expensively.

Why Most Restaurant Prep Lists Fail

Many kitchens have prep lists, but most of them have the same problems:

• Static quantities: The list says "prep 10 lbs salmon" every day regardless of whether it is a slow Tuesday or a busy Saturday with a private party of 40. The quantities are not connected to projected demand.
• No on-hand column: Cooks prep the full quantity on the list without checking what is already made from yesterday's prep. The result is over-production and waste.
• No ownership: The list is posted on the wall, but no specific cook is assigned to each item. When something does not get done, there is no accountability.
• No completion times: Everything is due "before service," which means everything gets started at the same time and the time-sensitive items are not prioritized.
• Not updated weekly: The list reflects last season's menu or last year's sales volume and has not been recalibrated to current reality.

The Anatomy of an Effective Prep List

A prep list that actually works has seven fields for every item:

The "On Hand" and "To Make" fields are what separate a functional prep list from a static one. They require a beginning-of-shift walk through the walk-in and prep areas, counting what is already made. This takes 10-15 minutes for most kitchens and prevents the single most common prep waste: making a full batch of something when half a batch from yesterday is perfectly usable.

Building the Prep Guide: The Data Foundation

The "Par / Needed" field is only as good as the data behind it. The prep guide template — the baseline quantities before daily adjustment — must be built from actual sales data, not the chef's memory of busy nights.

Step 1: Pull POS Sales Data

Export item count data from your POS for the past 8-12 weeks. Break it down by day of week and by daypart (lunch, dinner, late night if applicable). What you are looking for is the average number of portions sold for each menu item on each day type. A Tuesday lunch and a Friday dinner are fundamentally different prep environments and should have different par quantities.

Step 2: Calculate Prep Quantity per Item

For each item, the calculation is:

Prep Par = (Average Portions Sold per Service x Portion Size) + 15% Buffer

The 15% buffer accounts for volume variance, a dropped batch, or a slightly busier-than-average day. It is not a license to over-prep by 50%. Over-buffering is as damaging as under-prepping — it just manifests as waste rather than 86s.

For items with high carryover potential (stocks, sauces, dry-brined proteins), the par can be set lower than a single day's usage since these items can be held safely for 2-4 days. For highly perishable items (fresh fish, cut fruit, dressed salads), prep quantities should be tighter and matched more precisely to same-day demand.

Step 3: Set Completion Times by Priority

Not all prep items are equal in urgency. Assign completion times that reflect the actual service timeline:

• Critical path items (the thing that, if not ready, stops service): due 45-60 minutes before service.
• Standard line items (proteins, sauces, components used in multiple dishes): due 30 minutes before service.
• Support items (garnishes, accompaniments, items with large batch yields): due by service start.
• Ongoing prep (stocks, braises, items that cook all day): started at open, not due until mid-service or end of day.

Organizing Prep Lists by Station

A single master prep list posted on the wall is hard to use in a working kitchen. Break it into station-specific lists printed or displayed at the point of use:

• Cold prep list: All items made in the cold prep area. Butchery, portioning, salad components, cold sauces, house-made condiments.
• Hot prep list: Stocks, braises, roasted components, soups, sauces requiring cooking. Often the longest list in terms of time required.
• Line prep list: Items each line station needs in its mise en place for service. These are the final quantities that go into the line setup, drawn from the larger cold and hot prep batches.
• Pastry/bakery list: If applicable, separate from savory prep due to timing and temperature requirements.
• Bar prep list: Fresh juices, batched cocktail components, garnish prep, infusions.

The Opening Chef Walk and Sign-Off

The opening chef or kitchen manager should walk every station 30 minutes before service and physically verify that each prep item is complete, at the correct quantity, properly labeled with date and time, and stored at the correct temperature. Any incomplete prep item is escalated immediately — either the cook who was assigned it completes it urgently, or a decision is made to 86 the affected dish for that service.

The opening chef signs the prep list to confirm the walk was completed. This signature creates accountability and a documentation trail that protects both the manager and the operation. If a guest becomes ill from improperly stored prep, a signed and dated prep list showing correct temperatures and completion times is an important part of your defense.

Connecting Prep Lists to Waste Reduction

A prep list that is calibrated to actual demand is a direct waste reduction tool. When your cold prep cook makes exactly 8 lbs of portioned salmon based on a Friday dinner par that reflects actual Friday dinner sales, you will use nearly all of it. When the same cook makes "a full sheet tray" based on habit, the variance between what was made and what was sold goes into the waste log — or worse, is not tracked at all.

Connect your prep list system to your waste log. When a prep item is discarded at shift end, note it on the waste log with the quantity and reason. Review this data weekly. If the same item appears on the waste log more than twice in a week, your prep par for that item is too high and needs adjustment. This feedback loop keeps your prep guide accurate as your sales patterns evolve. For the complete waste reduction framework, see our restaurant waste reduction guide.

Digital vs. Paper Prep Lists

Both formats work. The choice depends on your operation's infrastructure and your team's comfort level.

Paper Prep Lists

Advantages: low cost, accessible to all staff regardless of tech comfort, easy to annotate during the shift, no dependency on hardware or software. Disadvantages: must be reprinted or rewritten daily, quantities must be updated manually, data from completed lists is not automatically analyzed.

Digital Prep Lists

Back-office software integrated with your POS can auto-populate prep quantities from actual sales data, carry forward on-hand quantities from the prior shift's closing inventory, and track completion status in real time. Kitchen display systems can display station-specific prep lists at the point of use without printed sheets. The investment in setup pays back in management time and data accuracy within weeks for most kitchens doing $800K or more in annual revenue.

Whether paper or digital, the disciplines are the same: data-driven quantities, on-hand counts, station assignments, completion times, and opening chef sign-off. The format is secondary. The system is primary.

For a complete picture of how prep lists fit into your daily kitchen management cycle, see our restaurant manager daily checklist, which integrates prep sign-off, line check, and shift accountability into a single opening-to-close framework.