Guides
Production planning for a meal-plan kitchen
Production 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.
Derive the counts, never type them
The production sheet should be a view of customer selections, not a document someone maintains. The moment it is typed, it becomes a second source of truth that has to be reconciled with the first — and reconciliation is exactly the work you were trying to eliminate.
The test is simple: when a customer changes a meal, does the production number change by itself? If someone has to remember to update it, the sheet will be wrong on the day it matters most.
Two views of the same day
The kitchen and the packing bench need opposite shapes of the same data.
Aggregate, for cooking
Total portions per recipe, summed across every customer, so the line has one number to work to.
Individual, for packing
Which portion belongs to which named customer, with their allergens attached, so the right box reaches the right person.
Exceptions, for both
Allergen conflicts and unusual requirements surfaced before service rather than discovered mid-shift.
Plan to the cut-off, not to the week
Planning production for days whose selections are still open produces confident numbers that are wrong. The useful planning horizon ends at the cut-off; beyond it you are estimating, and estimates should be labelled as such.
This is why cut-off and production planning are really one topic. Move the cut-off and you move the horizon over which your plan is trustworthy.
Common questions
- How far ahead should production be planned?
- Firmly, only as far as the cut-off — beyond that, customer selections can still change. Anything further out should be treated as an estimate for purchasing purposes rather than a plan the kitchen works to.
- Should the kitchen see customer names?
- For cooking, no: aggregate counts are the right view and names are noise. For packing and allergen checks, yes, because those tasks are about a specific portion belonging to a specific person.
- What causes a production sheet to drift from reality?
- Almost always a mid-week change that was applied in one place and not another. If the sheet is derived from selections rather than maintained by hand, that class of drift cannot happen.
See how this works in practice
The home page walks through the same mechanics against a real admin loaded with a demonstration kitchen: production, packing, routes and the customer side.
Related reading
- 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.
- GuidesSetting a meal delivery cut-off that actually holdsThe cut-off is the single most consequential number in a meal-plan operation. It is the line between a change that costs nothing and a change that costs food.
- 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.
- GuidesAllergen management in a meal-prep kitchenAllergen handling is the one part of a meal-plan operation where a data-entry problem becomes a medical one. It deserves a different standard of care from the rest of the customer record.
- GuidesMeal production plan templateA 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.