Households that want enough weekly structure to reduce repeated decisions without pretending every meal, schedule or leftover can be fixed in advance.
RecipeWanted Resources
Weekly plan, shopping & prep toolkit
Meal Planning Tools
Build a flexible weekly meal plan around real schedules, planned leftovers, freezer meals and use-first food; keep shopping and prep notes beside the plan; review weak spots; then save, copy, export or print the working plan locally in your browser.
Weekly plan builderLeftover-awareShopping + prep notesLocal save + CSV
Practical Resource GuideEditorial guidance and clearly labelled resource links.
Quick start
Before you start
Turn a real week into an editable seven-day meal structure with explicit busy-day, buffer and leftover intent, then keep meal names, servings, use-first food, shopping and prep notes in one working plan.
Who is eating, which meal slots matter, busy/low-time days, whether the week needs more flexibility, whether planned leftovers are welcome, and any food that should be used first.
Editable weekly rows, nine planning roles, use-first/shopping/prep lists, structural review warnings, browser-local save/load/delete, copy/CSV/print, seven planning-job reference cards, six presets, sources and ten FAQs.
Seven-day editable planNine planning rolesSix presetsUse-first listShopping listPrep/defrost listStructural reviewLocal save/load/deleteCopy/CSV/PrintSources + 10 FAQs
Examples for home cooking and teaching
Choose a relevant example and check the assumptions before using it in your kitchen or lesson.
Standard week
Keep the established balanced pattern and edit only the meals that need changing.
Busy week
Bias low-time days toward quick, leftover, freezer and flexible roles without pretending the meals themselves are known.
Use-first week
Keep food already owned visible and deliberately create places where planned extras can be used.
Use this againAt the start of a new planning cycle or when the current week changes enough that the structure should be regenerated.
Save on This Device stores the working planner locally in this browser profile. My Resources detects only that the known key exists and never reads the plan payload.
Practical shortcut: Neutral defaults preserve the previous planner. Buffer and leftover controls are opt-in, and the review flags missing meal names, high-effort busy-day clashes, unpaired leftover roles, lack of schedule buffer and an empty use-first list.
Trust & safety at a glance
Use the result for the decision it was built to support
Generated roles are workflow suggestions, not claims that a particular meal is suitable, affordable, nutritious, safe to store or safe to reheat.
Household meal-planning / leftover workflow support6 subject references · Reference register provided below; no current review date is asserted for this route.
Organise weekly meal roles, household servings, busy days, use-first food, shopping notes and prep tasks while making uncertainty and handoffs explicit.
Not for nutrient adequacy scoring, medical diet planning, allergy clearance, grocery-price prediction, exact food-storage life, use-by overrides or automatic food-safety decisions.
The weekly planning method is general. The specific leftover/chilling examples on the page are UK FSA examples; users elsewhere must apply the relevant competent authority and product instructions.
On-screen working data stays in the browser. Save on This Device uses the historic rw_resources_meal_planner_v2 localStorage key for compatibility. The module sends no meal names, shopping list, prep notes or medical information to the Resources server. Resource Cards are optional downstream surfaces. They cannot change generated meal roles, review warnings, source guidance or the nutrition/allergen/price/safety boundaries.
When to stop and verify:Use the relevant competent authority, product label/instructions, qualified clinician/dietitian/allergy professional or dedicated Food Storage/Allergy tools when a decision exceeds general weekly planning.
Privacy scope: this describes the working-data behaviour of this Resources tool only. Site-level cookies, analytics, consent and other storage/access technologies remain governed by RecipeWanted’s wider privacy/CMP configuration and applicable law.
Source scope: external authorities and specialist references support specific information; linking to them does not mean they have reviewed, approved or endorsed RecipeWanted.
How this Resource reaches its result
MethodDeterministic editable weekly meal-structure generator
With Standard buffer and Standard leftovers, the same style/busy inputs preserve the previous dinner-role baseline. New controls only affect generation when explicitly selected; every generated role remains editable.
Can it be reproduced?Deterministic under this version
PHP vectors prove the legacy patterns, busy override, neutral defaults, new control semantics, input normalization, source/privacy/export boundaries and preset/FAQ contracts; the browser publishes its own self-test marker.
Evidence6 registered references · RecipeWanted review UNREVIEWED
NHS/GOV.UK support the overall-diet boundary; FSA supports leftover/chilling/allergen boundaries; WRAP supports the household food-management and displaced-meal context. None certifies a RecipeWanted meal plan as safe, nutritious, cheapest or waste-free.
IndependenceNo paid or analytics influence over the result
The specialist contract declares that commercial relationships and analytics do not alter this tool's results. The specialist contract disables runtime AI for this tool.
Uncertainty stays explicit: The planner cannot know real recipe ingredients, preparation time, appetite, grocery prices, pack sizes, storage conditions, allergens, nutrient adequacy, actual leftovers, schedule changes or local food-safety requirements.
Evidence reference: RWRES-A035AE6963DE1FDF — a RecipeWanted integrity/reference fingerprint for this release evidence set, not certification or third-party endorsement.
Report a factual or method concern if a source conflicts with the tool, a calculation appears wrong, or a boundary needs review.
Flexible weekly planning
A useful meal plan should make the week easier to change
Start with who is eating, which days are busy and what food is already available. Then give the week enough structure to reduce repeated decisions without locking every meal to a plan that becomes useless as soon as one evening changes.
Calendar before recipes
Decide which days need quick food, leftovers or freezer support before choosing ambitious meals.
Keep a buffer
One flexible/use-up/freezer slot can absorb a changed plan and protect more perishable meals from being pushed aside.
Plan food you already own
Check the fridge, freezer and cupboards first so the shopping list fills genuine gaps instead of starting from zero.
Separate planning from nutrition or medical advice
This tool organises meals and tasks. It does not assess nutrient adequacy, allergies, medical diets or the safety of a particular food.
Flexible weekly planner
Generate a structure, then fill it with meals that fit your week
Choose the week, household size, meal coverage and planning style. Mark busy days, then optionally ask for more schedule buffer or a different leftover pattern. Generate the structure and edit every meal, role, serving count and note; shopping and prep lists stay beside the same working plan.
Local-browser working dataThe planner runs in this browser. Optional saved drafts use browser local storage; this final Tool 7 module does not send meal names, shopping lists or planning notes to RecipeWanted.
Anyone with access to the same browser profile may be able to see a saved local plan. Avoid entering sensitive medical or personal information and delete saved copies when they are no longer needed.Week setup
Set the constraints before generating the plan
Start from an example:
Plan slots0
Meals named0
Backup / flexible slots0
Review items0
Planning pattern—
Supporting lists
Keep the food and tasks that affect the plan beside it
Meal-plan review
Planning boundary:A meal planner organises intentions; it does not prove food is safe, nutritionally adequate or suitable for allergies/medical diets. Keep safety-critical information in the appropriate RecipeWanted/official guidance and adjust the plan when the real week changes.
Seven planning jobs
A useful weekly plan coordinates more than meal names
The meal itself is only one part of the system. These seven jobs cover the schedule, inventory, leftovers, shopping and preparation decisions that make a plan workable.
Calendar & availability
A plan fails quickly when the meals assume more time than the household actually has. The calendar should constrain the menu, not the other way around.
- Useful core
- Mark busy evenings, eating-out plans, late arrivals and days with enough time for longer cooking before choosing meals.
- Check
- Who is eating, when people arrive, active cooking time, whether the meal can wait or reheat, and which days are already committed.
- Watch for
- Avoid filling every day with a high-effort meal just because the week looks empty on paper.
Flexible space & backup meals
Displaced meals are normal. A useful plan has somewhere for a cancelled or delayed dinner to go instead of treating every slot as fixed.
- Useful core
- Keep at least one movable, freezer, pantry or use-up option so the week can absorb a changed schedule without wasting planned fresh food.
- Check
- Flexible/freezer slots, shelf-stable backup food, which planned meals can move, and which ingredients are most perishable.
- Watch for
- A seven-day plan with seven non-movable fresh meals can be more fragile than helpful.
Leftovers & batch use
Leftovers save work only when they are planned into the week and handled safely rather than discovered at the back of the fridge.
- Useful core
- Name the meal that creates leftovers and the later slot that will use them. Use batch cooking only when storage, cooling, freezing and reheating are suitable for the food.
- Check
- Expected extra portions, storage route, when they will be eaten, reheating method and whether freezing is more appropriate.
- Watch for
- Do not rely on a meal-planning label to prove leftovers are safe; use current storage and reheating guidance.
Use-first food & inventory
Planning from food already owned reduces duplicate buying and makes perishable items visible before they become waste.
- Useful core
- Check the fridge, freezer and cupboards before shopping and write down food that should influence the next few meals.
- Check
- Opened foods, short-dated ingredients, frozen portions, pantry staples and ingredients already committed to another meal.
- Watch for
- Use-by safety decisions still follow the label and official guidance; a plan should not extend a safe-use period.
Shopping list & shared ingredients
The list becomes more useful when it reflects household size, what is already available and the number of meals that will really be eaten at home.
- Useful core
- Build the shopping list from the actual plan, then look for ingredients that can serve more than one meal without forcing unwanted repetition.
- Check
- Pack size, household count, meals eaten elsewhere, loose/frozen alternatives, shared ingredients and whether a large pack will genuinely be used.
- Watch for
- A lower unit price is not a saving when the extra food is unlikely to be used.
Prep, defrost & make-ahead tasks
A meal can be simple to cook but still fail on the day because one earlier task was forgotten.
- Useful core
- Keep the jobs that happen before dinner next to the plan: defrosting, soaking, marinating, batch prep, chopping or moving a freezer meal into the correct workflow.
- Check
- Safe defrost route, prep lead time, container space, equipment, whether ingredients can be prepared ahead and what must wait until service.
- Watch for
- Do not use room-temperature shortcuts where safe chilling/defrost guidance requires another method.
Review, repeat & simplify
The best planning system gets easier with repetition. A recurring list of reliable quick meals, freezer meals and favourites reduces weekly decision fatigue.
- Useful core
- At the end of the week, keep the meals and structures that worked, remove unnecessary admin and note where time, portions or shopping assumptions were wrong.
- Check
- Meals repeated happily, leftovers actually used, food thrown away, unexpected schedule changes and tasks that created more work than they saved.
- Watch for
- If maintaining the planner becomes a weekly project of its own, reduce the number of fields or plan fewer meals.
Match the system to the problem
Different weeks need different planning rules
Use the smallest amount of structure that solves the actual problem. A fixed seven-dinner plan is not automatically better than a five-meal plan with deliberate flexibility.
| Situation | Useful structure | Main check |
|---|---|---|
| Very busy week | Quick meals + freezer support + one flexible slot | Do the chosen meals genuinely fit the available active cooking time? |
| Food-waste problem | Inventory first + use-up meal + smaller/targeted shopping list | Which food already owned is most likely to be forgotten? |
| Budget pressure | Staples + shared ingredients + realistic pack sizes + planned leftovers | Are you buying more because it is cheaper per unit but unlikely to be used? |
| Different household schedules | Meals that can be safely portioned, assembled separately or intentionally reheated | Who is eating, when, and what storage/reheating process is actually practical? |
| Want more variety | Keep reliable staples and add one or two deliberate new meals | Does novelty create extra one-use ingredients or unrealistic prep? |
| Batch-cooking week | Named batch session + planned leftover/freezer destinations | Can the food be cooled, portioned, stored and reheated safely in the intended way? |
Use the right RecipeWanted tool
Move the calculation or safety question to the system built for it
The planner stays focused on the week. Scaling, storage, shopping-list consolidation and recipe discovery already have their own routes.
Recipe discoveryRecipe Search
Find the actual dish after the planner has identified what kind of meal the slot needs.
Search Recipes → Portions & batch yieldRecipe ScalerChange ingredient quantities when the household count or batch target changes.
Open Recipe Scaler → Storage supportFood Storage ToolsMove storage, labelling, chilling/freezing and related tool decisions out of the meal plan itself.
Open Food Storage Tools → Consolidate ingredientsMulti-Recipe Shopping ListWhen recipes and quantities are known, use the dedicated builder to combine compatible ingredients without asking this weekly planner to guess recipe contents.
Open Shopping List Builder →Additional meal-planning resources
Use extra tools only when they remove repeated planning work
Active cards from the central Meal Planning Tools collection appear here. Commercial relationships are labelled and do not influence the planner structure above.
No additional Resource Cards are active yet.The weekly planner remains fully usable without them.
Balance, leftovers & safety
Use planning guidance without turning it into a nutrition or safety guarantee
The planner is intentionally conservative: it organises schedule, meal roles and working lists, while medical, nutrition, allergen, food-storage and exact-price questions remain outside the planning engine.
Think across the day or week
UK Eatwell guidance describes overall dietary balance across a day or week rather than requiring every single meal to contain the full pattern. The planner therefore does not score individual meals as “healthy” or “unhealthy”.
Special dietary needs require the right advice
Allergies, medical diets and individual nutritional requirements are not inferred from meal names. Use suitable professional/official guidance and the dedicated allergen systems where applicable.
Plan leftovers with a storage route
For UK households, cool and refrigerate cooked leftovers promptly, normally within two hours; use within 48 hours or freeze, and reheat only once. Rice needs extra care: cool ideally within one hour and use refrigerated rice within 24 hours. Follow food-specific guidance and any shorter product instructions.
Do not turn flexibility into unsafe delay
Moving a meal in the calendar does not extend a use-by date or safe storage period. The label, handling history and current food-safety guidance still control the decision.
NHSThe Eatwell Guide
Current UK healthy-eating reference used only for the boundary that overall balance can be considered across a day or week. The planner does not score individual meals or infer nutrient adequacy.
Open current source →GOV.UK / Office for Health Improvement and DisparitiesThe Eatwell GuideOfficial UK dietary guidance and supporting resources. Special dietary or medical needs remain outside this general meal-planning engine.
Open current source →Food Standards AgencyCooking your food — using leftoversCurrent UK household guidance on cooking checks, cooling leftovers, refrigeration/freezing and reheating. Planning roles do not extend safe storage periods.
Open current source →Food Standards AgencyHow to chill, freeze and defrost food safelyCurrent household chilling/freezing/defrosting guidance used for the boundary around make-ahead, freezer and leftover planning. Product instructions and local competent-authority guidance still apply.
Open current source →Food Standards AgencyFood allergies, intolerances, and coeliac diseaseOfficial consumer allergen information used to keep allergy and coeliac suitability outside the meal-name planner. The tool never infers that a meal is safe for an allergy.
Open current source →WRAPUnderstanding household food waste in the UK: Household Food Management Survey 2025Published in March 2026, this current UK evidence covers buying the right amount, displaced meals, pack-size behaviour and household food-management skills relevant to flexible planning and waste reduction.
Open current source →Guidance changes and the RecipeWanted planner is global in reach. The specific leftovers/chilling examples above reflect current UK Food Standards Agency guidance; users elsewhere should apply the competent authority and product instructions for their location.
Practical questions
Meal-planning questions that change whether the system lasts
Do I need to plan every meal for all seven days?
No. Many households only need to plan the meals that create the most friction, often dinners. The planner supports dinner-only, lunch-and-dinner or all-meals mode so the system can stay as small as useful.
How much flexibility should a weekly plan include?
There is no universal number. If schedules often change, one or more flexible, freezer, quick or use-up roles can make the plan more resilient. Use the flexibility controls to leave room for changes; every suggested meal role remains editable.
Can meal planning reduce food waste or save money?
It can support both by helping you check what you already have, buy closer to what the week requires and give leftovers a destination. It cannot guarantee savings because prices, pack sizes, appetite, schedule changes and shopping decisions still matter.
How should leftovers appear in the plan?
Name or identify the meal that creates extra portions and the later slot intended to use them. Then apply the correct cooling, storage, freezing and reheating guidance for that food rather than relying on the planner role alone.
What does the Planned Leftovers control actually do?
It changes generated workflow roles only. More creates deliberate cook-extra/batch and leftover handoffs; Fewer reduces generated leftover roles. Standard preserves the previous planner pattern. None of these settings decides whether a specific leftover is safe.
How should I plan for allergies, coeliac disease, diabetes or another medical diet?
Use the household’s established professional, medical and allergen guidance. This planner does not diagnose needs or judge suitability from a meal name. Avoid putting sensitive medical information into browser-local notes where possible.
Is one weekly food shop always better?
No. Shopping frequency depends on storage, transport, household routine, pack sizes and how quickly fresh food will be used. Plan the shopping pattern around what can realistically be stored and eaten rather than forcing a once-a-week rule.
Why does the shopping list stay manual?
The weekly planner deliberately does not scrape or guess recipe ingredients. A manual list is safer when meals may come from RecipeWanted, cookbooks or household favourites. When exact recipe ingredients are available, hand off to the Multi-Recipe Shopping List Builder.
Can this tool calculate my grocery budget or predict current food prices?
No. It does not fetch or invent grocery prices, discounts, pack sizes or local availability. Budget pressure can influence how you plan, but actual costing belongs in a current price-aware workflow or the Recipe Cost Calculator where you enter your own prices.
Can I move a leftover or use-first meal to a later day because the plan changed?
You can move the calendar slot, but the move does not extend a use-by date, safe storage period or handling history. Recheck the label, storage conditions, current competent-authority guidance and the dedicated Food Storage Tools before relying on the new date.
Continue across RecipeWanted
Use the next route for the next question
Related Resources handle the next practical job. The ecosystem handoffs add another useful format when a visual, video, current update, longer article or wider recipe browse answers something different. Cooking Education remains the deeper teaching layer.
01Recipe Scaler
Scale a known recipe when the household or batch yield changes.
Open related Resource → 02Food Storage ToolsReview storage, chilling, freezing, defrosting and date handling outside the calendar itself.
Open related Resource → 03Multi-Recipe Shopping List BuilderConsolidate known recipe ingredients once exact recipes and quantities are available.
Open related Resource → 04Meal Planning & PrepOpen the related Cooking Education route for deeper method and explanation.
05Weekly Meal PlanningOpen the related Cooking Education route for deeper method and explanation.
06Batch CookingOpen the related Cooking Education route for deeper method and explanation.
07Freezer Meal PrepOpen the related Cooking Education route for deeper method and explanation.
08Search RecipesApply the tool or decision inside a complete RecipeWanted dish.
Legal, privacy & fair-use notice
Free Resources, with clear limits and clear data boundaries.
RecipeWanted Resources provides general cooking information, deterministic calculations, planning aids and reference tools. It is not legal, medical, dietetic, allergy, regulatory or other professional advice, and it does not replace product labels, manufacturer instructions, competent-authority guidance or qualified professional advice where those are needed.
Each tool explains how it handles your entries. This Resources analytics dataset does not retain recipe or ingredient names, pantry lists, allergy, dietary or health information, other free text, exact quantities, visitor/session/account IDs, IP addresses, user-agent strings or referrer URLs.
This Resources statistics layer is currently enabled and records only allowlisted aggregate interaction and coarse workflow/build-shape counters. Daily aggregate buckets are retained for up to 730 days. Aggregate results are for RecipeWanted/QHE internal RecipeWanted service improvement only; they are not sold or used by this layer for advertising measurement, individual profiling or cross-site tracking.
Any reasonable fair-use or availability rules for free tools are separate from privacy law. Access is not conditional on participating in Resources analytics, and “fair use” is not treated as consent or as a legal basis for collecting personal data. On instrumented Resources pages, the usage-statistics panel provides a simple, free objection control.
Wider site/infrastructure scope: ordinary hosting, security, caching, firewall, consent-management or server-log systems may process technical request information outside the Resources aggregate dataset. Those systems remain governed by RecipeWanted’s wider privacy/CMP arrangements and published privacy information. This Resources notice does not claim that every web request is anonymous.
External authorities linked elsewhere in Resources support specific facts or methods; their inclusion does not mean they approve or endorse RecipeWanted. If a higher-consequence decision is uncertain, stop and verify it with the appropriate current source.First-party usage statistics
Help RecipeWanted learn what is actually useful
Resources records aggregate usage statistics such as qualified tool views, whether a working surface is started, route-level value actions, coarse read depth, broad workflow/build-shape buckets and which non-commercial RecipeWanted handoffs are used. Build-shape signals are deliberately coarse (for example, a small/medium/large row-count bucket or a selected calculator mode): RecipeWanted does not send the recipe name, ingredient list, pantry items, allergen/dietary choices, free text or exact quantities to this analytics dataset; it does not create a visitor/session ID; and it does not store IP addresses, user-agent strings or referrer URLs in the analytics dataset.
Purpose: help RecipeWanted/QHE decide which free tools, workflows, supporting content and first-party integrations to improve next. Aggregate statistics may be reviewed internally across QHE only for that same RecipeWanted service-improvement purpose. They are not sold and are not used by this layer for advertising measurement, cross-site tracking or individual profiling. Free access is not conditional on this measurement: opting out does not disable or reduce any Resource tool.
What is counted and retained?
Allowed counters include 5-second qualified views, 30 seconds of visible engagement, 50%/90% read depth, first working-surface use, selected non-commercial feature/export/continuity actions, hub task choices, broad allowlisted workflow/build-shape buckets and RecipeWanted internal/ecosystem handoffs. Counts are merged directly into UTC daily buckets and retained for up to 730 days under the current admin setting. The only browser preference this layer writes is the first-party objection cookie after you choose to opt out; removing the objection deletes that preference. This describes the Resources aggregate dataset only; ordinary hosting, security, caching, firewall, consent-management or server-log systems remain governed separately by RecipeWanted’s wider privacy/CMP arrangements.
Privacy informationYou can object simply and free of charge at any time. The preference applies only to this first-party Resources statistics layer.
Next step
Use the tool, then get back to cooking.
Resources should remove friction around the task rather than become another layer to manage.
