Your Garmin Says You're Ready to Race — But Is Your Nutrition Ready Too?

You've done the training. Your Garmin watch confirms it every morning. Training Status: Productive. VO2 max: trending up. Race Predictor: 3:45. Body Battery: full. Everything green.

Then mile 18 arrives and your stomach revolts, your legs seize, and you walk the last 8 miles wondering what went wrong.

The answer is almost always the same: your body was ready. Your nutrition wasn't.

What "Race Ready" Actually Means on Your Watch

Garmin's race readiness ecosystem — Training Status, Training Load, VO2 max estimate, Race Predictor, and Body Battery — measures one thing well: cardiovascular and musculoskeletal preparedness. It tracks whether you've trained enough, recovered enough, and built enough aerobic capacity to sustain your goal pace.

What it doesn't track: whether your gut can handle 60 grams of carbs per hour at race pace. Whether you've tested your gel brand at effort. Whether your hydration plan accounts for the 18°C race-day forecast that's 12 degrees cooler than your summer training. Whether your glycogen stores are actually topped off from carb loading or whether you cut calories during taper because your watch showed lower training load.

These are the things that decide whether your Race Predictor's 3:45 becomes a 3:48 finish or a 4:20 death march.

Training Status: "Productive" Doesn't Mean "Fueled"

Your Training Status reflects the relationship between your training load and your fitness. "Productive" means your load is building fitness without overreaching. That's valuable information. But it assumes you're eating and drinking adequately to support that load.

Here's the problem: most runners don't adjust fueling as training load changes. In your peak weeks — 60–70 km, back-to-back long runs, intensity sessions — your daily carb needs can reach 6–8 grams per kilogram of body weight. For a 70 kg runner, that's 420–560 grams of carbs daily. Most runners eat closer to 250–300 grams without realising the deficit.

Your watch still says "Productive" because it's measuring fitness adaptation. Meanwhile, you're accumulating glycogen debt that compounds week over week. By race day, you arrive depleted without knowing it.

What to check: Look at your training load trend over the past 4 weeks. If your weekly volume peaked above 60 km, ask yourself: did your eating match? If you've been eating the same meals regardless of training load, you've probably been running a carb deficit in your heaviest weeks.

Race Predictor: The Number That Assumes Perfect Fueling

Your Garmin Race Predictor estimates your marathon finish time based on VO2 max, training history, and recent performance. It's a useful benchmark. It's also built on an assumption it never states: that your fueling will be adequate throughout the race.

A 3:45 predicted marathon means sustaining roughly 5:20/km for 42.2 km. At that pace and a typical body weight, you'll oxidise 60–70 grams of carbohydrates per hour. Over 3 hours 45 minutes, that's 225–260 grams of carbs burned from a mix of muscle glycogen, liver glycogen, and whatever you take in.

Your body stores roughly 400–500 grams of glycogen when fully loaded. Do the maths: if you're burning 260 grams over 3:45 and you don't eat, you'll deplete your stores somewhere around 2:45–3:00 into the race. That's mile 20. That's the wall.

The Race Predictor doesn't know if you'll actually consume 45–60 grams of carbs per hour. It doesn't know if your gut can absorb that amount at race pace. It doesn't know if you'll skip an aid station because you feel fine at mile 10.

What to check: Take your predicted time and calculate your total carb burn (body weight in kg × 0.8–1.0g per minute of running). Compare that against your glycogen stores plus planned intake. If the numbers don't balance, the prediction is fiction.

Body Battery: Full Tank, Empty Cupboard

Body Battery measures your body's energy reserves based on heart rate variability, stress, and activity. A full Body Battery on race morning feels reassuring. It means you've recovered, slept well, and aren't carrying fatigue.

But Body Battery reflects autonomic nervous system recovery, not glycogen status. You can have a full Body Battery and depleted muscle glycogen. You can have a full Body Battery and a dehydrated body. These are different systems.

The confusion is understandable. When Garmin shows a battery icon at 95 out of 100, it feels like your entire body is charged up. In reality, your cardiovascular system is rested. Your muscles might be sitting on 300 grams of glycogen instead of 500 because you cut carbs during taper.

What to check: In the 48 hours before your race, focus on what Body Battery can't see. Did you consume 8–10 grams of carbs per kilogram of body weight yesterday? Did you stay on top of fluids, aiming for pale yellow urine? Did you add 1,000–1,500 mg of extra sodium in the 24 hours before the race? These are the fuel gauges Body Battery doesn't have.

The Metric Garmin Doesn't Track: Your Gut's Race Readiness

Here's the single biggest gap in wearable race readiness: no watch measures whether your gut can absorb fuel at race intensity.

Gut training — the process of systematically increasing carbohydrate intake during training runs to improve intestinal absorption — takes 4–8 weeks of consistent practice. Untrained guts absorb 30–45 grams of carbs per hour. Trained guts handle 60–90 grams per hour. That difference is the difference between hitting the wall and cruising through mile 22.

Your Garmin doesn't know whether you've gut-trained. It doesn't know whether you've tested your chosen gel at marathon pace. It doesn't know whether you've practised drinking at aid station intervals. These are binary readiness factors: either you've done them or you haven't, and no metric compensates for skipping them.

If you're 3 weeks from your fall marathon and haven't tested race nutrition during a long run, your cardiovascular fitness is irrelevant until you address this.

What to check: Count the number of long runs in the past 8 weeks where you practised your full race-day nutrition plan — gels, drink mix, timing, everything. If the answer is fewer than three, your nutrition isn't race-ready regardless of what your watch says.

VO2 Max: Fit Enough to Run, But Fit Enough to Absorb?

Your VO2 max estimate tells you about your aerobic ceiling. A higher VO2 max means you can sustain a faster pace before crossing into anaerobic territory. But VO2 max interacts with nutrition in a way most runners miss.

At lower intensities (60–70% of VO2 max), your body burns a higher percentage of fat for fuel, sparing glycogen. At higher intensities (80%+ of VO2 max), you shift to burning almost entirely carbohydrate. This means your pacing strategy directly determines your fueling needs.

A runner with a VO2 max of 45 running a 4:30 marathon is likely working at 70–75% of their max — a moderate intensity that burns a mix of fat and carbs. The same runner's friend with a VO2 max of 55 running a 3:30 marathon is working at 80%+ — burning carbs at nearly double the rate.

Your watch knows your VO2 max. It does not connect that number to your carb burn rate, your fueling plan, or your gel timing. That connection is the missing link between fitness data and race-day nutrition.

What to check: Estimate what percentage of your VO2 max you'll be running at during your goal marathon. If you're above 75%, you're burning carbs fast and need to be at the upper end of the 60–90 grams per hour intake range. If you're below 70%, you have more metabolic flexibility and can be more conservative.

How to Bridge the Readiness Gap

Your watch has given you half the picture. Here's how to complete it in the weeks before your fall race.

This week: Do a fueling audit. List every long run from the past 8 weeks. For each one, note: what you ate, how much, when, and how your gut responded. If you don't have this data, your next long run (even a shorter one during taper) becomes a nutrition dress rehearsal.

Two weeks out: Lock in your race-day products. Choose one gel brand and one drink mix. Know the carb content per serving. Calculate how many you'll carry and when you'll take each one. Write it on your hand or tape it to your bottle if needed.

Race week: Focus on what your watch doesn't show. Carb load for 2–3 days (8–10g per kg body weight). Hydrate consistently (aim for pale yellow urine). Add extra sodium (1,000–1,500 mg on top of normal intake). Track these manually — your watch won't remind you.

Race morning: Eat 3–4 hours before the start. Aim for 1–2 grams of carbs per kilogram of body weight. Sip fluids until 30 minutes before the gun. This is the fueling equivalent of a fully charged Body Battery.

Your Watch Is Half the Answer

Garmin, Apple Watch, and every other wearable have made runners more data-literate than any previous generation. You know your VO2 max, your training load, your recovery status, and your predicted race time. That's genuinely powerful.

But fitness readiness is only half of race readiness. The other half — glycogen status, gut training, hydration planning, sodium targets, and fueling execution — lives outside your watch's sensors.

Sweatr bridges that gap. It takes your Garmin and Apple Watch training data — the sessions, the heart rate, the training load trends — and connects them to a personalised hydration and fueling plan. Not generic advice. Not a calorie tracker. A specific plan that tells you what to drink, when to eat, and how much of each — built from your data, for your race.

Your watch knows you're fit enough. Sweatr makes sure you're fueled enough.