The Complete Guide to Par-Based Prep Lists for Restaurant Kitchens

Every kitchen preps. The question is whether prep happens by memory and instinct or by a system that survives a busy Friday, a new hire on the line, and a manager taking a day off. A par-based prep list is that system. It starts with a simple idea: for every prepped item, decide how much you want on hand at the start of service, count what you actually have, and prep the difference. That sounds obvious, and in a sense it is. The hard part is doing it consistently, keeping the numbers honest, and adjusting them as your menu, your volume, and your week change shape. Most kitchens that struggle with prep are not short on effort. They are short on structure, and structure is something you can build in a few weeks if you know where to start.

This guide is the hub for everything we have written about kitchen prep and production. It walks through the full cycle: setting pars, counting on hand, converting the gap into batch sizes with real yields, assigning tasks across stations, diagnosing over prep and under prep, and using history to tighten pars season after season. Each section links to a deeper article on that topic. We build prep software, so we have opinions about tools, but the principles here work whether your prep list lives on a clipboard, in a spreadsheet, or in an app. Start wherever your kitchen hurts the most, and come back to the rest when you are ready. Nothing here requires a big rollout. Most of it is a matter of deciding a few things once and writing them down where the team can see them.

Par levels are the foundation of every prep list

A par level is the quantity of a prepped item you want available at a defined moment, usually the start of a service or the start of a day. It is not a maximum and it is not a guess about how much you will sell. It is a target that accounts for expected usage, a safety cushion for variability, and the shelf life of the item. A quart of house vinaigrette that holds for a week can carry a generous par. A pan of sliced avocado that browns in hours cannot. When pars are set well, the prep list almost writes itself: par minus on hand equals what to prep. When pars are set badly, no amount of hustle on the line fixes the result, because the team is working hard toward the wrong number.

The most common mistake is setting pars once and treating them as permanent. Demand in a restaurant moves with the day of the week, the season, local events, and the weather. A par that is right for a Saturday dinner is wrong for a Tuesday lunch, and a par sheet that ignores this forces the team to either over prep on slow days or scramble on busy ones. The fix is to keep pars per item and per day type, and to revisit them on a regular cadence, not only when something breaks. Our article on building a prep list from pars covers the mechanics step by step, and our piece on pars by day of the week explains how to structure the variation without creating a sheet nobody can read.

Pars also need a unit that matches how the item is actually counted. If cooks count diced onion in hotel pans, the par should be in hotel pans, or at least in a unit that converts cleanly. Mixing weights, volumes, and container counts on the same sheet invites rounding errors and arguments. Pick the unit that is fastest to eyeball in the walk-in and stick with it. Where precision matters, such as portioned proteins or sauces with a fixed recipe, use a count or a weight. Where it does not, such as a bulk mirepoix, a container count is fine. The goal is a number the closing cook can verify in seconds, not a number that looks rigorous on paper and gets guessed at in practice.

Finally, treat pars as a shared agreement, not a private number in the chef's head. When the whole team knows the target for each item, they can flag when it looks wrong. A lead who notices that the cut lemons par is always double what gets used is giving you free data. Write pars down where the team can see them, explain the reasoning when you change one, and expect them to move over time. A living par sheet is a sign of a kitchen that is paying attention. A par sheet that has not changed in a year is a sign that nobody is looking at it, no matter how neat it is.

Counting on hand, the step that makes or breaks the list

The prep list is only as good as the count that feeds it. Par minus on hand is simple math, but if the on-hand number is a rough memory from the closing shift, the resulting prep quantity carries that error straight into the next day. Counts drift for predictable reasons: items stored in more than one place, partially used containers that get counted as full or ignored entirely, items that were made but not labeled, and counts taken at the wrong time. A count taken before the dinner rush tells you nothing about what is left at close, and a count that skips the reach-in on the line misses whatever was pulled for service.

Speed and accuracy are not in conflict if the count is designed well. The best counts follow the physical layout of the walk-in and the line, so the person counting walks one path and never doubles back. The list is ordered the way the shelves are ordered, not alphabetically. Units match what is on the shelf. Anything that is always prepped fresh and never carried over does not need to be counted at all. Our article on counting prep fast and accurately goes into the practical details, including how to handle partial containers, what to do about items that live on the line during service, and how to keep the count from turning into a twenty-minute chore that gets skipped on busy nights.

Timing matters as much as method. The cleanest count happens at close, after the last ticket and before the walk-in is locked up, because that is the moment the on-hand quantity is stable. Some kitchens count first thing in the morning instead, which works as long as nothing is used between the count and the prep. What does not work is counting whenever someone remembers. A fixed time, a fixed path, and a fixed owner turn the count from a chore into a habit, and habits are what make the rest of the system trustworthy. If the owner changes from night to night, the method drifts and the numbers drift with it.

One more point that is easy to miss: the count should feed directly into the prep list without a manual transcription step. Every time a number is copied from a clipboard to a spreadsheet to a whiteboard, there is a chance for it to change. If the count and the list live in the same place, whether that is a single sheet or a single screen, the gap calculation happens once and the whole team sees the same number. Our guide to building a prep list from pars shows how the count and the list fit together as one workflow rather than two documents that have to be reconciled every morning.

From par to batch: yields, batch sizes, and recipe math

Knowing you need three more quarts of salsa verde is not the same as knowing what to cook. Recipes have yields, and yields have variability. A recipe that says it makes four quarts might make less on a day when the tomatillos are smaller or the reduction went a little long. A cook who scales a recipe up by half and rounds every ingredient loses a little more. If the prep list says three quarts and the recipe makes four, does the cook make one batch and over prep by a quart, or make three quarters of a batch and risk under prepping? That decision, repeated across forty items every day, is where a lot of waste and a lot of 86s come from.

The fix is to record the real yield of each recipe, not the theoretical one, and to define a sensible batch size for each item. Some items should only be made in whole batches because the recipe does not scale cleanly or the equipment has a fixed capacity, such as a stock pot, a mixer bowl, or a sheet tray. Others can be scaled freely. When the prep list shows the gap in the same unit as the batch, and rounds to the nearest practical batch, the cook does not have to do arithmetic on the fly. Our article on recipe yields and batch sizes walks through how to measure yields honestly, how to set batch rules per item, and how to write them so a new cook applies them the same way the veteran does.

Batch rounding is also where you make a conscious trade between labor, waste, and stock outs. Rounding up on a long-shelf-life item costs little and protects service. Rounding up on a short-shelf-life item creates waste you will see in the trash on Monday. Rounding down on a high-velocity item risks running out mid-service. There is no universal rule, which is why the batch decision should be made once per item, written down, and applied consistently rather than reinvented by whoever is on prep that morning. Our piece on reducing over prep and under prep explores how batch rules interact with pars to push both problems down at the same time instead of trading one for the other.

Assigning prep across stations and people

A list of forty items with quantities is not yet a plan. Someone has to decide who does what, in what order, and by when. In small kitchens this happens informally: the sous chef reads the list and calls out assignments. That works until it does not, usually when the sous chef is off, when two people both assume the other one is doing the pickled onions, or when the item that takes the longest starts last and is not ready for service. Assignment is the step that turns a list into a schedule, and it deserves the same care as the pars themselves.

The cleanest approach is to group prep tasks by station, matching the person who will use the item during service where possible, and then sequence by lead time and shared equipment. Anything that needs the oven, the braise, or a long cool-down starts first. Anything that must be prepped fresh and close to service starts last. Tasks that compete for the same mixer or the same slicer get spaced out so nobody stands around waiting. Our article on assigning prep tasks across stations covers how to structure this so nothing gets missed and no station is overloaded while another sits idle, including what to do when one person covers two stations on a short-staffed day.

Ownership is the other half. When each task has a name attached and a way to mark it done, the manager can see progress without walking the line every fifteen minutes, and the team can see what is left without asking. Handoffs between shifts become explicit: the morning crew marks what was finished, the afternoon crew picks up the rest. This is also the foundation for a prep list that runs without you. If the assignments, the sequence, and the batch rules are written down, any capable lead can run the morning. Our piece on making a prep list anyone can run goes into what that documentation needs to include and how much is too much.

A note on fairness and skill. Assigning by station is efficient but it can lock people into the same tasks forever. Rotating a few tasks deliberately builds bench depth so that a call-out does not leave a station without anyone who can make the house sauce. It also surfaces process problems, because the second person to make a recipe will find the ambiguity the first person learned to work around. Treat assignment as both a daily logistics decision and a slow training program, and the kitchen gets more resilient every month without anyone noticing a special effort.

Over prep and under prep: reading the symptoms

Over prep shows up as waste: containers dated three days ago still half full, staff meals made from things that did not sell, a walk-in that is always crowded. Under prep shows up as 86s, mid-service prep that pulls a cook off the line, and a rush of substitutions that annoy guests and servers. Most kitchens have both at the same time on different items, which is why a blanket instruction to prep less or prep more never works. The problem is per item, and the diagnosis has to be per item too. Fixing the wrong item, or fixing the right item for the wrong reason, just moves the problem somewhere else.

The root causes fall into a small number of buckets. Pars that do not match demand for that day type. Counts that are inaccurate or taken at the wrong time. Yields that differ from what the recipe claims, so a whole batch overshoots or undershoots the gap. Batch rules that round the wrong way for that item's shelf life. And execution problems: an item was on the list but never got made, or was made but never labeled and got counted as missing. Our article on the causes of over prep and under prep provides a structured way to sort each symptom into its bucket, because the fix for a par problem is completely different from the fix for a count problem, and applying the wrong one wastes weeks.

Day-of-week variation deserves special attention because it is the most common cause of both problems in the same week. A kitchen running one flat par across seven days will over prep on its slowest day and under prep on its busiest, then conclude that the par is fine because the average looks right. Splitting pars by day type, even into just two or three tiers, usually removes much of the swing. Our piece on prep pars by day of the week explains how to pick the tiers, how to handle holidays and events that do not fit the pattern, and how to keep the sheet simple enough that the team actually uses it instead of defaulting to the number they remember.

Using prep history to tighten pars

Every count and every prep list is a data point. If you keep them, you can see how much of each item you actually made and actually used, week after week. That record is the only reliable basis for adjusting pars, because it replaces opinions with observations. Without history, par changes happen after a bad night or a full trash can, and they swing too far in the opposite direction. With history, you can see that the Tuesday par for grilled chicken has been consistently high for six weeks and trim it with confidence, or notice that the Saturday par for fries has been hitting zero since patio season started and raise it before the next weekend instead of after.

The habit is simple: keep the completed prep sheets, or keep the data in one place, and review a handful of items every week. Look for items that are consistently left over at the next count and items that consistently hit zero. Check whether the pattern holds across day types or only on some. Adjust one variable at a time, usually the par, and watch the next two weeks before touching it again. Seasonal shifts, menu changes, and new items all reset the clock. Our article on using prep history to tighten pars goes through the review process, what to look for, and how to avoid overreacting to a single unusual day that will not repeat.

History only works if the counts are honest, which loops back to the counting section. A count that is padded to avoid prepping, or rounded up to look good, corrupts the record and leads to worse pars later. This is one reason the fastest, simplest count method tends to be the most accurate: it lowers the temptation to guess. Our guide to counting prep fast and accurately is worth revisiting with history in mind, because a count that seems fine day to day can still hide systematic bias that only shows up over a month, such as one closer who always rounds partial pans up and another who always rounds them down.

Paper, spreadsheets, and prep software

Every tool can hold a par-based prep system. Paper is fast, cheap, and visible on the wall. Spreadsheets add arithmetic and let you keep pars per day. Purpose-built prep software adds shared access, task ownership, automatic gap calculation, and a history you do not have to file in a binder. The right choice depends on the size of the kitchen, how many people touch the list, and how much the manager wants to see without being there. We build prep software, so we are not neutral, but we will say plainly that a well-run paper system beats badly used software every time, and that buying a tool before the pars are sound just makes the wrong numbers easier to distribute.

Where paper and spreadsheets tend to break is scale and handoffs. A single clipboard works for one prep cook and one manager. Add a second shift, a second location, or a manager who is not on site every morning, and the sheet is either being photographed and texted around or being rewritten from memory. Spreadsheets fix the math but not the access problem, and they are fragile when several people edit them. Our article on why paper prep sheets and spreadsheets fail a growing kitchen lays out the specific failure points, and it is honest about the kitchens for which paper is still the right answer.

Whatever tool you use, the test is the same: can a lead who has never seen this list before run prep correctly from it? That requires pars, units, batch rules, station assignments, and sequencing to be written down in one place. Our piece on making a prep list anyone can run is the checklist for that. And if you are starting from scratch, our step-by-step guide to building a prep list from pars is the place to begin, regardless of whether the result ends up on a clipboard or a screen. Get the system right first. The tool is there to make a good system easier to keep, not to invent one for you.

More guides on this topic

Further reading from the PrepDeckr blog, each answering one specific question in depth.

A par-based prep list is not a form. It is a loop: set pars, count on hand, prep the gap in sensible batches, assign the work, run service, and feed what you learn back into the pars. Each part of the loop has a few things that commonly go wrong, and each has a fix that is more about discipline than cleverness. If you take one thing from this guide, make it this: the numbers only help if they are honest, and they only stay honest if the process is simple enough that a tired cook at eleven at night will follow it without shortcuts.

Start with pars and a clean count. Add batch rules and station assignments once the count is reliable. Then use history to tighten, a few items at a time, and keep going. The articles linked above go deeper on every step, and each one stands on its own if you only have time for one problem this week. When you are ready for a tool that keeps the whole loop in one place, we are here. But the system comes first, and it is worth building well on whatever you have.