Restaurant prep lists and par levels: prep the right amount every day

Walk into most kitchens at 8am and prep is running on memory. The opener looks in the walk-in, thinks about how busy last night felt, and starts cutting. On a slow Tuesday that habit quietly fills the bin with dated product. On a busy Friday it 86’s your best seller at 7:40pm. A restaurant prep list fixes both problems, but only if the quantities on it come from somewhere real. That somewhere is your sales data, and the bridge between the two is a par level.

What a restaurant prep list actually is

A prep list is the day’s production plan: every item the kitchen makes ahead of service, who makes it, how much they make, and what container and date label it goes into. A good one is boring on purpose. The line cook shouldn’t have to decide anything — the list says diced onion, two 6-inch sixth pans, use the batch from Sunday first. The thinking happened earlier, once, when the pars were set.

The difference between a prep list and a to-do list is the quantity column. “Make ranch” is a to-do. “Make ranch: on hand 2 qt, par 6 qt, prep 4 qt” is a prep list. Without the numbers, every cook preps to their own comfort level, and comfort level is usually “more than we need” — nobody gets yelled at for over-prepping until the month-end food cost percentage comes in high and nobody can say why.

Par levels: the number that does the thinking

A par level is the amount of a prepped item you want on hand at the start of service — enough to get through the day plus a cushion, and no more. Every line on the prep list is then simple arithmetic: prep amount equals par minus what’s already on hand. Count what you have, subtract, and the list writes itself.

The classic ordering formula — average weekly usage plus safety stock, divided by deliveries per week — works for raw goods you buy. For prepped items the horizon is shorter: you’re usually setting a daily par, and the driver is how much you sell of each menu item on that day of the week, times how much of the prepped item each portion uses.

How to set pars from your sales data

• Pull a product mix report for the last 4–6 weeks from your POS and look at sales by day of week. Tuesdays and Fridays are different restaurants; they need different pars.
• For each prepped item, list which menu items use it and roughly how much per portion. Sold 60 burgers on a typical Friday and each takes an ounce of sauce? That’s about 2 quarts of demand before you add anything else that uses it.
• Add a cushion of roughly 10–20% for the swings you can’t predict. Perishable and slow-moving items sit at the low end; cheap, stable, high-velocity items can carry more.
• Round to containers your kitchen actually uses — pans, quarts, hotel pans — not grams. Cooks count containers, and pars written in containers get followed.
• Revisit pars every few weeks and after any menu change. A par set in July is wrong by October.

Notice what this replaces: it replaces asking your most experienced cook to carry the whole demand model in their head. That knowledge is real, but it walks out the door on their day off. Pars written down are the kitchen’s memory, and they’re what makes a prep list survive staff turnover and day-off gaps.

A prep sheet that runs itself

The working document needs six columns. Here’s a slice of what a real one looks like mid-morning:

The count column is the discipline point. If nobody counts on-hand before prepping, the sheet degrades into the same guessing it replaced — cooks skip the count, prep to par from zero, and you over-produce exactly the way you used to. Thirty minutes of counting at open pays for itself every single day.

Shelf life changes the math

Par answers how much; shelf life answers how often. A three-day item can be batched twice a week at a higher par. A same-day item like cut avocado needs a tight daily par because yesterday’s surplus is today’s waste, full stop. When two items compete for the same prep hour, the shorter shelf life wins the fresher slot. This is also where batching discipline ties into your inventory counts — variance between what you prepped and what you sold is the earliest warning you have that pars are drifting or product is walking.

Where your POS fits in

None of this requires software, but the demand side gets a lot less manual when your sales history is one report away. A POS that tracks product mix by daypart and day of week hands you the demand line for every par. If online ordering runs through the same system instead of a separate tablet, those orders are in the same numbers instead of being the surprise that blows through your Friday par. And if you run more than one store, multi-location reporting lets you set pars per location instead of copying the flagship’s numbers everywhere. That’s the quiet argument for one platform: the prep list is only as good as the sales data underneath it.

Common mistakes that quietly cost money

• One par for every day of the week. Weekend pars on a Tuesday are a standing order for waste.
• Pars in raw weight instead of containers. If the sheet says 2.3 kg and the cook thinks in sixth pans, the sheet loses.
• No on-hand count before prepping. Prep-to-par only works if you subtract what exists.
• Setting pars once and never touching them. Sales mix moves; pars that don’t move with it are just old guesses with a laminated cover.
• Letting the prep list live in one person’s head. If the list can’t run without a specific human, you don’t have a system yet.

Start small. Pick your ten highest-volume prep items, set day-of-week pars from the last month of sales, and run the count-subtract-prep loop for two weeks. Most kitchens see the bin get lighter and the 86 board get shorter in the first week — and the opener stops making forty decisions before 9am.