Make a weekly meal plan from what you already have
A one-week plan built in a fixed order: the week's schedule, then the food that must be eaten first, then meals from your list, with a planned-leftover meal and a backup meal for the night the plan fails.
- Start here: the essentials
- 1. The order of work, and why this one
- 2. Perishables first: the storage card sets the days
- 3. Meals that carry the week: planned leftovers, eat-down and backup
- 4. A plan that bends: swaps and posting it
- 5. Other ways to plan
- 6. See it: Jordan's first planned week
- 7. Practice: one week on the plan sheet
- 8. Your kitchen
- 9. Check your work
- 10. Knowledge check and scenario
Start here Essentials
At minimum, plan the dinners you will eat at home this week: two or three cooked, one planned leftover and one backup, in the order below. Everything marked Go deeper can wait.
- Copy the week's schedule into the plan. Mark each evening home, out or short on time (the order of work, how many meals).
- List the eat-first items. Take them from the eat-first shelf and the inventory, each with its eat-by day (perishables first).
- Choose meals from your list for the nights you cook, shortest-keeping food first and quick meals on busy nights (busy days).
- Mark one planned-leftover meal inside the leftover's keep time (planned leftovers).
- Write one backup meal from pantry staples (the backup meal).
Minimum time: about 30 to 45 minutes once a week. Done when: the plan sheet has the week's dinners, one planned-leftover meal and one backup.
1. The order of work, and why this one Understand
A weekly meal plan is a written list of the meals a household means to eat at home between one shopping trip and the next, with the day each falls on and the food it uses. It is a draft that puts the food in the kitchen, the food about to be bought and the evenings people are home into one picture before money is spent.
Fill the plan in one fixed order of work, the sequence in which each part of the week gets written down:
| Step | What you write | Where it comes from | Where it goes |
|---|---|---|---|
| 1. The schedule | Each day: who eats at home, and the time available to cook | The week sheet (The people at your table) | Plan: Day, Who, Time available |
| 2. The eat-first items | Food in the kitchen that has to be eaten soon, with an eat-by day | The eat-first shelf (Kitchen inventory) and storage card (How long food keeps) | Eat first |
| 3. The order of the days | Which perishable food is eaten on which day | Keep times on the storage card | Plan: Uses up |
| 4. Meals | A meal from your list for each night you cook | The meal list (Your meal list) | Plan: Meal, From on hand |
| 5. The carrying meals | One planned leftover, an eat-down meal if the week allows, one backup | This chapter | Plan: Planned leftover, Prep note |
| 6. The list | What the plan needs that the kitchen does not have | The plan, with amounts from How much to buy | Shopping list (Shopping and budget) |
The schedule comes first because it sets how much food the week needs. A plan that starts from the fridge can fill seven evenings with meals when the household is home for four, and the extra food is what ends up in the waste bag.
The eat-first items come second, before any meal is chosen, so you plan around what you already have. Meals chosen after reading the fridge can start from the chicken that has to be cooked by Monday. Extension services order these steps differently; the comparison is under other ways to plan, and the order here is our choice, not a finding that it works better.
How many meals to plan
Plan the meals the household will eat at home before the next shopping trip, and no more. EPA's Smart Shopping sheet asks how many meals you will eat at home this week and how long until the next trip (EPA, Smart Shopping: Shop with Meals in Mind), and EPA's page on preventing wasted food at home bases the list on that count, allowing for meals out, frozen precooked meals and leftovers (EPA, Preventing Wasted Food At Home). The count is subtraction, done on the schedule:
- Start with the evenings in the plan period: seven for a weekly shop, fourteen for a shop every two weeks.
- Take away the evenings nobody eats at home, and the ones you already know will be ordered in or eaten out. Write them as "out". This manual does not set how many there should be; Review and adjust measures what happened.
- What is left is the dinners the kitchen supplies. Some are leftovers or an eat-down meal, so the evenings someone cooks are fewer still.
Start with dinners, or with fewer. Utah State's tips say to start with dinners only and build up. Iowa State's post on planning with young children plans dinners only, with lunch as leftovers or sandwiches (Iowa State, Simplifying Meal Planning with Young Kids). Penn State's EFNEP post plans only the nights you will cook a full dinner (Penn State, Gearing up for Time Schedule Changes), and Michigan State says to start with one or two planned meals. Two or three cooked dinners make a full first plan in this manual.
Packed lunches go on the plan when they come from a dinner, because that dinner has to be cooked larger. A household that shops every two weeks puts the perishable meals in the days after each shop or a midweek top-up, and frozen and canned food in between.
How long planning takes. Utah State's Create Better Health curriculum asks readers to set aside 30 to 60 minutes once a week, and to start with a few days if a full week is too much (Utah State, Create Better Health curriculum). That is one program's figure, not a measured time. Your kitchen system sets a standing planning day (planning day).
2. Perishables first: the storage card sets the days
Once the evenings are known, keep times set the order of the days. A food that keeps one or two days in the refrigerator goes in the first days after it is bought, or into the freezer. A food that keeps a week goes later. Shelf-stable and frozen food fills the rest. This is what the storage card from How long food keeps is for (storage card).
The federal refrigerator times are safety limits for food kept at 40 °F (4 °C) or below. FSIS's refrigeration page gives raw poultry, ground meat and fresh fish 1 to 2 days, steaks, chops and roasts 3 to 5 days, and cooked casseroles, soups and stews 3 to 4 days (FSIS, Refrigeration and Food Safety). FoodSafety.gov's cold storage chart gives the same times for ground meat, poultry, steaks and chops, and leftover cooked meat (FoodSafety.gov, Cold Food Storage Chart).
| Food | Refrigerator time | Where it goes in the plan |
|---|---|---|
| Raw chicken or turkey, raw ground meat, fresh fish | 1 to 2 days | Cooked by day 1 or 2 after the shop, or frozen the day it is bought |
| Raw steaks, chops, roasts | 3 to 5 days | Early to mid-week |
| Cooked leftovers, cooked rice or pasta, soups, casseroles | 3 to 4 days | Within three days of cooking, or frozen within that time |
| Opened deli or luncheon meat | 3 to 5 days | Lunches in the days after opening |
| Opened can of low-acid food (beans, soup, most vegetables) | 3 to 4 days | The rest used within three days |
| Hard-cooked eggs | 7 days | Any day that week |
| Fresh produce | No federal day count; the storage card's produce rows | Tender greens and soft fruit early; roots, cabbage and apples later |
| Frozen food kept at 0 °F (-18 °C) | Safe while frozen; freezer times are for quality | Any day, with thawing planned ahead (Prep and batch cooking) |
Produce guidance is in How long food keeps and on the produce table. The keep-until calculator turns a time into weekdays: chicken cooked on Sunday is eaten by Wednesday to Thursday. Counting the cooking day as day 0 is our convention, so that "3 to 4 days" lands on named days (refrigerator times).
Fill the eat-first sheet before the plan's meal column. For each item write what it is ("2 lb chicken thighs, raw"), its eat-by day from the storage card or calculator, and the day and meal it goes into. If no meal on your list uses it in time, write "freeze" and the day. For a food with a "Best if Used By" date, the date marks quality under federal guidance; write it, and why you chose the day (date labels). Then give each eat-first item its meal before any other meal is chosen. When two perishable foods compete for one night, the shorter keep time takes the earlier day.
The plan is a draft for one week. When a food reaches the end of its keep time, the plan changes, not the food's date: a dinner that slips past Thursday does not stretch Sunday's chicken to Friday. Freeze it within its refrigerator time, or follow Leftovers and using it up. The federal times apply to food kept at 40 °F or below and refrigerated within 2 hours; this manual does not judge whether a particular item is safe to eat. This manual also makes no claim about the money or time a plan saves. Review and adjust measures your own planned week against your baseline.
Busy days and quick meals
The schedule's second job is to match meals to the time each evening allows. The plan sheet's Time available column has four choices: no cooking, 15 minutes, 30 minutes, an hour or more. Fill it from the week sheet before choosing meals.
- Longer meals on days off. Utah State's tips say to cook longer recipes on days off and plan larger recipes for more than one meal.
- Known meals on busy nights. Penn State says to use recipes you know how to cook and whose prep time you know. A new recipe is a guess about time. Test it
- Leftovers and no-cook meals on the shortest nights. A planned leftover only needs reheating. The Grant household's soccer night, Tuesday with 15 minutes, is that kind of night (fictional example).
- The cook's time, not the household's. Illinois Extension's method asks who is home to help (Illinois Extension, Mastering Mealtime).
If a perishable food falls on a busy night, move the food, not the night: cook it on the nearest longer evening and make the busy night its leftover. The tags from Your meal list make this quick (tags). If anyone has a food allergy or a medical diet, take meals only from the list as checked against the household's rules, and leave any question about a meal to their allergist, doctor or registered dietitian (The people at your table). Ask the authority
3. Meals that carry the week: planned leftovers, eat-down and backup
A planned leftover (some extension pages say planned-over) is food cooked on purpose in a larger amount so that part of it becomes a later meal. Cook once, eat twice names the same idea. Utah State's Create Better Health curriculum cooks extra rice on Monday for a stir-fry on Wednesday. Nebraska Extension's page on cooking for one or two plans two meals from one entrée, separates the extra before serving, and eats it within 3 to 4 days or freezes it (Nebraska Extension, Planning Healthy Meals for One or Two). Clemson's fact sheet includes at least one planned-over meal a week (Clemson HGIC 4200, Planning Meals for a Family).
- It falls inside the keep time. Cooked leftovers keep 3 to 4 days in the refrigerator under FSIS's leftovers guidance. Chicken cooked Sunday can be Tuesday's dinner and Wednesday's lunch; Friday is past it. A leftover turned into a different dish keeps its first cooking day, our convention (Leftovers and using it up).
- It is cooked large enough on the first day. How much to buy works out how much to buy for every meal the food is used in (the buy formula), and Prep and batch cooking covers dividing it into shallow containers and refrigerating it promptly (cooling).
- It can look different the second time. ReFED suggests recipe trios: a roast chicken one night, chicken tacos the next, chicken salad for lunch (ReFED, Consumer Food Waste). Jordan's baseline rice went in the bag because nobody wanted it again (fictional example); a second meal that does not repeat the first is one answer.
Tick Planned leftover on the day the leftover is eaten, and write in the cooking day's Prep note how much to set aside: "save half for Tue tacos, 2 portions for lunches".
An eat-down meal
An eat-down meal is planned around whatever is left in the refrigerator near the end of the plan week, rather than around a recipe. ReFED lists "eat down" among its five consumer habits: plan a day to eat the leftovers and extra food collecting in the fridge. Love Food Hate Waste, a UK program, puts a weekly "throw-it-all-in" meal on its checklist, and the VA's sample planner has a "Leftovers + green salad" night (VA, Weekly Meal Planner).
Put it on the last evening before the next shop's food is opened, so it catches what the week did not use. Write "eat-down" in the Meal column and fill it on the day; Leftovers and using it up gives the order for using things up (eat-down day). The keep times still apply: an eat-down meal uses food within its time, and anything past it goes to the waste log with its reason.
The backup meal
A backup meal is one meal written on the plan without a day, made from staples that keep for weeks or months, for the night the plan fails: a late shift, a sick child, no energy. Penn State's post says that if you end up ordering takeout, try again tomorrow, and Iowa State's young-kids post treats an occasional drive-thru the same way. A backup gives that night one more choice. Utah State's Be Well back-to-routine guide ends its sample week with "a simple pantry night" (Utah State Be Well, Back-to-Routine Meal Prep).
A backup works when its ingredients keep (canned, dry, frozen or long-keeping, so an unused backup wastes nothing), it takes about 15 minutes with your equipment, and its ingredients are on the staples list, so the next shop replaces them. Pasta with canned tomatoes, eggs with frozen vegetables, beans and rice, or a frozen meal already in the freezer all qualify if your household eats them. Write it in its own row with "backup" in the Day column.
4. A plan that bends: swaps and posting it
Iowa State's planner deliberately has no days of the week, so meals can be switched around, and Illinois Extension's last step is to be flexible and swap meals. This manual keeps weekdays on the plan, because keep times are counted in days, and lets meals swap under one rule.
The swap rule: a meal can move to another day if every perishable food in it is still within its keep time on the new day. In practice:
- Earlier usually works. Check that any leftover it was meant to make still has a day.
- Later needs the eat-by day. If the move runs past an item's eat-by day, freeze the item now, within its refrigerator time, and plan it into next week.
- A planned leftover moves with its first meal. If Sunday's cooking moves to Monday, its leftover meals each move a day, or one goes into the freezer.
- After the backup, the plan resumes. The meal it replaced moves to a later evening within its keep time, or its food is frozen.
Mark each swap on the plan the day it happens, crossing out rather than deleting, so that the review in Review and adjust can see what moved and why (causes).
Posting the plan
Put the plan where the people who eat from it can see it. Clemson's fact sheet posts it on the refrigerator with the family's activity schedule, Penn State posts each night's dinner on a chalkboard or the family calendar, and Colorado State says a posted plan lets others help. The plan page prints its own sheet (plan), and the binder prints all of them. Put the eat-first list beside it so anyone opening the fridge sees which food is next, and mark swaps on the posted copy. In a shared house, post the shared meals and the shared shelf's eat-first items; each person's own meals stay their own (shared houses).
5. Other ways to plan Go deeper
The order of work and the one-week horizon above are this manual's defaults. The Limits above hold for any method: the plan is a draft, keep times move the plan and not the food, and no method here comes with a measured saving.
Who puts what first
| First step | Source | What comes next |
|---|---|---|
| The week's schedule | Iowa State, Menu Planning; Colorado State, Meal Planning for Busy Families | Foods on hand, then meals |
| The inventory | Utah State, Food Waste Prevention Part 2: Meal Planning; the VA's planner, whose first column is "Items on Hand" | Main dishes from the inventory, then the list |
| The menus | Illinois Extension (after the schedule); Penn State (meals for the nights you cook); Clemson (two-week menus before inventory) | Check what you have, then the list |
| No set order | Michigan State, How to master meal planning | Its steps in any order |
None of these pages measures one order against another. This manual's order uses the schedule-first sources' count of meals and the inventory-first sources' rule of planning around food on hand.
Planning horizons
- Five days without weekdays: Iowa State's worksheet.
- A rolling plan: Love Food Hate Waste adds one day at a time. Iowa State's cooperative-planning post shops for about two weeks and, every few days, writes the next few days' meals on a sticky note (Iowa State, Cooperative Meal Planning).
- A cycle menu: a set of menus that repeats. Clemson makes about a two-week cycle; Utah State's Meal Planning 101 suggests two to four weeks, changed with the seasons (Utah State, Meal Planning 101). The two-week rotation in Your kitchen system is this manual's version (rotation).
- Weekly or monthly: Utah State's Food Waste Prevention page offers both; Penn State's author hopes to work up to a month. No extension source we read teaches a full monthly method step by step.
Every meal and snack, and theme nights
Clemson starts with the main meal and adds one meal at a time until the plan covers all meals and snacks, including those eaten away from home. Utah State's weekly planner has breakfast, lunch and dinner rows for seven days (Utah State, Weekly Menu Planner). If you add meals, add one kind at a time.
A theme night gives one evening a fixed kind of meal, such as Taco Tuesday. Clemson's sample week runs Meatless Monday, crock-pot Tuesday, soup and sandwich Wednesday, pasta Thursday, grill Friday and leftovers Saturday. N.C. Cooperative Extension in Watauga County repeats meals on fixed days each week (N.C. Cooperative Extension, Meal Prep and Planning). The Grant household's Friday pizza night is one (fictional example). Themes cut the choices each week; the keep-time order still places the perishable food.
6. See it: Jordan's first planned week See it
Jordan Pike is one of this manual's fictional cases; the amounts, dates and results here are invented. Jordan is 29, lives alone, works days and takes leftovers for lunch about twice a week. The kitchen has a refrigerator with a top freezer, one cupboard shelf, an oven and a microwave. Jordan shops on Saturday.
Known. In the baseline week Jordan cooked two dinners, ate one of leftovers and ordered in four. The waste bag held most of a bag of salad greens (spoiled), half a container of cooked rice (did not want the leftovers) and two yogurts past their date. The coming week: home every evening except Thursday, a work dinner.
The schedule. Seven evenings, less Thursday: six. Jordan chooses to order in on Friday and writes it as "out". Five dinners come from the kitchen, plus two packed lunches.
Eat first. Salad greens bought Saturday go on Sunday and Monday, because greens spoiled last time. Raw chicken thighs bought Saturday keep 1 to 2 days, so they are cooked Sunday. The yogurt goes on the sheet with its "Best if Used By" date, a quality date (How long food keeps).
| Day | Meal | Time | Uses up | Planned leftover |
|---|---|---|---|---|
| Sat | Shop | |||
| Sun dinner | Chicken thighs with rice and salad (all 2 lb of thighs cooked) | An hour or more | Raw chicken, greens | |
| Mon lunch | Leftover chicken | No cooking | Sunday's chicken | Yes |
| Mon dinner | Salad with eggs | 15 minutes | Greens, eggs | |
| Tue dinner | Chicken tacos | 30 minutes | Sunday's chicken | Yes |
| Wed lunch | Chicken and rice | No cooking | Sunday's chicken and rice | Yes |
| Wed dinner | Pasta with sauce and frozen vegetables | 30 minutes | Frozen vegetables | |
| Thu | Out (work dinner) | |||
| Fri | Out (ordered in) | |||
| Sat dinner | Eat-down | 15 minutes | Whatever is left and in time | |
| Backup | Black bean quesadillas from staples | 15 minutes | Canned black beans, cheddar |
Checked against the keep times. Chicken cooked Sunday is eaten by Wednesday to Thursday under this manual's day count, so Tuesday's tacos and Wednesday's lunch fall inside it. On Monday one more portion goes into the freezer for a later dinner (Prep and batch cooking). The rice cooked Sunday is eaten by Wednesday.
Assumed. That 2 lb of thighs covers Sunday, both lunches, the tacos and the frozen portion; How much to buy checks it. That the backup's tortillas come from the pack bought for the tacos.
Open, and who settles it. Whether Jordan wants chicken four times in four days: Jordan, by eating the week (the tacos are there so the second meal differs). Whether the backup gets used: the week itself, recorded as a swap. Whether ordering in drops compared with the baseline: the review in Review and adjust. This manual does not say what it should be.
Free sources behind this chapter:
- Iowa State, Menu Planning: a five-day, schedule-then-inventory method with a printable worksheet that has no weekdays.
- Utah State, Food Waste Prevention Part 2: the inventory-first method, written to cut food waste, with tips for starting with dinners.
- Clemson HGIC 4200: planned-over meals, theme nights and posting the plan. Use it for method; its nutrition section predates the current Dietary Guidelines.
- EPA, Preventing Wasted Food At Home: planning around what needs to be used up and counting the meals eaten at home.
7. Practice: one week on the plan sheet Practice
Minimum: one week of dinners on the plan sheet: the schedule, the eat-first items, two or three cooked dinners, one planned-leftover meal and one backup. Time: 30 to 45 minutes for a first plan. Materials: your week sheet, inventory and storage card from Kitchen inventory, How long food keeps and The people at your table, your meal list from Your meal list, and the plan page or a sheet of paper.
- Set the plan period, from the day after your next shop to the day of the one after.
- Copy the schedule. Fill Who and Time available on the plan sheet from your week sheet, and write "out" on evenings nobody eats at home.
- Count the dinners: evenings left, less any you know will be ordered in.
- List eat-first items from the eat-first shelf, the fridge list and the perishables you will buy. Give each an eat-by day from the storage card or the keep-until calculator on the eat-first sheet.
- Give each eat-first item a day, shortest keep time first, in Uses up.
- Choose meals for the cooking nights from your meal list, matched to each night's time. Tick From on hand where the kitchen can already make it.
- Mark one planned leftover within 3 to 4 days of its cooking day, with the amount to set aside in the Prep note.
- Write the backup in its own row, and post the plan with the eat-first list beside it.
- Add an eat-down meal on the last evening before the next shop.
- Add packed lunches that come from dinners, and size the dinners for them.
- Try a second week with a theme night or a rolling plan, and note which you prefer.
8. Your kitchen Your kitchen
9. Check your work Check your work
Criteria
- Does every day of the plan period have a line: a meal, "out", a leftover or "eat-down"?
- Does the number of dinners match the evenings people are home, less the ones written as out?
- Does every eat-first item have an eat-by day and a meal on or before it, or "freeze" and a day?
- Is the shortest-keeping food on the earliest days after the shop?
- Is there one planned leftover within 3 to 4 days of its cooking day?
- Is there one backup made only from staples, written without a day?
- Does each meal's time fit the evening's?
Worked example
Jordan's plan (fictional example) meets each criterion. Every day has a line, including "out" on Thursday and Friday. Five dinners from the kitchen match six evenings home less one ordered in. The greens fall on Sunday and Monday, and the raw chicken is cooked Sunday, inside its 1 to 2 days. The tacos and Wednesday's lunch come before Sunday's chicken reaches its Wednesday to Thursday limit. The backup uses canned beans and cheddar from the staples list. The two 15-minute evenings carry a salad and the eat-down. What the plan does not show yet is whether 2 lb of chicken covers it all; How much to buy checks.
Common mistakes
- Planning seven cooked dinners for a week with three evenings out. Count the evenings first.
- Choosing meals before reading the fridge, so the eat-first items have no day.
- Putting fish or ground meat late in the week because that night has time. Cook it early, or freeze it the day you buy it.
- Planning a leftover for the fifth or sixth day after cooking. Freeze a portion within the 3 to 4 days instead.
- A backup that needs fresh food, so it spoils if the week goes to plan.
- Rewriting the plan when it changes instead of marking the swap, so Review and adjust cannot see what happened.
What is still unresolved
This chapter does not say how much to buy for each meal; How much to buy works that out from people, portions and yields. Whether the week goes as planned, and what it costs, shows up on the receipt (Shopping and budget) and in the review of the planned week (Review and adjust). Whether a meal suits someone with an allergy or a medical diet is settled by their allergist, doctor or dietitian.