Guides
A daily operations checklist for a meal-plan kitchen
Most operational checklists are organised by department, which is convenient and wrong. Ordering them by when a problem is still cheap to fix is what makes a checklist worth running.
The day, in the order things become expensive
Before the cut-off closes
Which slots are still empty, and which customers have not selected. This is the last moment a gap costs nothing.
On freezing the day
Confirm counts against expectations. A total that looks unlike last week usually means a plan change landed oddly, not that demand moved.
Before cooking starts
Allergen conflicts resolved. After this point the portion physically exists and the fix is waste.
Before packing
Labels printed in load order, conflicts still visible above the run.
Before the van leaves
Box counts against the manifest, and any address flagged as problematic yesterday.
End of round
Every stop closed as delivered or failed. An open stop becomes an argument next week.
End of day
Failed deliveries actioned, and terms expiring in the next fortnight reviewed.
Why the ordering matters
Every item above is cheap at its point in the day and expensive an hour later. An empty slot before the cut-off is a click; the same gap after freezing is either a default meal nobody chose or a missing box.
A checklist arranged by department invites you to run the kitchen items together and the delivery items together, which means half of them are performed after the moment they were useful.
What to automate off this list
Several of these should stop being checks at all. Empty-slot chasing becomes a customer notification; allergen conflicts become a flag rather than an inspection; expiring terms become a standing view rather than a review.
A good checklist shrinks over time. If yours has not, the system underneath it is not absorbing anything.
Common questions
- Why order a checklist by time rather than department?
- Because each item is cheap at its own point in the day and expensive later. Grouping by department means half of them get performed after the moment they could have prevented anything.
- Which item is most often skipped?
- Closing out stops at the end of the round. It feels like paperwork on a finished day, and it is the evidence that settles next week’s billing dispute.
- Should a checklist stay the same size?
- No. Items should migrate off it into automation — empty-slot chasing becomes a notification, allergen checks become a flag. A checklist that never shrinks means nothing is being absorbed.
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
- SolutionsMeal delivery management software for the daily operating rhythmEvery meal-plan business runs the same loop every single day — cook, pack, drive, confirm. Management software earns its place by making the current position of that loop visible without anyone compiling it.
- GuidesThe packing workflow, and where it goes wrongPacking is the join between two opposite shapes of the same day: the kitchen cooked totals, and the customer receives one specific box. Nearly every visible error in a meal business is made at that join.
- GuidesThe driver handover checklistAlmost every delivery failure in a meal-plan business is an information failure rather than a driving one, and nearly all of them are created in the ten minutes before the van leaves.
- 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 packing software for prep kitchensThe packing bench is the narrowest point in a meal-plan operation. Everything upstream converges here as totals, and everything downstream leaves as named boxes — and almost every error a customer ever notices is created in that conversion.
- GuidesHiring the first operations person in a meal businessThe first operations hire is where most meal-plan founders discover how much of the business was never written down — usually in the third week, when something goes wrong in a way it never did before.