A four-top walks in at 6:14 p.m. on a Thursday. Tickets start stacking within minutes. The cook on the line shouts for more chimichurri, the dishwasher is already backed up, and the owner is slicing onions because the prep cook called out. The walk-in has half a hotel pan of cilantro, three tired lemons, and a sheet tray of proteins portioned for a hundred covers that the menu may not actually need. None of this is dramatic. It is just Tuesday, then Thursday, then Saturday, in a kitchen that does not have a working prep system.
A simple restaurant prep list system for small kitchens is the answer most operators reach for too late. It is not software, not a franchise binder, and not a spreadsheet that requires an hour of maintenance each night. It is a short, repeatable way to know what to prep, how much of it, when to do it, and how to hand it off, so the line can move without someone in charge playing hero every shift.
What a simple restaurant prep list system for small kitchens actually does
The phrase sounds larger than the work. A prep list system is the routine that turns yesterday’s sales, today’s covers, and tomorrow’s menu into a list of containers, weights, and portions that someone can execute in a defined block of time. When it works, the cook on prep knows what to pull, the line cook knows what will arrive, and the owner knows the kitchen is not bleeding food cost through guesswork.
In a small kitchen, the system has to be simple for three honest reasons. First, the team is small, often two to four people on a prep shift, and nobody has time to decode a six-page document. Second, space is tight, so the list has to match what physically fits in the walk-in and on the rail. Third, menus change, so the system has to be editable in five minutes, not rebuilt from scratch every season.
Think of the system as four working parts that touch each other: a daily prep sheet, a par level sheet, a weekly rhythm that decides what gets prepped on which day, and a short handoff so the line knows what is ready. Each part is small on its own. Together they replace the most expensive thing in a small kitchen, which is someone making decisions from memory during service.
The rest of this guide walks through each part, with the practical decisions, the common mistakes, and the small mechanics that decide whether the system holds up on a real Friday night.
Why small kitchens fail without a prep system
Most small kitchens do not lack recipes. They lack a reliable answer to three questions that come up every single morning: what do we need, how much of it, and who is doing it. Without a written answer, the prep cook makes a list from memory, the line cook adjusts on the fly, and the owner absorbs the result in food cost and stress.
The failure shows up in consistent ways. Produce is over-cut on slow days and under-cut on busy days. Proteins are portioned at the wrong weight, so the expediter has to re-plate. Sauces run out mid-service because nobody tracked the remaining pints. Sides sit in the walk-in past their usable life and quietly drain margin. None of these are one-time events. They are the predictable cost of running a kitchen from memory.
There is also a quieter cost. A line cook who cannot trust prep is a line cook who slows down to check every container, double-portion to be safe, and throws away food at the end of the night “just in case.” That is not carelessness. That is a reasonable response to a kitchen that has not told them what to expect.
A prep system is not a sign of a fancy operation. It is the bare minimum that lets a small kitchen produce the same plate twice, on a Tuesday and a Saturday, without the result depending on who shows up.
The four parts of a working prep system
The system below is built for kitchens with one prep cook, one to two line cooks, a single walk-in, and a menu that does not change every week. It will not scale to a 200-seat restaurant with a garde manger station. It is meant to fit on a clipboard, a dry-erase board, or a shared phone note.
Part 1: the daily prep sheet
The daily prep sheet is the actual document the prep cook works from. It is short, written the night before or the morning of, and it lists every item that needs to leave the prep table ready for service. Each line on the sheet should carry the same five pieces of information, every time. Consistency is what makes the sheet scannable in a busy kitchen.
- Item name, written the way it appears on the line label, not the recipe title.
- Unit, in the container or portion the line actually pulls: pint, quart, half hotel pan, six-ounce portion, two-ounce ladle.
- Quantity to prep, as a number, not a range.
- Target storage location: walk-in shelf, reach-in drawer, dry shelf, low-boy.
- Time the item should be on the line, written in 24-hour format so there is no confusion at 5 p.m.
Keep the sheet to one page. If it spills onto a second page, the prep cook will work the top of the first page and ignore the rest. A useful target is twelve to twenty lines for a full prep day and six to ten lines for a mid-week touch-up day.
Part 2: the par level sheet
A par level is the amount of each prepped item the kitchen wants to have on hand at the start of service. The daily prep sheet tells the cook what to make. The par level tells them how much is “enough.” Without a par, prep is a feeling. With a par, prep is a number you can audit.
Par levels are not the same as order quantities. A par of eight pints of salsa means the kitchen wants eight pints on the line and in the walk-in before the first ticket. If there are five already, the prep sheet should call for three, not eight. This is the difference between a prep list and a production list, and it is the single most common point of confusion in small kitchens.
Set pars based on actual sales, not wishful thinking. A good starting point is two to three weekends of POS data per menu item, then rounding to a container size that is easy to portion. Pars should be reviewed every four to six weeks, and after any menu change, price change, or shift in covers.
Part 3: the weekly prep rhythm
Small kitchens cannot prep everything every day. A weekly rhythm assigns categories of work to specific days so the prep cook is not trying to do a full reset in a four-hour window before service. The exact days depend on the restaurant’s volume curve, but the structure should always answer one question: what does Monday look like, what does Wednesday look like, and what does Friday look like.
A common rhythm in a small kitchen with a Tuesday to Sunday service pattern looks like this:
- Monday: deep clean, equipment check, sauce and stock production, portioned proteins for the week.
- Tuesday and Thursday: light touch-up prep, fresh produce, à la carte restocks based on par.
- Wednesday: mid-week reset, bread, desserts, and any item with a two-day shelf life.
- Friday morning: full prep for the weekend, with portions sized to forecasted covers.
- Saturday morning: final restock, focused on the items that ran short the night before.
The rhythm should be written down somewhere visible, not held in the head of the owner or the chef. A laminated page on the inside of the prep cooler door is enough.
Part 4: the handoff note
The handoff is a one-paragraph note left for the line cook at the end of prep. It says what is ready, what is short, and what needs to be built to order. It is not a recap of the prep sheet. It is the small amount of context the line cook needs to set up the pass without walking into the walk-in to investigate.
A handoff note can be as short as four lines. “Salsa: 8 pints, on the left shelf. Chimichurri: 3 pints, short by 2, made-to-order for the next 90 minutes. Proteins: portioned through Saturday dinner. Lemon wedges: prepped for tonight only, redo in the morning.” That note is worth more than the prep sheet it came from, because it tells the line exactly what to expect.
How to build your first prep sheet from scratch
If the kitchen has been running on memory, the first sheet is the hardest one. After that, it is editing. Build the sheet in this order, and resist the urge to start with a template from a software vendor.
- Pull two to four weeks of POS item sales, sorted by menu item, including modifiers that change prep, such as add-on sauces or protein swaps.
- For each item, calculate the average daily count and the highest single-day count, then divide by the number of times the item can be built from a single prepped component.
- Convert the count into containers the line actually uses: pints, quarts, half hotel pans, six-ounce portions, and so on. Round up to a clean container number, then add one extra container as a safety margin.
- Group items by storage location so the prep cook is not walking the kitchen eight times for an eight-line sheet.
- Time each item based on when it has to be ready, working backward from service start, and add a buffer of fifteen minutes for hand-off and label printing.
- Print or write the sheet, run it for one full service day, then adjust based on what was short, what was wasted, and what took longer than expected.
Do not try to make the first sheet perfect. Make it usable. The point of a prep system is to be edited every week until it reflects the real kitchen, not to be admired on a clipboard.
Setting par levels that survive a busy weekend
Pars are where most small kitchens either save real money or quietly lose it. A par that is too low produces stockouts, mid-service panic, and free comps the kitchen cannot bill back. A par that is too high produces waste, expired product, and a walk-in nobody can navigate because there are too many half-full containers.
Use the table below as a starting framework, not a final answer. The exact numbers depend on the menu, the sales mix, and the kitchen’s holding capacity. The columns are the only part that should stay consistent: how you measure, what you assume about sales, and what counts as a safety buffer.
| Item type | How to measure par | Typical weekly review signal | Common mistake |
|---|---|---|---|
| House-made sauces and dressings | Number of full pints or quarts the line needs before service start. | More than 10 percent of prepared volume thrown out at end of week. | Prepping the full recipe every time, regardless of remaining stock. |
| Portioned proteins | Number of portions at the correct weight for the next 24 to 48 hours. | Mid-service re-portioning or portion sizes drifting by 10 percent or more. | Portioning a full case at once without checking the forecast. |
| Cut produce | Pounds or containers of usable, trimmed product on the line. | Trim loss above 20 percent or finished product browning before service. | Cutting all produce the morning of service regardless of shelf life. |
| Garnishes and small items | Count of prepared units (sliced lemons, picked herbs, microgreens). | Last-minute prep during service that delays the first ticket of the night. | Storing garnishes in deep containers where the bottom layer crushes. |
| Bread, tortillas, and starches | Count of finished units, kept at the holding method the menu requires. | End-of-night waste above 5 percent of prepped units. | Batching for the full week when holding quality only lasts two days. |
The weekly review signal column is the part most operators skip. A par level is only as honest as the kitchen’s willingness to look at what was wasted, what ran short, and what sat untouched. Build that habit before adding more items to the sheet.
Daily prep sheet example, built for one cook
The example below is a real-shape sheet for a small bistro running 60 to 90 covers a night with one prep cook starting at 9 a.m. and one line cook arriving at 3 p.m. The numbers are illustrative. The format is the part worth copying.
| Item | Unit | Quantity | Location | Ready by |
|---|---|---|---|---|
| Romesco sauce | Pint | 4 | Walk-in, shelf 2 | 11:00 |
| Chimichurri | Pint | 3 | Walk-in, shelf 2 | 11:00 |
| Pickled onions | Quart | 2 | Walk-in, shelf 1 | 11:30 |
| Chopped romaine (case) | Hotel pan | 2 | Walk-in, shelf 3 | 14:00 |
| Portioned salmon (6 oz) | Each | 36 | Low-boy, left drawer | 15:00 |
| Lemon wedges | Six-count container | 6 | Reach-in, top shelf | 16:30 |
| Herb salad, picked | Half hotel pan | 2 | Walk-in, shelf 4 | 16:30 |
| Dessert: panna cotta | Each | 18 | Walk-in, shelf 1 | 15:00 |
The sheet does the line cook’s thinking for them. They know how many salmon portions are ready, where to find the chimichurri, and when the lemon wedges will be on the reach-in. That is the entire job of a prep sheet in a small kitchen: replace a question with an answer.
The kitchen tools that make the system hold up
A prep system fails less because of the document and more because of the tools around it. Five low-cost items carry most of the weight.
- A whiteboard or dry-erase sheet on the prep cooler door. This is where the daily sheet lives for the prep cook, and where the previous day’s waste notes get written for the next shift to see.
- A small digital scale that reads in grams and ounces. Portioning proteins by eye is how par levels drift. A twenty-dollar scale pays for itself in two weekends of consistent portions.
- A label printer or a stack of masking tape and a sharpie. Every container gets a label with the item name, the date, and the date it should be used by. Unlabeled containers become mystery food, and mystery food becomes waste.
- Clear, stackable containers in three sizes. Standardize on one or two brands and one or two sizes per category. Random tupperware from home is a hidden tax on the prep cook’s time.
- A single shared prep sheet location. Whether it is a clipboard, a tablet in a stand, or a printed sheet taped to the wall, the system needs one canonical place. A second copy that drifts out of sync is worse than no copy at all.
None of this requires a subscription or a software rollout. The tools are deliberately boring, because a prep system for a small kitchen has to survive a cook who is in a hurry.
Common mistakes that quietly break a prep system
Most prep systems do not fail on day one. They fail in the third or fourth week, when the kitchen gets busy, the prep cook changes, or a menu item is added without updating the sheet. These are the failure patterns to watch for.
- Prepping from memory, “just this once.” Once turns into every shift, and the system stops being a system. Keep the sheet visible and treat the prep cook’s job as working the sheet, not improvising.
- Letting pars drift upward after a busy weekend. A busy weekend does not mean every weekend is busy. If pars were raised and waste spiked the following week, pars were raised too far.
- Adding menu items without updating the prep sheet. Every new item needs a par, a unit, a location, and a ready-by time. Skipping any of those four turns the new item into a line-cook problem at 7 p.m.
- Storing prep sheets digitally only. If the prep cook has to log in to a tablet, the sheet is invisible. A printed sheet, a clipboard, or a whiteboard is faster and survives a Wi-Fi outage.
- Skipping the handoff note. The handoff is what closes the loop between prep and service. Without it, the line cook walks in cold and rebuilds mental lists the kitchen was trying to eliminate.
- Letting the system live in the owner’s head. A system the owner can run while absent is a system that survives a sick day, a vacation, or a hiring change. A system that depends on one person is not yet a system.
None of these are dramatic. They are the slow leaks that turn a working prep list into a binder nobody opens.
How the prep system connects to the rest of the operation
A prep list system does not live alone. It is most useful when it talks to the rest of the operation in small, predictable ways. Two connections matter more than the rest.
The first is the menu. A menu item that is hard to prep should be flagged on the prep sheet with a longer ready-by time, or it should be reconsidered on the menu. A good rule in a small kitchen is that every menu item must be producible from a prepped component in under four minutes during service. Items that take longer either need a dedicated prep cook during service or a menu revision.
The second is ordering. A prep list tells the kitchen how much finished product it needs. The order sheet should be informed by what the prep list consumes. If the prep list calls for eight pints of salsa, the order sheet should account for the tomatoes, onions, peppers, and herbs it takes to produce eight pints, plus a buffer. When these two documents drift apart, food cost is the first place the kitchen feels it.
If the kitchen is also working on menu pricing, branding, or marketing, the prep system is what keeps those choices honest. A menu that is well priced but impossible to prep is a menu that will be cut mid-service. A brand that promises a hand-made experience is undermined by a freezer full of pre-portioned mystery items. The prep system is the operational floor that every other decision rests on.
How long it takes for the system to start paying off
A realistic timeline helps. A small kitchen that has never had a written prep system should expect a messy first week, a workable second week, and a steady third week. The first real payoff shows up in week two or three, when the line cook stops asking “what do we have” and the prep cook stops guessing what to cut.
The financial payoff is harder to see on a single P&L, but it shows up in three places that add up. First, food waste drops because pars are based on real demand. Second, labor efficiency improves because the prep cook is not walking in circles looking for instructions. Third, the kitchen loses fewer sales to 86’d items, because the system is built around what the line actually needs at the start of service.
There is also a less measurable payoff. A kitchen that runs on a system rather than on a personality is a kitchen that can hire and train faster. New cooks can read the sheet, find the labels, and follow the rhythm. The owner can step off the line for a meeting, a doctor’s appointment, or a day off without the kitchen falling apart. That is the real test of whether the system is working.
Adapting the system as the kitchen grows
A prep system for two cooks and 60 covers a night is not the same system that will work at four cooks and 120 covers. The principles stay the same, but the scale changes three things.
First, the daily sheet gets longer and starts to need categories: sauces, proteins, sides, garnishes. The prep cook works the sheet in order, and the line cook scans by category. Second, the par level sheet graduates from a clipboard to a shared spreadsheet or a lightweight tool, because the math of thirty or forty items by hand is error-prone. Third, the weekly rhythm gets two prep cooks or a prep cook and a sous chef, which means the system needs a clear primary owner so nothing falls between two people’s responsibilities.
The temptation at this stage is to reach for a full restaurant management platform. That is reasonable, but only after the kitchen has run a working manual system for at least a month. Software amplifies an existing system. It does not invent one. A kitchen that has never written a daily sheet by hand will not get value from a tool that promises to write it for them, because nobody on the team will know what the tool is supposed to produce.
For a kitchen that is in this growth window, the best next step is to formalize the par level sheet into a small spreadsheet with one row per prepped item and a column for each day of the week, then let the spreadsheet generate the daily prep sheets. The cost is an afternoon of setup. The benefit is a system that is editable in minutes rather than rewritten from scratch.
A short checklist for the first thirty days
Use the list below to keep the rollout honest. It is the order a working prep system usually comes together in, and skipping steps is the fastest way to make the system look finished when it is actually only half-built.
- Day 1 to 3: build the first daily prep sheet by hand, from POS data, and run it.
- Day 4 to 7: write down par levels for every prepped item, based on what the line actually used.
- Day 8 to 14: add the weekly rhythm to a laminated page and tape it inside the prep cooler door.
- Day 15 to 21: introduce the handoff note, written by the prep cook at the end of each shift.
- Day 22 to 30: review waste, stockouts, and re-portioning, then adjust pars and the daily sheet once.
- Day 31 onward: schedule a fifteen-minute weekly review, same day, same time, until the system stabilizes.
If the kitchen hits day thirty and the sheet still feels like a chore, the sheet is probably too long or too detailed. Cut it down to the items that actually drive the line, and let the rest stay in the recipe binder.
Frequently asked questions
What is the simplest prep system a small kitchen can start with this week?
One printed daily prep sheet, written the night before, listing each prepped item by name, unit, quantity, storage location, and ready-by time. Pair it with a short par level list for the ten to fifteen items the line pulls most. That is enough to replace memory, and it fits on a clipboard.
How do I set par levels if I have no historical sales data?
Estimate from the menu. For each item, multiply the number of covers you expect on your busiest day by the average number of times the item is sold per cover, then round up to a clean container count and add one safety container. Refine the numbers after the first two weeks of real service.
How often should the prep sheet be updated?
Rewrite it daily for the next day’s prep, and review the par levels behind the sheet every four to six weeks. The daily edit is a five-minute job once the par levels are set. The par review is a fifteen-minute meeting that prevents the sheet from drifting out of touch with real demand.
What is the difference between a prep list and a production list?
A prep list tells the cook what to make today, in the exact quantity that brings stock up to par. A production list tells the cook how to make it, in batch sizes based on recipe yield. The prep list drives the day’s work. The production list is the recipe behind each line on the prep list.
How do I keep the prep system going when the prep cook changes?
Keep the documents physical, in the same place, every day. A printed sheet on a clipboard, a par list taped inside the cooler, and a weekly rhythm page on the wall survive a staffing change better than a digital workflow that lives on a specific login. Train the new cook to update the same documents, not to rebuild their own.
Should a small kitchen use prep software or stay on paper?
Start on paper or a whiteboard. Software is useful once the kitchen has a stable menu, a stable par list, and a stable rhythm, because software amplifies a system that already exists. If the system is still being built, paper is faster, cheaper, and harder to ignore.
How do I prevent the prep cook from over-prepping “just in case”?
Make the par level visible on the sheet. If the line already has four pints and the par is six, the sheet calls for two, not six. Over-prepping becomes harder to justify when the number is written down and the waste is reviewed at the end of the week.
What is the most common reason a prep system fails in the first month?
The owner or chef keeps adjusting the sheet on the fly and the prep cook stops trusting it. The fix is to lock the sheet at the start of prep, treat changes as the next day’s edits, and protect the prep cook from mid-prep revisions that turn the sheet into a suggestion rather than a plan.
How does a prep system affect food cost?
The direct effect is on waste, which usually drops once par levels are written down and reviewed weekly. The indirect effect is on portion consistency, which improves when proteins and sauces are portioned against a number instead of a feeling. Together, those two changes are where most small kitchens find the food cost improvement a prep system actually delivers.
What should be on the handoff note and what should be left out?
The handoff note should say what is ready, what is short, and what is built to order, with locations and counts. It should leave out the recipe instructions, the reasoning behind the prep, and any item the line already knows. The handoff is a status report, not a teaching document.