How to Set Prep Pars for a Smoother Kitchen

The lunch rush is not the time to discover that the line is out of diced onions, cooked rice, or portioned chicken. But overprepping is not the answer either. Pans of food that expire untouched cost your restaurant money just as surely as an 86 costs a sale. Knowing how to set prep pars gives your kitchen a practical middle ground: enough product to execute every shift, without turning your walk-in into a waste problem.

Prep pars are not fixed guesses. They are working targets based on what you sell, when you sell it, how much each menu item uses, and how long the prepared product stays usable. When those targets are documented and reviewed, prep becomes a controlled system instead of a daily argument between the kitchen and the floor.

What Prep Pars Should Do for Your Kitchen

A prep par is the target quantity of a prepared ingredient or component you need on hand for a defined period, such as one lunch shift, one full day, or a weekend service. It answers a simple operational question: how much should the team prepare before service so they can meet expected demand?

A good par level protects speed, food quality, and labor. Cooks do not have to stop mid-rush for an emergency batch. Managers are less likely to overreact by telling the team to prep “a lot.” And the person opening tomorrow is not left sorting through aging product with unclear labels.

Prep pars work best for ingredients that are used across multiple menu items or require meaningful time to prepare. Think sliced vegetables, sauces, cooked proteins, pizza dough, rice, pre-portioned sides, dressings, and batch beverages. A par for each component creates a clearer production plan than trying to estimate every menu item independently.

The target should not always be the same. A Tuesday lunch par can be very different from a Friday dinner par. Catering orders, local events, weather, delivery promotions, and seasonal menu changes can all change demand. The goal is a repeatable baseline that gives managers a reason to adjust, rather than relying on instinct alone.

How to Set Prep Pars From Real Sales Data

The most reliable prep pars start with sales history, not with what the team feels busy making. Pull at least two to four weeks of POS sales by daypart when possible. If your restaurant has strong weekly patterns, use the same day of the week for comparison. Friday sales should guide Friday prep more than Monday sales.

Start with your highest-volume menu items and the components that cause the most disruption when they run out. You do not need to perfect every prep item on day one. Focus first on the products that drive the most sales, take the longest to replace, or create the most waste.

Calculate expected portions

For each component, identify how many menu items use it and the standard portion in each item. For example, if a restaurant sells 60 chicken bowls and 20 chicken wraps on an average lunch shift, and each uses 5 ounces of cooked chicken, expected usage is 400 ounces:

`(60 bowls x 5 ounces) + (20 wraps x 5 ounces) = 400 ounces`

That is 25 pounds of usable cooked chicken. If the kitchen wants a small service buffer, it might set the lunch par at 27 pounds. The buffer should cover normal variation, not compensate for poor portion control or missing sales data.

For an ingredient used in several recipes, build the calculation from every relevant menu item. A house sauce used on tacos, bowls, and sandwiches needs a combined usage estimate. This is where clean POS menu setup and standardized recipes matter. If modifiers, sizes, or ingredients are entered inconsistently in the POS, the sales data will not tell the full story.

Factor in yield before setting the prep amount

A prep par should be based on usable product, not the raw case weight. Ten pounds of raw chicken may not yield ten pounds of cooked, portion-ready chicken. Produce trimming, cooking loss, draining, and slicing all reduce usable yield.

If 10 pounds of raw chicken produces 7.5 pounds of cooked chicken, the yield is 75 percent. To reach a 27-pound cooked chicken par, the kitchen needs to start with 36 pounds of raw chicken. Without this step, prep sheets look accurate on paper but consistently leave the team short.

Document yields during a normal prep shift. Weigh the raw product, complete the standard preparation method, then weigh the finished usable product. Do this more than once if the item has variable quality or different vendors. A real yield number also improves ordering and food cost control.

Match the par to the prep cycle

Not every item needs a full-day par. Highly perishable products may need separate pars for lunch and dinner. A sauce with a five-day shelf life may be better prepared in a two- or three-day batch, depending on storage space and volume. Labor availability matters too. A component that takes 45 minutes to make during service needs a more protective par than one a cook can replenish in five minutes.

Define the time period beside every par. Instead of writing “Rice: 20 pans,” write “Rice: 20 pans for lunch” or “Rice: 20 pans by 4 p.m. for dinner.” This removes ambiguity and helps the team see when a batch is meant to last.

Build a Prep Sheet the Team Can Actually Use

A prep par only works when it becomes part of a simple daily tool. The prep sheet should tell the cook what to make based on what is already available, not just show a static target.

For each prep item, include the par, the unit of measure, the amount on hand, and the amount to prep. The basic calculation is:

`Par – usable amount on hand = amount to prep`

If the dinner par for pico de gallo is 12 quarts and the team has 4 usable, properly dated quarts in the walk-in, the cook preps 8 quarts. The word usable matters. Do not count product that is expired, poorly stored, unlabelled, or unlikely to meet quality standards through service.

Use units your team can measure quickly and consistently. If the kitchen works in hotel pans, sheet pans, quart containers, scoops, or portion bags, choose one of those units and define it clearly. “One pan” is not a useful standard if different cooks fill pans to different levels. A prep sheet should specify the pan size, fill line, portion count, or weight when needed.

Keep the sheet organized by station or prep sequence. For example, cold station items can be grouped together while cooked proteins and hot sides appear in the order they are produced. A long alphabetical list may look tidy in a spreadsheet, but it slows down execution in a working kitchen.

Add Buffers Carefully, Not Emotionally

A buffer is extra product above expected demand. It is useful, especially for high-selling items, unpredictable delivery volume, or products that cannot be remade quickly. But every buffer has a cost in product, storage, labor, and potential waste.

For most stable, high-volume items, begin with a modest buffer of 5 to 15 percent. A restaurant with highly variable sales may need more, while a restaurant with limited cold storage or short shelf life may need less. The right number depends on the cost of an 86 compared with the risk of throwing product away.

Do not add a blanket 25 percent to every item. That approach hides the real issue. If one ingredient is regularly running out, determine whether sales are higher than expected, portions are too large, the yield is wrong, or the cook is not following the sheet. Each problem needs a different fix.

Test Pars During Service and Adjust Weekly

Your first par levels are hypotheses. Run them for one to two weeks and capture what happens. Did the kitchen run out? How much was left after service? Was the leftover product still within its approved shelf life and likely to be used? Were emergency batches needed, and at what time?

Managers should review these notes on a weekly schedule, not only after a bad shift. Increase pars when stockouts are recurring and sales support the change. Reduce pars when usable leftovers repeatedly carry over or get discarded. A small adjustment of one pan, two quarts, or five portions can make a meaningful difference over a month.

Separate true demand changes from execution problems. If the recipe calls for 4 ounces of cheese but cooks are using 5 ounces, the solution is portion control, not a higher cheese par. If online orders are not flowing into the same reporting system as in-store sales, fix the data source before changing prep targets. Accurate pars depend on accurate recipes, accurate sales channels, and staff who can follow a consistent process.

Common Reasons Prep Pars Fail

Prep systems usually fail because the restaurant uses one number for every day, ignores inventory already on hand, or lets recipes remain informal. Another common issue is building a detailed sheet once and never training the team on how to read it. A prep list is not an SOP unless the cook understands the units, quality standards, labels, and handoff expectations behind it.

Avoid changing several variables at once. If you revise the recipe, change the portion tool, and raise the par in the same week, you will not know what improved or created waste. Make one clear adjustment, document it, and review the result.

For multi-unit restaurants, keep the framework consistent while allowing each location to have its own pars. A downtown location with strong weekday lunch traffic should not be forced to follow the same prep levels as a suburban location built around family dinner and weekend sales.

A well-set par does more than prevent an 86. It gives your team a calmer starting point, makes waste visible, and turns prep from guesswork into a daily operating standard. Start with the few items that create the most pressure, review the results with your staff, and let the numbers earn the next adjustment.