Your Training Load Is Telling You How Much to Eat — Here's How to Listen

Your Watch Knows More Than You Think

Open your Garmin Connect or Apple Watch fitness summary right now. Somewhere in there — maybe labelled Training Status, Training Load, or Training Readiness — is a number or a colour-coded bar that's trying to tell you something important.

Most athletes glance at it, nod, and move on. Maybe you've noticed it say "High" after a big training week, or "Overreaching" after back-to-back long runs in the summer heat. And then you did... nothing different. You ate the same meals, drank the same amount of water, and wondered why you felt wrecked by Thursday.

That number isn't just a fitness score. It's a signal about how much fuel your body needs — and ignoring it is one of the most common reasons endurance athletes under-fuel, under-hydrate, and hit a wall in training or on race day.

What Training Load Actually Measures

Training load is your watch's attempt to quantify total physiological stress. Not just how far you ran or how many hours you rode — but how hard those sessions were on your body.

Garmin calculates training load using heart rate data, workout duration, and intensity relative to your personal thresholds. It combines your most recent 7 days of training into an "acute load" and compares it against your 28-day average ("chronic load"). Apple Watch uses a similar approach through its Training Load feature, tracking workout effort scores over rolling 7-day and 28-day windows.

The resulting number — whether it's expressed as a score, a ratio, or a colour — reflects three things that directly affect your nutrition:

1. How many calories you've burned above baseline — higher training load means more energy expenditure
2. How much glycogen you've depleted — harder and longer sessions burn through stored carbs faster
3. How much your body needs to recover and rebuild — muscle repair, immune function, and adaptation all require fuel

When training load is high, your body isn't just tired. It's literally running on a caloric and carbohydrate deficit unless you've deliberately eaten more to match.

Why Generic Meal Plans Fail During Big Training Weeks

Most nutrition advice for runners and cyclists looks something like this: eat a balanced diet, get enough protein, have a carb-rich meal the night before a long run, and take a gel every 45 minutes during the effort.

That advice isn't wrong — it's just static. It doesn't change when your training changes.

Here's the reality of what happens in a typical marathon training block:

Week 6 — moderate training load: You run 55 kilometres across five sessions. Your daily energy expenditure above baseline is roughly 400–600 kcal. Your normal meals probably cover the difference without much thought.

Week 10 — high training load: You run 75 kilometres including a 32K long run and two tempo sessions. Your daily energy expenditure above baseline is 800–1,200 kcal. Your normal meals don't even come close. You're in a caloric deficit every day, and you might not realise it because you're not hungry — cortisol and training fatigue suppress appetite.

Week 14 — peak training load: Back-to-back high-volume weeks. Training load reads "Overreaching." Your body is burning through glycogen stores faster than you're replacing them. You feel sluggish, your easy pace feels hard, and your sleep is disrupted.

Most athletes blame the training. But the training is doing exactly what it's supposed to. The problem is the fueling didn't scale up with the load.

The Numbers: How Training Load Changes Your Carb Needs

Sports nutrition research gives us a framework for matching carbohydrate intake to training volume and intensity. Here's a simplified version based on current guidelines from the American College of Sports Medicine:

| Training Load Level | Daily Carbs (per kg body weight) | Example: 70 kg athlete | |---|---|---| | Light (easy/recovery days, low training load) | 3–5 g/kg | 210–350 g | | Moderate (steady training, moderate load) | 5–7 g/kg | 350–490 g | | High (big training weeks, tempo + long runs) | 6–10 g/kg | 420–700 g | | Very High (peak weeks, double sessions, heat) | 8–12 g/kg | 560–840 g |

Look at that range. A 70 kg runner could need anywhere from 210 to 840 grams of carbohydrates per day depending on their training load. That's a fourfold difference — and yet most athletes eat roughly the same thing every day.

The delta between a moderate and a high training load week could be 200–300 extra grams of carbohydrates per day. That's roughly four extra servings of rice, or three extra bowls of oatmeal, or six extra energy bars. Miss that consistently across a three-week peak training block and you're entering a compounding deficit that shows up as fatigue, poor recovery, compromised immunity, and eventually injury.

It's Not Just Carbs — Hydration Scales With Training Load Too

When training load rises, so does your fluid requirement. Higher training volume means more sweat lost across the week. Higher intensity sessions generate more metabolic heat, which increases sweat rate per hour. And if you're training through summer — when most fall marathon plans hit their peak blocks — the combination of load and heat is a double hit.

A light training week in cool weather might require 2–2.5 litres of total daily fluid. A high training load week in June heat could push that to 3.5–4.5 litres — not counting the fluid you drink during workouts themselves.

Your watch captures the data that drives this: session duration, intensity (via heart rate), environmental conditions (if your phone provides weather data), and even sleep quality, which affects recovery and fluid balance. But it never converts that data into "drink 500ml more today" or "add an extra electrolyte sachet to your afternoon water."

That conversion is the missing link.

How to Read Your Training Load for Fueling Decisions

You don't need a sports nutritionist to start using training load as a fueling signal. Here's a practical framework:

Step 1: Know Your Baseline

On a moderate training week (your typical steady-state week, not a peak or recovery week), track what you eat for three days. You don't need to weigh everything — rough portion estimates work. Note your total carbohydrate intake per day using a free app or food label reading. This is your baseline.

Step 2: Watch the Load Trend, Not the Daily Number

Training load is a rolling metric. Don't react to a single session — look at the 7-day trend. When your watch shows your weekly training load climbing (Garmin's "Productive" turning to "Straining," or Apple Watch's 7-day load exceeding your 28-day average), that's your cue to increase fueling.

Step 3: Add Carbs in Proportion to Load Increase

A rough rule of thumb:

• Training load up 10–20% from your baseline week → add 1–2 g/kg carbs per day (an extra 70–140 g for a 70 kg athlete)
• Training load up 20–40% → add 2–4 g/kg carbs per day
• Training load up 40%+ (peak week, overreaching territory) → you need professional-grade fueling attention — this is where an automated tool earns its keep

Step 4: Front-Load Carbs Around Training

When training load is high, timing matters more. Prioritise carbs in the 2–3 hours before your key session and within 30–60 minutes after. Your muscles are most receptive to glycogen replenishment in that post-workout window, and a high training load means you've dug a deeper glycogen hole.

Step 5: Don't Cut Back Too Fast in Recovery Weeks

When training load drops — taper weeks, recovery weeks, injury-forced rest — the instinct is to cut calories. Resist the urge. Your body is still repairing and adapting from the high-load block. Keep carbohydrate intake at moderate levels (5–7 g/kg) for at least 2–3 days into a recovery week before reducing.

Why Your Watch Can't Finish the Job

Your Garmin or Apple Watch is excellent at measuring training load. It's not designed to tell you what to do about it nutritionally. Garmin Connect+ added food logging in January 2026, but it's a calorie tracker — it tells you what you ate, not what you should eat based on today's training load. TrainingPeaks launched Fueling Insights, but it only works for cycling with power meter data, and it tells you what you burned, not what to consume.

The gap between seeing a training load number and knowing how to fuel for it is where most self-coached athletes struggle. You need something that reads your training data — the sessions, the intensity, the trend — and converts it into a personalised fueling plan that adjusts daily.

Sweatr does exactly this. It pulls your training load data from Garmin, Apple Watch, and Strava, combines it with your body metrics and sweat profile, and generates a daily fueling and hydration plan that scales with your training. When your load climbs during peak weeks, your plan adjusts. When you taper, it tapers with you. No spreadsheets, no guesswork, no calorie counting.

The Biggest Risk You're Not Seeing

Under-fueling doesn't announce itself the way a rolled ankle does. It builds quietly across weeks. You feel a bit flat. Easy runs feel harder than they should. You pick up a cold. Your sleep gets worse. You blame the training volume, or the heat, or stress at work.

Relative Energy Deficiency in Sport (RED-S) — the clinical term for chronic under-fueling relative to training demand — affects an estimated 22–58% of endurance athletes, depending on the study and the sport. It's not limited to underweight athletes or those with disordered eating. It hits everyday runners and cyclists who simply don't realise that their 70-kilometre week requires a fundamentally different eating pattern than their 45-kilometre week.

Your training load data is the early warning system. It tells you when your body's demand has outpaced your fuel supply. The question is whether you have something that translates that warning into action — or whether you'll keep ignoring the number on your wrist until it shows up as a DNF on race day.

Make the Number Work for You

Your watch has already done the hard work. It tracked every heartbeat, every minute, every session. It calculated the load. It even told you when you were overreaching.

What it didn't do was hand you a plate of food and say "eat this."

That's the gap Sweatr fills. Connect your Garmin, Apple Watch, or Strava account, enter your body metrics, and Sweatr converts your training load into a daily fueling and hydration plan — personalised to your data, adjusted for conditions, and mapped to real products you can buy.

Your watch tells you the score. Sweatr tells you what to do about it.