Three Morning Metrics That Tell You Whether Yesterday's Long Run Fueling Worked

You wake up the morning after a 20-miler. Your legs feel heavy, which you expected. But then you check your watch. Your HRV dropped 15 points. Your resting heart rate is 8 beats above baseline. Your Garmin Body Battery barely moved past 30 overnight.

Most runners see these numbers and think one thing: that was a hard session. And they move on.

But those three metrics are doing something more useful than confirming you ran far yesterday. They're grading your fueling. And most runners never make that connection.

The Morning-After Feedback Loop Nobody Uses

Your watch collects recovery data while you sleep. Garmin tracks Body Battery and HRV. Apple Watch tracks resting heart rate and respiratory rate. Both feed overnight data into recovery scores and readiness metrics.

The standard advice is to use these numbers to decide whether to train hard today. That's fine, but it's only half the value.

The other half: these metrics respond directly to how well you fueled and hydrated during and after yesterday's run. A long run where you nailed your carbohydrate intake and hydration produces a visibly different overnight recovery profile than one where you under-fueled or finished dehydrated.

The problem is nobody teaches you to read it that way. Your watch shows the data. Your running app shows the workout. Nothing connects the fueling you did during the run to the recovery numbers that showed up the next morning.

That gap is exactly where your most valuable training data lives.

Metric 1: Overnight HRV Change

Heart rate variability measures the variation in time between heartbeats. Higher HRV generally means your body is in a recovered, parasympathetic state. Lower HRV means your autonomic nervous system is still working to restore balance.

After a long run, your HRV will drop. That's normal. The question is how much it drops relative to your personal baseline and relative to comparable training sessions.

Here's what to look for: compare your morning-after HRV to the last three long runs of similar distance and intensity. If this morning's HRV is significantly lower than those, something was different. The run itself wasn't harder (similar distance, similar pace). So what changed?

Usually one of three things: you slept poorly (check your sleep data — if sleep was normal, rule this out), you're getting sick (if this is the case, you'll know within 24 hours), or your fueling was off.

Under-fueling during a long run forces your body to work harder during recovery. Depleted glycogen means your liver and muscles are pulling harder on available resources to restock. Dehydration means your cardiovascular system has to work harder to maintain blood volume overnight. Both suppress HRV.

When your HRV drops more than 15-20% below your 30-day morning average after a long run — and you slept normally — your fueling deserves a second look before you blame training load.

What to track: Your morning HRV reading (Garmin: check the HRV Status widget; Apple Watch: check the Health app's HRV overnight average). Write it down alongside what you ate and drank during yesterday's run. After four to six long runs, you'll see the pattern.

Metric 2: Morning Resting Heart Rate vs. Baseline

Resting heart rate is the simpler sibling of HRV, and in some ways more reliable for spotting fueling problems.

Your baseline resting heart rate is the number your watch shows on a typical recovery morning when you've slept well and aren't stressed. Most runners know their number: maybe it's 48, maybe it's 55, maybe it's 62. It doesn't matter what it is. What matters is how far above that number you wake up the morning after a long run.

A 3-5 beat elevation is normal after a genuinely hard long run. Your body did real work and it's recovering. Nothing to worry about.

A 6-10+ beat elevation, on a morning where you slept a normal amount and went to bed at a reasonable time, is your body telling you recovery is taking longer than expected. And one of the most common reasons recovery takes longer than training alone would predict is inadequate fueling — either during the run, in the recovery window after, or both.

Here's the mechanism: when you finish a long run in a glycogen-depleted state, your body releases more cortisol and norepinephrine to maintain blood glucose levels through the night. That sympathetic nervous system activity shows up directly as elevated resting heart rate. It's not dangerous. But it's a signal.

Dehydration compounds this. If you finished your run 2-3% dehydrated (which is surprisingly common in cool autumn weather, when you don't feel as thirsty), your body has to maintain cardiac output with less blood volume. Heart rate goes up to compensate, and it stays up until you've fully rehydrated — which often takes until the following afternoon.

What to track: Your morning resting heart rate (check your watch's overnight average, not the number when you first wake up). Compare it to your 14-day resting average. If the gap is consistently larger after long runs than after comparable-intensity shorter runs, your fueling is the likely variable.

Metric 3: Recovery Score or Body Battery Recharge

Garmin's Body Battery and Apple Watch's readiness or recovery indicators synthesise multiple inputs — HRV, resting heart rate, sleep quality, stress — into a single number that represents how recovered you are.

These composite scores are blunt instruments. They can't tell you why your recovery is slower. But they're excellent at telling you that it is.

The protocol is simple: after each long run, note where your Body Battery or recovery score sits when you wake up the next morning. Then compare it across long runs of similar length over several weeks.

If your Body Battery consistently rebounds to 60-70+ after 18-mile long runs, and then one week it only hits 40 after the same distance, something changed. If you also noted that you skipped your mid-run gel, reduced your fluid intake because the weather was cool, or forgot your post-run recovery meal, you have your answer.

The value here isn't in any single reading. It's in the trend. Four data points from four long runs, with fueling notes attached, gives you more actionable insight about your personal nutrition needs than any generic blog post ever could.

What to track: Morning recovery score or Body Battery alongside a simple fueling log: total carbs consumed during the run, total fluid consumed, and what you ate within 60 minutes of finishing. The correlation will reveal itself within a month of consistent tracking.

How to Build a Three-Metric Fueling Feedback Loop

Here's the protocol. It takes 60 seconds each morning after a long run.

Step 1: Check your watch when you wake up. Note three numbers: morning HRV, resting heart rate, and recovery score (Body Battery, readiness, or equivalent).

Step 2: Write them down next to yesterday's long run details. You need: run distance, run duration, total carbs consumed during the run (approximate grams), total fluid consumed (approximate millilitres or ounces), and what you ate in the 60 minutes post-run.

Step 3: After your next long run, repeat. And the one after that.

Step 4: After four to six long runs, compare. Look for the pattern. On mornings where recovery metrics were strong, what did your fueling look like? On mornings where they were suppressed, what was different?

You'll almost certainly find that the runs with the best recovery profiles are the ones where you hit your carbohydrate targets during the run, stayed on top of hydration, and ate a proper recovery meal within the hour. And the runs with the worst profiles are the ones where you skipped a gel, ran out of water, or got home and collapsed on the couch before eating.

This isn't a theory. It's your own data telling you what works for your body.

Why This Matters More Than Any Fueling Calculator

Generic fueling advice says take 60-90 grams of carbs per hour. Drink 400-800ml of fluid per hour. Take sodium.

Those ranges are so wide they're almost useless for an individual. 60g per hour might be perfect for you. Or it might be 40% below what you need. You won't know from reading a table.

But your own recovery data narrows the range fast. If you fueled at 60g per hour and your recovery metrics looked great, that's your floor. Try 50g next time and see if recovery suffers. If it does, you know your minimum. Try 70g and see if recovery improves further. If it doesn't, you've found your ceiling.

This is personalised nutrition science, built from data you're already collecting. No expensive sweat test. No lab visit. Just your watch, a notes app, and four weeks of attention.

The Catch: Doing This Manually Is Tedious

You probably noticed the gap in this protocol. You have to manually connect your fueling notes to your recovery data, across multiple sessions, and spot the patterns yourself. Your watch doesn't do this. Garmin Connect doesn't do this. Apple Health doesn't do this. None of them connect "what you ate during a run" to "how your body recovered overnight."

Sweatr does. It pulls your recovery metrics from your Garmin, Apple Watch, or Strava, overlays them with your fueling data, and shows you the relationship across your entire training history. Not as a spreadsheet you have to interpret, but as a clear signal: your fueling worked, or it didn't, and here's what to adjust.

It's the feedback loop your watch already collects the data for — and the intelligence layer that finally makes that data useful.

Build Your Feedback Loop Starting This Week

Your next long run is probably this weekend. When you wake up Sunday morning (or Monday morning, depending on when you run), check your three numbers. Write them down. Note what you ate and drank during the run.

Do it again next week. And the week after.

By the time your next race arrives, you won't be guessing at your fueling plan. You'll be using your own recovery data to build one that actually works for your body.

Or let Sweatr do the tracking for you. Connect your watch, log your fueling, and let the app show you what your data has been trying to tell you all along. Download Sweatr free and start building your personal fueling profile from the data your watch already collects.