Kitchen Prep and Par Level Glossary

In most kitchens the terms overlap. A prep sheet is the document or screen where pars and counts are recorded, and a prep list is the resulting set of items and quantities to make today. Some teams use one word for both, which is fine as long as everyone knows where the pars live and where the day's tasks live.

Subtract the on-hand count from the par level for each item to get the prep gap, then convert that gap into batches using the recipe's real yield and the item's batch rules. Items with a zero or negative gap are skipped. The count has to be accurate and taken at a consistent time for the math to hold.

Every item that is prepped ahead and carried over should have one. Items that are always made fresh to order or prepped in full each day do not need a par so much as a fixed daily quantity. Raw ingredients are usually managed through ordering pars, which are related but separate from prep pars.

Start with an estimate based on a comparable item, the expected sales mix, and the new item's shelf life, then treat the first two to three weeks as a test. Count carefully, note leftovers and 86s, and adjust the par once a clear pattern appears. Expect the first number to be wrong and plan to revise it.

At close is typically best, because quantities are stable and the count reflects everything used during service. A morning count works if nothing is used between counting and prepping. The key is a fixed time and a fixed person or role, so the method does not drift from night to night.

The prep gap tells you how much you need; the yield tells you how many batches produce it. If real yields differ from the recipe card, a whole batch may overshoot or undershoot the gap. Measuring yields once and recording them lets the list show batch counts instead of leaving arithmetic to the cook.

Common causes are pars set for the busiest day and applied every day, counts that miss carryover, batch rules that always round up regardless of shelf life, and cooks prepping from memory rather than from the list. Each has a different fix, so diagnosing the cause per item matters more than a blanket instruction to prep less.

Usually pars that are too low for that day type, counts that were padded or taken before the rush, yields that fall short of the recipe, or an item that was on the list but never got made. Reviewing 86s against the prep list and count for that day points to which one it was.

Group tasks by the station that uses the item during service, then sequence by lead time so long items start first and fresh items start last. Space out tasks that compete for the same equipment. Give each task an owner and a way to mark it done so handoffs between shifts are explicit.

Write down everything that normally lives in the chef's head: pars per day type, units, batch rules, station assignments, sequencing, and where each item is stored. Keep it in one place the team can access. If a competent lead can run the morning from the document alone, the system is complete.

Review a few items every week using prep history, and do a fuller pass when the menu changes, a season shifts, or volume moves noticeably. Change one par at a time and watch about two weeks of counts before adjusting again, so a single unusual day does not swing the number.

They struggle with handoffs and access. A clipboard is visible only to whoever holds it, and a spreadsheet is fragile when several people edit it or when it is printed and marked up by hand. Both also make it slow to review history, so pars stop getting tuned. For a single shift with a manager on site, they remain perfectly workable.

Follow the batch rule written for that item. Items that do not scale, such as those limited by pot or mixer capacity, are usually made in whole batches and the rule says whether to round up or down. If no rule exists, the cook should ask rather than guess, and the answer should be added to the list for next time.

Treat the event as a separate line on the prep list with its own quantities, rather than raising the regular pars. That keeps the regular pars honest for tuning and makes it obvious what the event required. After the event, the extra line disappears and the normal numbers continue.