Before writing a weekly menu, put seven lines on a piece of paper. Mark the nights when cooking time is short and the days when lunch must leave the house. A plan that ignores those two things usually leaves good ingredients unused. If the week has more constraints than this budget example covers, adapt the meal plan to your schedule before pricing the basket.

Build the week from the kitchen you have

Open the fridge, freezer and cupboard. Note cooked food that needs eating soon, then the raw ingredients you already own. If there is cooked rice, a little cabbage and a can of beans, Monday could be bowls. If there is no rice, the list needs rice; it does not need a new set of ingredients for a completely unrelated recipe. USDA MyPlate recommends this inventory before planning meals.

Choose two dinners that can share a purchase without feeling like duplicates. For example, cook a pot of lentils: serve some with tomato and pasta on Tuesday, then use the rest in a soup with carrots on Thursday. Keep the lentils plain until you split them, so the second dish can take a different seasoning.

Look at package amounts while you plan. If a recipe uses half a bag of carrots, write where the rest will go before adding it to the cart. The same applies to fresh herbs, greens and a large tub of yogurt. A low unit price is not a saving if you regularly discard the remainder. Frozen or shelf-stable versions can be useful when the schedule is uncertain, even if the price per serving needs a closer comparison.

Check the number of mouths at each meal. Two adults may both be home for dinner but only one needs a packed lunch the next day. Write those facts on the page rather than multiplying every recipe by the same number. If a guest is likely or a child eats at school on some days, mark that as well. A menu can be rough, but the shopping quantity should reflect the actual week.

Fill the calendar with real constraints

Put the longer meal on the night with the most time. Give the busiest night a pantry dinner such as eggs on toast with frozen vegetables, or pasta with canned tomatoes and beans. Write a leftover lunch next to the dinner that will produce it. Do not count on leftovers from a recipe that only makes two servings for two people.

A workable example for two adults might read: Monday rice and bean bowls; Tuesday lentil pasta with extra lentils set aside; Wednesday eggs, toast and vegetables; Thursday lentil soup; Friday a meal from remaining ingredients. Breakfast can repeat oats or yogurt on several days. This is a planning example, not a price or nutrition guarantee; scale it to your household and appetite.

Now test that example against the clock. If Tuesday is your late shift, cooking lentils from dry that evening may be a poor fit. Cook them on Monday if you can store them safely, use canned lentils, or move the soup to the day with more time. Mark what needs thawing in the refrigerator ahead of a planned meal. A tiny note such as "move beans to fridge Wednesday" can prevent Thursday's dinner from becoming takeout.

Leave at least one flexible square. A strict seven-night schedule has no room for an invitation, a sick day or a meal that makes more than expected. The flexible night can use the backup meal or leftovers that are still within their safe storage window. If everything goes as planned, you can use it to clear ingredients before the next shop.

Shop for the gaps, then revise

Write quantities beside the missing items. "Two onions" makes a better shopping instruction than "vegetables." Mark a substitute where prices may vary: "cabbage or frozen greens" gives you room to choose. Keep one shelf-stable backup meal so a changed schedule does not force another store trip.

On the next planning day, check what survived the week. If Thursday's soup never happened, use or safely store those ingredients before buying more. Cooked leftovers belong in the fridge promptly and are generally for use within three to four days under USDA guidance. The useful menu is the one you can adjust, not the one with every square filled.

Before checkout, compare the full basket with the amount you can spend, including breakfast, snacks and household staples that this dinner list may have missed. If it is over budget, change a planned purchase rather than hoping the total will shrink at the register. When package sizes differ, compare cost per usable portion, not only the shelf price. Swap a costly vegetable for one you already have, reduce a recipe that makes too many servings, or choose a less expensive protein that still works in the dish. Keep the quantities visible so the revised list still feeds the household.

At the end of the week, note only what helps the next plan: what ran out early, what spoiled and which dinner required more time than expected. You do not need to track every bite. A few repeated observations can tell you whether the problem is overbuying, an unrealistic Tuesday meal or simply a recipe nobody enjoyed. Next week's page should reflect that evidence.