Weekly macro meal plan · Guide

How to build a weekly macro meal plan that holds

Six steps from macro targets to a week of meals that survives a training schedule. A simple framework you can run by hand — or have Mero generate end-to-end when the app opens.

One email. We’ll only write when there’s something real to say.

Why most weekly plans collapse

“The macros were right.
The week didn’t survive contact with training.”

A weekly macro meal plan that holds isn’t a spreadsheet with seven identical days. It’s a sequence: set the targets, map the training shape, assign the meals, pull the grocery list, prep what batches, and tune what didn’t work. Six steps. Done in order.

Step 1

Set your macro targets.

Start with the day. Calories come from bodyweight × an activity multiplier (roughly 14–16 kcal/lb for most active athletes, adjusted for goal). Protein floor is 0.8–1.0g per lb of bodyweight. Fat floor is 0.25–0.4g per lb, with a hard minimum around 50g/day. Carbs are the remainder.

  • Cutting. 300–500 kcal/day below maintenance. Protein high. Fat at the floor. Carbs flex with training.
  • Recomp / maintenance. ±100 kcal of maintenance. Protein high. Fat and carbs balanced to preference.
  • Building. 200–400 kcal surplus. Protein steady. Carbs absorb most of the surplus.
  • Sanity check. If the calorie target plus the protein floor leaves room for both fat and carbs to clear their floors, the targets are workable.
Mero macro targets screen showing daily calorie target, protein, carbs, fat, and per-day distribution
Targets · Protein · Carbs · Fat

Step 2

Map your hard and rest training days.

Sketch the seven days. Tag each one: hard, strength, recovery, rest, long. The high-output days — hard intervals, two-a-days, the long day — need more carbs and (depending on the goal) more total calories. Recovery sits next to hard. Rest day settles.

  • High-output day. +30 to +60g carbs and +200 to +400 kcal over the baseline day. Time the carbs around the session.
  • Recovery / easy day. Protein steady, carbs settle, fat may rise slightly to hold satiety.
  • Rest day. Closest to baseline. The day doesn’t need to be artificially low.
  • Long day or two-a-day. Treat combined session output as one big day. Don’t starve the second session because the first ate the budget.

Step 3

Assign meals across the week.

With targets and training tags in place, fill the days. Protein anchors each meal; carbs land where training needs them; fat rounds out the remaining calories. Re-use a small set of meals across the week — variety helps adherence, but a dozen unique recipes a week is a recipe for not following any of them.

Common mistakes

  • Identical macros every day, regardless of training.
  • Twelve new recipes you’ve never cooked.
  • Carbs all stacked at dinner, no pre-workout fuel.
  • No pre/post structure on session days.

What holds

  • Day macros that bend with training tags.
  • 5–7 anchor meals you actually cook, rotated.
  • Carbs placed pre- and post-session, not piled at night.
  • One protein, one carb, one veg per main meal; snacks fill gaps.
Mero weekly plan screen showing hard days, rest days, meals, and an accept plan button
Weekly plan · hard, easy, rest

Step 4

Generate the grocery list.

Sum quantities across every assigned meal. Aisle-group the list — produce, protein, dairy, dry goods, frozen, condiments — so the shop runs in one pass. Reconcile across recipes: if three meals call for spinach, buy one bag, not three half-bags. Note what you already have so the list doesn’t double-buy.

  • Aisle order matters. The store layout dictates the order, not the recipe order.
  • Quantities reconciled. Sum every recipe’s call for an ingredient before writing it down once.
  • Pantry pass first. Mark what’s in stock. Subtract from the list before shopping.
  • One shop, not three. A consolidated list keeps Wednesday top-ups off the calendar.

Step 5

Prep the week in the right order.

Sunday prep that holds is mostly about sequence. Start the oven first — sheet pans and roasts run on their own clock. While that’s going, run a stovetop block (grains, sauces, eggs). Cold assembly (jars, dressings, portioning) goes last. Cook what batches well in bulk; leave single-serve meals on the daily list.

  • Oven block. Biggest, longest items first. One sheet pan can cover four lunches and a dinner protein.
  • Stovetop block. Grains, sauces, sautés while the oven runs.
  • Cold assembly. Portion, jar, dress, label.
  • Storage windows. Cooked grains 4–5 days. Cooked proteins 3–4 days. Anything beyond that goes in the freezer.
Mero prep workflow screen showing Sunday prep checklist
Sunday prep · ordered for active time

Step 6

Track adherence and tune next week.

Honest tracking beats elaborate logging. Tap or note what you actually ate — not what you intended. At week’s end, ask three questions: did the scale move the right direction, did energy hold through hard sessions, did you finish what you prepped. Adjust calories ±100–200/day if the scale is off-target. Carry forward what worked.

Signals to ignore

  • One bad day mid-week.
  • Daily macros that miss by 5%.
  • Scale fluctuations of less than 1% bodyweight.

Signals to act on

  • Two weeks of no scale movement in a cutting or building phase.
  • Energy crashes on the hard days — usually a carb timing or volume issue.
  • Repeated unfinished prep — the plan is too ambitious or wrong on volume.

Spreadsheet vs Mero

You can run the six steps by hand.
Mero runs them for you.

A spreadsheet works. It also burns 60–90 minutes every Sunday and resets to a blank tab every Monday. Mero generates the same six steps from your targets and training calendar, then tunes the next week from what you actually checked off.

Spreadsheet or template

  • Built manually from scratch or copy-pasted.
  • Rebuilt or re-pasted every Sunday.
  • Macros and grocery quantities calculated by hand.
  • No automatic link to the training week.
  • Adherence tracked in a separate tool, if at all.

Mero

  • Generated from your macro targets and training calendar.
  • Adapts to next week’s training shape.
  • Grocery list and Sunday prep workflow generated with the plan.
  • Carries last week’s learning into next week.
  • Adherence captured as you tap planned meals.

FAQ

Common questions about weekly planning.

How long should planning a weekly macro meal plan actually take?

30–60 minutes the first week. 10–15 minutes once you have a base plan to adapt. Most of the time goes to deciding meals, not the macro math itself.

Do I need to hit my macros to the exact calorie?

No. Targets are directional. Hitting the weekly totals matters more than landing every single meal on the exact macro. A ±5% daily range averaged over a week is enough for most goals.

How often should I re-plan?

Weekly. Re-evaluate the macro targets themselves every 2–3 weeks if a goal phase is active. Faster if the scale, energy, or adherence is moving in the wrong direction.

Should the plan be the same every week?

The shape can repeat if your training stays steady. The specific meals shouldn’t — variety helps adherence and nutrient coverage. Mero handles this by reusing structure but varying the meals.

What if I miss a planned meal mid-week?

Track it honestly and continue on plan. Don’t try to make up the missed calories later in the day — that usually distorts the next day too. The weekly total is what matters.

How do I handle a deload or low-activity week?

Drop carbs and total calories proportionally. Protein stays the same. The shape of the week looks similar — just smaller volume on the high-output days.

Can the plan handle a meal out?

Yes. Slot the meal out into the plan in advance, estimate its macros, and adjust the surrounding meals if needed. Plan the deviation in — don’t pretend it didn’t happen and then improvise.

More general questions? See the main FAQ on the Mero homepage.

Join the waitlist

Stop rebuilding the spreadsheet.

One email gets you first-batch access the day Mero opens, plus the first word on pricing and launch timing. No drip. No noise.

No spam. No drip campaign theater. Unsubscribe in one click.