Special Diets and Fitness

How to fuel training without tracking every meal

August 16, 20266 min read
3D clay-style illustration of a weekly planner beside a plate of chicken, rice and vegetables with a protein figure shown

Logging tells you the week went badly after it already has. Deciding 4 things once a week is what actually keeps fuelling consistent.

The failure mode for people who train regularly is almost never a miscalculated macro split. It is an empty fridge on the evening of the hardest session of the week, followed by whatever can be ordered in 30 minutes.

That is a logistics problem, and logging does not solve logistics. This article sets out a structural approach: 4 decisions made once a week that hold up without a food diary.

What does fuelling actually require?

Less precision than the internet suggests, and more consistency. For most people training 4 to 6 times a week and not competing, 3 things matter: enough protein spread through the day, enough carbohydrate around hard sessions, and eating at all after training.

Precision beyond that has diminishing returns compared with simply hitting those 3 most days. A week where you ate well 6 days out of 7 without measuring anything beats a week measured to the gram where 2 dinners were a bag of crisps.

So the objective is not accuracy, it is reliability. That reframing is what makes the food side manageable without a diary.

How do you set a protein floor?

Pick a per-meal minimum rather than a daily total. A daily total requires tracking to know where you are; a per-meal floor is a property of the recipe, so it is decided when you plan rather than measured as you go.

Around 30 to 40 g per main meal works for most people training regularly. The useful part is knowing what that looks like in ingredients, so you can check a recipe at a glance.

IngredientPortionProtein, approximate
Chicken breast150 g raw34 g
Chicken thigh, boneless150 g raw28 g
Salmon fillet150 g31 g
Lean beef mince, 5% fat150 g raw31 g
Greek yoghurt, 0%200 g20 g
Eggs3 large19 g
Firm tofu200 g28 g
Cooked lentils250 g22 g
Cottage cheese200 g24 g
Figures are approximate and vary by brand and cut. Enough to check a recipe, not enough to audit a competition diet.

Read a recipe against that table once and you can classify it in about 5 seconds. Recipes that clear the floor go in the rotation; recipes that fall short get a side of yoghurt or an extra egg rather than being rejected. High-protein recipes lists options with the numbers already stated.

Which days should you plan first?

The hard ones. This is the single highest-leverage change available, and most people plan in the wrong order, filling the week evenly and letting the difficult nights take what is left.

  1. 1Mark the 2 hardest sessions of the week.
  2. 2Assign the fastest recipes you own to those evenings, 20 minutes maximum.
  3. 3Make sure something for those nights is already cooked or needs 1 pan.
  4. 4Fill the easier nights afterwards with anything, including the longer recipes.
  5. 5Leave 2 nights empty for leftovers, changed plans and whatever needs using.

A 45-minute recipe after a long run gets replaced by a takeaway, every time, and no amount of intention changes that. Matching cooking effort inversely to training effort is how a plan survives, which post-workout meals covers for the immediate window.

Why not eat back calories burned?

Because the number is soft and the behaviour it produces is not. Estimated expenditure varies with the method: GPS pace, a heart-rate strap and a power meter can give noticeably different figures for the same session.

Eating precisely against an imprecise number produces a week that swings without anyone understanding why. The more robust approach is to fix the food pattern and let training volume vary around it: same protein floor, same number of cooked dinners, same single shop, through a heavy week and a taper.

That is less satisfying than matching intake to output daily and it survives a real training block considerably better. Recipe app vs calorie tracker covers the wider version of the same argument.

What about carbohydrate around sessions?

Simpler than protein, and usually overcomplicated. For most people training once a day, the practical rule is that the meal before and the meal after a hard session both contain a proper portion of carbohydrate, and the rest of the week looks after itself.

A proper portion means something recognisable rather than a calculation: a large serving of rice, pasta, potatoes, couscous or bread, roughly 60 to 100 g dry weight of a grain per person. Cutting carbohydrate on training days is where people quietly ruin sessions while blaming fatigue on everything else.

  • Before a session: something easy to digest 2 to 3 hours ahead, or a small carbohydrate snack 30 to 60 minutes ahead.
  • After a session: carbohydrate plus 30 to 45 g of protein, ideally within a couple of hours.
  • On easy or rest days, nothing needs changing. Consistency beats cycling.
  • For endurance sessions past about 90 minutes, eating during them matters more than either side.

The planning consequence is small but real: recipes for hard days should include the grain rather than being a protein and a salad. That is a decision made on Sunday, not a macro calculation made at 8pm.

What does the weekly routine look like?

About 20 minutes of planning and one shop. The point is that all the deciding happens once, while you are not tired and not hungry.

  • Sunday, 10 minutes. Pick 4 dinners from recipes you already own, hard days first.
  • Sunday, 5 minutes. Generate one shopping list, merged and in shop order.
  • Sunday, 60 to 90 minutes. Cook 2 things in bulk: a tray of protein and a pan of grains.
  • Midweek, 0 minutes. Assemble rather than cook on the 2 hardest nights.
  • Anytime. Use the open nights for leftovers or whatever is about to spoil.

One practical note on portions: cook for more people than are eating. A tray of chicken thighs for 6 when 2 of you are eating covers 2 further dinners with no additional work, and it is the same oven, the same washing up and the same 10 minutes of preparation. Scaling up is nearly free, which is why the arithmetic of batch cooking favours the largest tray your oven will take.

Bulk cooking 2 components rather than 5 complete meals is what stops the food becoming repetitive: the same chicken and rice becomes 3 different dinners with 3 different sauces. High-protein meal prep covers the technique, and batch cook for the week covers the timings.

If you want a single test of whether this is working, look at the 2 hardest evenings of last week and ask what you ate. If the answer is a meal you had planned, the system is holding. If it was ordered, the problem is upstream of nutrition and no adjustment to a macro target will reach it.

On apps, ReciBites vs Strava covers the training side against the food side, and ReciBites vs MyFitnessPal covers logging if you decide you want it after all.

Protein floor
A minimum protein target per meal rather than per day, checked when planning so it needs no tracking.
Component cooking
Bulk cooking 2 or 3 elements, such as a protein and a grain, then combining them differently across the week.
Eating back calories
Adding estimated exercise expenditure to your intake target. Unreliable, because the estimate varies by measurement method.

Frequently asked questions

+How much protein do I need per meal?

Around 30 to 40 g per main meal works for most people training regularly. That is roughly 150 g of chicken, 200 g of Greek yoghurt or 200 g of firm tofu.

+Can I fuel training without tracking?

Yes. Set a per-meal protein floor, plan the hardest sessions first, cook 2 components in bulk and shop once. Consistency matters more than measurement.

+Should I eat back the calories my watch says I burned?

No. Those estimates vary by measurement method, and eating precisely against an imprecise number makes weeks swing for no visible reason.

+Which days should I plan first?

The 2 hardest training days. Assign your fastest recipes there, because a 45-minute recipe after a long session gets replaced by a takeaway.

+What should I eat after a session?

Roughly 30 to 45 g of protein with a similar amount of carbohydrate. Chicken with rice, salmon with couscous or yoghurt with oats all work inside 20 minutes.

+How do I stop meal prep becoming repetitive?

Cook components rather than complete meals. One tray of protein and one pan of grains becomes 3 different dinners with different sauces.

+How many dinners should I plan?

Four, with 2 nights left open. Leftovers, changed arrangements and one takeaway usually fill the rest, and a shorter plan survives the week.

+Do I need a fitness app and a recipe app?

They cover different halves. A training app measures sessions; a recipe app decides and shops for the food, which is usually the unmanaged side.

  • #high protein
  • #meal planning
  • #fitness
  • #meal prep