A production sheet is one page that tells a kitchen what to make for a meal, and how much, and then records what actually happened. Before the shift it lists each menu item with its portion size, the number of portions forecast, what's already on hand, and so how many to prepare and how many batches of the recipe that takes. After service it gets the rest: how much was prepared, how much was served, what was left over, and the temperatures measured. The first half is a plan and the second half is a record, and next week's plan is written from this week's record. Cafeterias, hospitals, caterers and schools use them every day. Below is a filled-in sheet for a made-up cafeteria's lunch, the sums, and a file.
The short version
- One row for each menu item, one sheet for each meal.
- To prepare = forecast − on hand.
- Batches = to prepare ÷ what one batch of the recipe makes, rounded up.
- Left over = on hand + prepared − served.
- Next week's forecast starts from this week's served column.
- Schools in the lunch program must keep production records.
- TaroStack says how many batches the stock on hand allows. More below.
A filled-in sheet
A made-up cafeteria, Wednesday lunch, about 300 people.
| Menu item | Portion | Forecast | On hand | To prepare | One batch makes | Batches |
|---|---|---|---|---|---|---|
| Teriyaki chicken | 4 oz | 140 | 0 | 140 | 48 | 3 |
| Vegetable stir fry | 6 oz | 60 | 0 | 60 | 24 | 3 |
| Steamed rice | 1 cup | 200 | 0 | 200 | 50 | 4 |
| Garden salad | 1 bowl | 90 | 12 | 78 | 20 | 4 |
| Chocolate chip cookie | 1 cookie | 160 | 36 | 124 | 48 | 3 |
That's the plan, written the day before. This is the record, filled in after service.
| Menu item | Prepared | Served | Left over | Cooked to | Notes |
|---|---|---|---|---|---|
| Teriyaki chicken | 144 | 131 | 13 | 172°F | |
| Vegetable stir fry | 72 | 64 | 8 | 168°F | |
| Steamed rice | 200 | 188 | 12 | 180°F | |
| Garden salad | 80 | 85 | 7 | Tuesday's 12 bowls served first | |
| Chocolate chip cookie | 144 | 150 | 30 | Ran low at 12:40 |
The calculations
To prepare. Forecast minus what's on hand. Ninety salads forecast, twelve in the cooler from Tuesday: 78 to make. What's on hand gets served first.
Batches. A standardized recipe makes a known number of portions. The chicken recipe makes 48. A hundred and forty portions ÷ 48 is 2.9, so three batches, which is 144. You can't cook nine-tenths of a batch of most things, so the sheet rounds up, and the four extra portions are known before anyone turns on the oven.
Left over. On hand plus prepared, minus served. Salad: 12 + 80 − 85 = 7.
The forecast. This is the number that matters, and it comes from old sheets. Look at the last three or four Wednesdays this menu ran. If chicken was served 131, 128 and 135 times, 140 is about right, and three batches cover it. If the cookie count shows 150 served and a note says they ran low before one o'clock, the real demand was higher than 150: forecast 180. A sheet with no notes column loses that.
Portion size is part of the sum. A 4 oz portion served as 5 oz turns 144 portions into 115. If an item runs out early with nothing left over, check the scoop before raising the forecast.
Scaling the recipe to the batches is in recipe multiplier, and writing a recipe that makes the same number of portions every time in standardized recipe template.
What else goes on the sheet
| Column | Why |
|---|---|
| Recipe name or number | So "chicken" means one recipe, with one yield |
| Who made it | Questions go to a person |
| Time it came off the heat, and its temperature | The record that it was cooked |
| Temperature on the line | Hot food is held at 135°F or above |
| What happened to the leftovers | Chilled for tomorrow, or thrown out, and how much |
The temperatures here are what this kitchen measured. Under the FDA Food Code poultry is cooked to 165°F, and hot food is held at 135°F or above. Your own limits come from your food safety plan and your inspector.
Schools. A school in the National School Lunch Program has to keep one. 7 CFR 210.10(a)(3) says schools "must keep production and menu records for the meals they produce", showing how the meals offered contribute to the required meal components and food quantities for each age and grade group every day. Your state agency has the form it wants. The food safety side is in HACCP plan for a school kitchen.
A production sheet covers a meal. The list of chopping and thawing that gets a kitchen ready for it is a prep list, and a bakery's version is a bread production sheet. This is general information, not legal advice.
Get the sheet
Download the production sheet. One sheet and a read-me: type the forecast and what's on hand, and it works out what to prepare and the batches; after service, type what was prepared and served, and it works out what's left. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
The sheet says three batches of chicken. It doesn't say whether there are 36 pounds of chicken thighs in the walk-in to make them. That's a second sum, for every ingredient of every item, done from memory at two in the afternoon the day before. And last Wednesday's sheet is in a binder, so the forecast gets copied from last week, leftovers and all.
How TaroStack does it
TaroStack ties the batches to the stock.
Each menu item is a recipe by weight, with what one batch makes. Units convert, so chicken bought by the case and used by the pound is one item.
"What could I make right now" says how many batches the stock on hand allows, and which ingredient runs out first.
Record the batch and its ingredients come off stock. Your own checks, such as the temperature it was cooked to, are fields on the batch record. The batch notes which lots it used, automatically.
What was thrown out is an adjustment with its reason, so leftovers show by item.
A reorder list in days of cover says what to buy before next Wednesday.
| The job | Paper sheet | In TaroStack |
|---|---|---|
| Is there chicken for three batches? | Look in the walk-in | What could I make right now |
| Take ingredients off stock | A separate count | Recorded with the batch |
| The cooked-to temperature | A column | A field on the batch record |
| What was wasted last month | Add up the sheets | Adjustments by reason |
TaroStack doesn't forecast how many people will come to lunch or take a temperature. Recipes and batches are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
