
Original kitchen worksheet · SHUPA DIET — four dinners, a shared ingredient map, and a small decision test. All amounts below are illustrative planning assumptions, not shopping prices or a tested meal plan.
Meal planning gets tedious when every dinner requires an entirely different basket. At the other extreme, making one enormous batch can leave the week repetitive. This worksheet shows a middle path: reuse a few ingredients without repeating the same finished meal. It is about shopping decisions and kitchen logistics, not weight-loss promises.

Illustrative kitchen photograph: Clay Banks / Unsplash. Menu quantities below are a transparent hypothetical demonstration.
1. Choose functions, not just ingredients
Write down one anchor grain or starch, one vegetable group, one flexible protein source, and two flavour routes. The point is that an ingredient can play different roles: a pepper can be chopped into rice, roasted as a side, or stuffed as the centre of a dish. Similar shopping inputs should not force identical dinners.
| Ingredient role | Example basket | Ways to use it |
|---|---|---|
| Anchor starch | Dry rice | Rice bowl, skillet, stuffed pepper filling |
| Vegetable group | Four peppers + frozen greens | Chopped, roasted, folded into filling |
| Flexible protein | Two cans of chickpeas + eggs | Chickpea tomato bowl, egg and greens skillet |
| Flavour route A | Tomato sauce and herbs | Saucy bowl or filling |
| Flavour route B | Lemon, garlic and spices | Fresh-tasting skillet or salad-style bowl |
2. A four-dinner map for two people
This is an idea map, not a nutritional prescription. Decide serving size and ingredients based on household needs, product labels, allergies and food availability. The methods below use the same basket without pretending that all dishes taste alike.
| Evening | Dinner idea | Shared components | Change the experience |
|---|---|---|---|
| Monday | Tomato-chickpea rice bowls | Rice, chickpeas, tomato, greens | Saucy base and herbs |
| Tuesday | Pepper and egg skillet with rice | Peppers, rice, greens, eggs | Pan finish rather than tomato |
| Wednesday | Stuffed pepper halves | Peppers, chickpeas, rice, tomato | Oven-baked presentation |
| Thursday | Lemon-chickpea and greens plates | Chickpeas, greens, rice, lemon | Different seasoning and texture |
3. The overlap inventory is the real planning tool
Use grams or packages consistently. In this example, the household plans to use 480 g of dry rice out of a 500 g purchase, leaving 20 g before considering kitchen losses or other meals. That is 480 ÷ 500 × 100 = 96% planned use. It says nothing about nutrition or whether the pack should be finished in four days.
| Bought | Planned use | Remaining on paper | Decision |
|---|---|---|---|
| Dry rice: 500 g | 480 g | 20 g | Keep in pantry for later |
| Bell peppers: 4 | 4 | 0 | No extra planned |
| Frozen greens: 600 g | 4 × 150 g | 0 | Use portions as needed |
| Chickpeas: 2 cans | Four half-can uses | 0 | Check the drained weight on your actual cans |
When using canned ingredients, a ‘half-can’ is a planning unit, not a universal weight. Check each package’s drained quantity. Allergen-sensitive households should also check labels on sauces and seasonings.
4. What if one ingredient changes in price?
Do not copy a price from an old article. Enter your own shelf price and size. Cost per usable unit = shelf price ÷ usable grams. If a 400 g ingredient costs 4.00 in your local currency, its planning cost is 0.01 per gram. A 120 g use costs 1.20. These are invented demonstration figures; currency and real market prices vary.
To compare alternatives fairly, write the new recipe’s role. A replacement for a thick sauce needs similar texture; a replacement for a crunchy vegetable needs a different preparation strategy. Price per package alone is not a fair comparison if only part of the package will be used.
5. Time is a separate budget
| Task | Potential bottleneck | Adjustment |
|---|---|---|
| Wash and prepare vegetables | Repeated washing | Plan one dedicated preparation window |
| Cook the grain | Shared pot or cooker | Schedule it around the meal that needs it |
| Create distinct flavours | All meals taste the same | Split the seasonings just before finishing |
| Clean-up | Too many pans on Tuesday | Choose a simpler skillet or bowl |
| Leftovers | Portions exceed real appetite | Reduce shopping quantities next week |
Plan shopping and preparation separately from food storage. Cooked and perishable foods require appropriate temperature control, hygiene, and storage rules; do not assume one large batch stays safe for the entire week. Follow package instructions and reliable food-safety guidance such as FoodSafety.gov’s four basic food-safety steps.
6. Run a real four-night review
Record just four values after each dinner: what was actually cooked, ingredients left, time spent on active work, and whether you would make it again. The example menu above is a proposal; only a real household record can establish if it helped.
| Day | What did we actually eat? | What ran out / remained? | Make again? |
|---|---|---|---|
| 1 | ________ | ________ | Yes / No / Adjust |
| 2 | ________ | ________ | Yes / No / Adjust |
| 3 | ________ | ________ | Yes / No / Adjust |
| 4 | ________ | ________ | Yes / No / Adjust |
7. Make the second week easier than the first
Keep the two dishes that required the least fuss and were genuinely enjoyed. Replace a low-value recipe, not the whole basket. If a pack repeatedly remains unused, buy a smaller amount even if the shelf unit price is higher. This is where real household evidence is more useful than a generic ‘perfect meal plan’.
For package price arithmetic, use our unit-price comparison calculator. For planning portions, see the recipe cost per serving calculator. The purpose of this worksheet is ingredient overlap and workflow design, not medical or weight-loss advice.
Editorial method: The four dinners and example quantities are original illustrative planning scenarios, not a measured study. Adjust all food choices for dietary requirements, allergies and household circumstances; questions are welcome via contact.