A weekly tiffin menu plan for lunch and dinner

Start with a framework your kitchen can repeat

A useful weekly tiffin menu plan balances variety with a preparation routine you can repeat. Start by defining the parts of your standard meal: a dal or pulse dish, a sabzi, roti or rice, and the accompaniments you actually offer. A different combination each day can give customers variety without requiring an entirely different kitchen process.

The vegetarian example below is a planning template, not a menu currently sold by OrderTiffin. Adapt it to your customers, ingredient availability, equipment and serving sizes. Your kitchen should publish only the dishes and service days you are ready to provide.

A seven-day vegetarian lunch and dinner example

Add salad, pickle, curd or other accompaniments only where they are included in your offer and suitable for your packing and delivery process. The four-roti serving is an example, not a universal portion. If your customers prefer fewer rotis or more rice, define that clearly and cost the actual combination.

A kitchen closed on Sunday should remove those meals or mark the day closed. Do not add a seventh service day just to match the table. If lunch is your only service, a reliable seven-day lunch plan is more useful than a dinner menu that customers cannot order.

Write a portion standard beside the menu

Customers need to know what the meal includes, and the packing team needs to know what goes in the box. Write down the serving sizes for dal, sabzi and rice, the number and approximate size of rotis, and any accompaniment. Use the same container or ladle as a repeatable reference while packing.

Check that the whole meal fits the intended container without mixing or leaking. Pack a trial box, close it, carry it on the planned route and inspect the result. A dish that looks attractive on a plate may need a different container for delivery. If you change the box size, check the portion standard again instead of assuming the old serving still fits.

Rotate the week without adding needless complexity

Read the menu as a whole week. Look for several similar sabzis in a row, repeated ingredients that customers may notice, and days where every dish needs intensive last-minute attention. Rotate the main dish while preserving some familiar parts of the meal. Consistency is helpful when people rely on the service for an everyday lunch.

Think about the experience of a customer ordering both lunch and dinner. Two different pulse dishes and a change in the sabzi can matter more than giving every combination a new marketing name. Ask which dishes regular customers want repeated and which they would prefer less often. Use that feedback to adjust a future week rather than changing an accepted order without telling people.

Turn the menu into a buying plan

Estimate ingredient quantities from confirmed portions and recipe yield. Keep pantry items separate from ingredients you need to purchase close to preparation. Note what you already have so that a large buying trip does not accidentally duplicate usable stock. Keep a short alternative list for seasonal vegetables that your supplier may not have.

An ingredient can appear in more than one recipe without the meals tasting identical. However, do not build the week around using leftovers in ways that compromise food handling. Follow the applicable food-safety guidance for your kitchen, and use the official FSSAI food-business resources (opens in a new tab) for the requirements that apply to your operation.

• Check opening stock against the confirmed service menu.
• Calculate the quantity needed for your standard portions.
• Confirm supplier availability for the next purchasing window.
• Record approved substitutions before updating the customer-facing menu.

Check the preparation schedule, not just the ingredients

Write the tasks in the order they need to happen: buying, washing, soaking where required, preparation, cooking, packing and dispatch. Identify the equipment and person needed for each task. Several dishes that each seem easy can still compete for the same burner or preparation space immediately before delivery.

Use a trial service to measure the time taken by the whole batch. Include making rotis, labelling boxes and cleaning between tasks. If a menu is consistently late, change the work sequence or simplify the combination before accepting more orders. The home tiffin launch guide includes a practical trial-batch record you can use with this plan.

Define Jain and other custom requests precisely

Different customers can mean different things by a Jain meal or another dietary preference. Describe exactly which ingredients your kitchen can exclude, what notice is required and whether preparation is separate. Ask questions when the request is unclear. Do not use a dietary label as a substitute for a conversation about the food being supplied.

For allergies, do not promise an allergen-free meal solely because you can leave an ingredient out of the recipe. Shared equipment and handling can matter. Explain your actual capability honestly and decline a request you cannot safely fulfil. Custom options should be published only when your kitchen supports them; they are not an automatic feature of every meal.

Have a clear rule for substitutions

An ingredient shortage is easier to manage when there is a stated process. Decide who approves a substitute, how it changes the menu description and when customers need to be contacted. Keep the replacement comparable to the meal people selected, and check any dietary request attached to an accepted order.

Update the current menu before taking further requests. For orders already accepted, notify customers of a meaningful change and agree on the next step rather than silently replacing a promised item. Avoid keeping one menu in a WhatsApp image and another on your website; choose the public kitchen page as the current reference.

Cost the weekly rotation before setting a plan price

Calculate the cost of the actual week rather than choosing a subscription price from your least expensive meal. Paneer, different vegetables, accompaniments and packing needs may change the cost across days. Weight the estimate by the meals and quantities you expect to serve, then check it against the completed week.

Use our tiffin service pricing worksheet to include labour, delivery and overheads. If a special menu costs extra, say so before a customer chooses it. A regular plan should clearly state which service meals are included, which days are closed and whether any optional dish is charged separately.

Publish one current menu customers can understand

A clear public menu needs the weekday, lunch or dinner label, dishes, portion description, price or plan link, delivery window and order cutoff. Show closures and unavailable meals explicitly. Customers should not have to send a message merely to discover whether the kitchen serves dinner on the day they need it.

With OrderTiffin’s menu and ordering tools, a kitchen maintains its weekly menu and meal plans in one dashboard. The selected website design presents the same business data. Explore the sample kitchen to see how customers move from the menu to an order request, and check our WhatsApp order routine for the confirmation step after that.

Prepare a menu handover for the packing team

The public menu and the packing instruction solve different problems. Customers need a readable meal description; a helper needs a precise instruction for the box being assembled. Keep an internal daily note showing each standard component, serving utensil, paid extra and confirmed exception. Check it against the accepted order list before packing begins.

For example, if the public meal includes four rotis and a customer has ordered two additional rotis, make the six-roti requirement explicit on the packing note. Do not assume the helper has read the WhatsApp conversation. Use the same order reference on the packing note and delivery list so that the right box reaches the right customer.

If a dish changes, update both the public version for new requests and the internal instruction for the batch. Record who checked any affected custom meals. A photograph of a finished standard box can help a new helper understand presentation and portions, provided the written measurements are still available.

At the end of the service, compare the instruction with what was actually packed. Repeated confusion about an accompaniment, an extra charge or a container size is a signal to make the instruction clearer. Improving this handover can preserve menu variety while reducing avoidable packing mistakes.

Use a short weekly menu review

• Which dishes were ordered again or specifically requested?
• Did any combination regularly slow down packing or dispatch?
• Were portions consistent across the batch?
• Which ingredients were wasted or unexpectedly unavailable?
• Did the public menu match what customers actually received?
• Are next week’s service days, cutoffs and delivery windows correct?

Keep the review practical. One repeatable improvement is more valuable than replacing the entire menu every week. Save the old version with its dates so you can understand customer feedback and past orders. Publish the next version when buying, preparation capacity and prices agree, then create a kitchen page as the place to check the current week.