Guides
Meal production plan template
A production plan is four connected documents pretending to be one: what to cook, what to buy, what goes in each box, and what went wrong. This template keeps them on one sheet so they cannot disagree.
What is in the template
A CSV, so it opens in Excel, Google Sheets or Numbers without conversion. Two example rows are included and should be deleted once you understand the shape.
Free download
- Cook list — recipe, selections, portion size, cook quantity, allergens, and a conflicts column that must read zero before cooking starts
- Ingredient requirement — required quantity, on hand, to purchase, supplier and lead time
- Packing and labels — customer, recipe, allergens, use-by date, and printed/packed checkboxes
- Exceptions log — what went wrong, the decision taken, who took it and when
- In-sheet notes explaining the two calculations, so the arithmetic is not a mystery formula
Why these four sections belong together
Most kitchens keep the cook list and the purchasing list in separate places, and they diverge on the first mid-week change. Selections drop, the cook list is updated, the purchasing sheet is not, and the ingredients arrive for meals nobody ordered.
Keeping them adjacent does not make them derive from one another — a spreadsheet cannot do that — but it makes the divergence visible. If your cook list says twenty-four portions and your ingredient line still says the quantity for thirty, you can see it.
The exceptions log is the section people skip and later wish they had. When a customer disputes a charge six weeks later, the only thing that settles it is a note written on the day by the person who made the decision.
Using it through the week
After the cut-off, fill the selections column
Not before. Anything entered while customers can still change their meals is a draft, and treating a draft as a plan is how purchasing goes wrong.
Resolve conflicts to zero
The conflicts column exists so there is a single number to check before cooking starts. Any figure above zero is a portion that should not be produced yet.
Work out to-purchase before ordering
Required minus on hand. If the result is negative you are over-stocked, which is information rather than permission to skip the check.
Fill packing as boxes are made
Not afterwards from memory. The use-by column should be derived from the production date and shelf life, not guessed.
Log every exception the same day
A substitution, a shortfall, a failed delivery. Same day or not at all — nobody reconstructs these accurately on Friday.
Where a spreadsheet stops being enough
This template is genuinely useful and it has a ceiling, so it is worth being straight about where that is. A sheet cannot guarantee that changing one fact updates every other place that depends on it. Every propagation here is done by a person who has to remember.
That works while one person holds the week in their head. It stops working somewhere between two and four hundred meals a week — earlier if your customers pause and swap often — and the failure is quiet: a production number that no longer matches what customers ordered, discovered on a Tuesday.
Mealroh derives the cook list, the ingredient requirement, the labels and the delivery manifest from one set of customer selections, so those four views cannot disagree. That is the difference between a good sheet and a system, and it is the only reason to move off one.
Common questions
- What format is the template?
- A CSV, so it opens directly in Excel, Google Sheets or Numbers with no conversion step and no macros. Two example rows are included to show the shape and should be deleted before use.
- When should the selections column be filled in?
- After the cut-off, never before. Anything entered while customers can still change their meals is a draft, and purchasing built on a draft is how ingredients arrive for meals nobody ordered.
- Why is there an exceptions log?
- Because six weeks later a customer will dispute something and the only thing that settles it is a note written on the day by the person who made the decision. Nobody reconstructs these accurately afterwards.
- At what point does this template stop working?
- When one person can no longer hold the week in their head — commonly two to four hundred meals a week, earlier if customers change plans often. A sheet cannot propagate a change automatically; that is its structural limit.
When the sheet stops keeping up
Mealroh derives the cook list, ingredient requirement, labels and delivery manifest from one set of customer selections, so the four cannot drift apart. The product pages show it against a demonstration kitchen.
Related reading
- GuidesProduction planning for a meal-plan kitchenProduction planning here is unusually tractable, because unlike a restaurant you know your entire day before it starts. The difficulty is not forecasting — it is keeping the plan in step with a customer base that keeps changing its mind.
- GuidesIngredient forecasting for meal-prep kitchensPurchasing is where a meal-plan kitchen’s margin is actually decided, and it is downstream of information the business already has. Most over-buying is not a forecasting failure but a plumbing failure.
- SolutionsMeal production planning and ingredient forecastingProduction planning is the join between what customers chose and what the business has to buy. When those two are maintained separately, food cost drifts and nobody can say exactly why.
- GuidesMoving a meal-plan business off spreadsheetsSpreadsheets are not a mistake. They are the correct tool for an operation still working out what it is, and they fail for a specific, identifiable reason rather than because they are unprofessional.
- GuidesWhen a supplier arrives short on a production morningUnlike a restaurant, a meal-plan kitchen cannot quietly eighty-six a dish. Every portion is owed to a named person who chose it, which makes a shortage a customer-facing decision rather than a menu adjustment.