The cook sheet writes itself the night before

Ask a tiffin owner what time their day starts and the honest answer is usually the night before, lying awake doing arithmetic. How many veg. How many non-veg. Did the Sharmas pause. Did anyone message after nine.

The cook sheet is the answer to that, and the reason it works is not the printing. It is the cutoff.

The cutoff is the whole idea

You set a time each day at which the next day's orders close. At that moment the day locks: every pause, skip, plan switch and add-on that arrived before it is already counted, and nothing after it can silently change the number you are about to cook against.

This is what a spreadsheet cannot give you. Not because a spreadsheet cannot hold numbers, but because it has no moment where the counting stops. A message at 11pm quietly invalidates the count you made at 9pm, and you find out at 6am.

What prints

Portions per dish

Not just "84 meals" but what that means in the kitchen: how much of each dish, in the measure you actually cook in. Rotis are counted; dal is weighed. Menu items carry their own measures, so the sheet speaks in units your hands understand rather than in servings you then have to convert.

Containers and packaging

How many containers, lids and bags today needs. Packaging is the cost most kitchens forget to track and the supply most kitchens run out of on a Thursday.

The packing list, per customer

The second half of the sheet is the packing bench: every customer, what goes in their box, their add-ons for that day, any per-day quantity change, and their notes — less spicy, no onion, extra rotis on Thursdays.

Those notes are the thing that makes a tiffin customer stay for two years, and they are exactly what gets lost when a new person is packing.

Labels

Packing labels print in one click, so the box that leaves the bench is already addressed to the right family and the driver is not matching names to lids in a car.

The menu behind it

The cook sheet is generated from a weekly menu attached to each plan. A veg plan and a non-veg plan run their own rotations, so you are not maintaining two systems or mentally filtering one list.

Menus are published by week, which means next week can be drafted and adjusted without touching what is currently being cooked against. Individual days can carry quantity overrides — three rotis instead of four on a heavy day — without redefining the item.

What it changes

The measurable effect is on food cost. Cooking to a guessed count means over-cooking, because nobody wants to come up short — and consistent over-cooking is how a food-cost percentage drifts from 30% to 40% without a single price changing.

The menu performance report closes that loop, showing which dishes actually sold and what each plan returned, so next week's rotation is chosen from evidence.

Open the live demo to see a real cook sheet with sample data, or read the nine numbers every tiffin kitchen should track for where food cost fits in.