How to build a weekly meal plan around your nutrition goals

1. Turn “eat better” into a short planning brief

A useful weekly brief has three parts: the person, the food pattern and the few numbers worth checking. Start with the person whose portions you are planning. Australian and New Zealand Nutrient Reference Values vary by life stage and sex, and they use different reference types. The official NRV introduction explains RDI, AI and upper references.

Then write down constraints that affect whether the plan will happen: meals out, cooking nights, leftovers, budget, available equipment, dietary preference and foods the person enjoys. Choose two or three nutrient checks that relate to the plan—perhaps protein plus two vitamins or minerals—without treating them as a complete health score.

Eat for Health’s “Putting it all together” guidance suggests thinking about how food-group serves will be spread across meals and snacks. Its meal-planning guidance also emphasises planning those snacks, not only dinner.

2. Build from anchors, batches and flexible gaps

Put fixed events in first: a work lunch, dinner out or a night with no time to cook. Next choose a few anchor meals that cover the hardest parts of the week. Use batches deliberately, but do not turn seven days into the same menu.

The quantities are planning examples, not tested recipes. If the oats breakfast is used five times, the week needs 250 g oats and 1.25 L milk or alternative for those breakfasts: 5 × 50 g = 250 g and 5 × 250 mL = 1,250 mL. Check the actual product and portion in the nutrition calculation; “fortified alternative” does not describe one standard nutrient profile.

Give each meal a realistic personal portion. A recipe may make four prepared servings while one adult is assigned one serving on three dates and the fourth is frozen. Prepared servings drive the batch and shopping list; personal portions drive that person’s nutrition totals.

3. Review the week without hiding weak days

Use the weekly view to find patterns, then open the days that created them. This illustrative example follows one nutrient with complete reported data and an invented 11-unit daily planning target. The units and amounts do not describe a real nutrient or food.

The average is below the illustrative 11-unit target, but it is more useful to inspect Tuesday and Saturday than to add food randomly across the week. The Wednesday result should not be subtracted from Tuesday’s gap. Nutrient references are generally expressed as daily intakes; a weekly average is a pattern-finding view, not permission to ignore an applicable daily upper reference.

In MorselMetrics, a seven-day average divides by seven calendar days, including empty dates. If Saturday is blank rather than genuinely low, finish the plan before interpreting 8.9—or any weekly average. If a food does not report this nutrient, the reported subtotal is incomplete and should not be presented as a confirmed low intake.

4. Make one change that fits the actual day

Open the lowest complete day and check the meal slots, portions and food matches. The best change may be correcting a portion, adding a forgotten side, swapping a meal, or planning a snack you would genuinely eat. Recalculate the whole day because a change affects energy, macros and several micronutrients at once.

1. Correct the record first. Resolve a missing meal, wrong food state or unassigned portion before changing the menu.
2. Find the food contributors. Open the nutrient detail to see which planned foods supply the reported amount.
3. Compare one realistic option. Add a named recipe, side or snack with a checked portion; do not add an abstract “nutrient boost”.
4. Review knock-on effects. Check the revised day’s energy, macros, other nutrients, preparation and shopping needs.
5. Keep uncertainty visible. A missing value remains unknown after the edit unless the underlying food record changes.

The Australian Food Composition Database provides data for foods commonly available in Australia, with nutrients reported according to the available data. See the FSANZ AFCD overview. Database estimates help compare plans; they do not measure the exact meal on your plate or diagnose a deficiency.

5. Build and review the week in MorselMetrics

1. Set the week and person. In the planner, choose the seven-day view and the person whose portions you are entering.
2. Add fixed and anchor meals. Use saved recipes or catalogue recipes. Set prepared servings, then assign the person’s actual portion.
3. Reuse deliberately. Copy a day, copy an individual meal, or save a reusable week when that reflects the plan. Review overlaps before adding copied meals.
4. Open Nutrition. Read daily amounts first, then period totals and daily averages. Separate Below reference from No data.
5. Adjust one weak day. Use the contribution detail or Improve this day for practical ideas; adding a suggestion remains your choice.
6. Check the shopping list. Confirm each batch is counted once, subtract pantry amounts and review changed purchase overrides.

If you want the software to propose empty meal slots, use the target-based Autofill guide. Manual planning remains useful when you already know the week’s meals or want direct control over every recipe.

Keep exploring

Reviewed 12 October 2026 against MorselMetrics planner, household-reference, copy-week, nutrient-period and shopping behaviour. General guidance: Eat for Health meal-planning, food-group and Nutrient Reference Value pages; food-data scope: FSANZ AFCD Release 3. The seven-day figures are explicitly invented arithmetic, not food data or advice.