Sweatr
All articles
Fueling Strategy9 min read25 July 2026

How to Fuel Back-to-Back Training Days — The Glycogen Debt Most Runners Ignore

Your Saturday long run empties the tank. Here's how to refuel so Sunday's session doesn't wreck your week.

How to Fuel Back-to-Back Training Days — The Glycogen Debt Most Runners Ignore

In Summary

  • A single long run can drain 80% of your muscle glycogen — and it takes 24–48 hours of intentional eating to fully restore it.
  • Most runners under-fuel between sessions, not during them. The damage compounds across days.
  • Your wearable recovery metrics (HRV, Body Battery) drop faster when glycogen is depleted — that's a nutrition signal, not just a fatigue signal.
  • Sweatr tracks your cumulative training load and adjusts fueling recommendations across days, not just within sessions.

You nailed Saturday's 20-miler. Fueled well, hit your pace, felt strong at the finish. Sunday morning you lace up for an easy recovery run and your legs feel like concrete. By Monday's tempo session, you're dragging through intervals you handled comfortably two weeks ago.

The problem isn't fitness. It's fuel.

Most fueling advice focuses on what to eat during a single session — how many gels per hour, how much fluid, when to take your first carbs. But the bigger threat to your training block isn't a bad fueling plan for one run. It's the cumulative glycogen debt that builds across consecutive training days when you don't eat enough between sessions.

If you're training for a fall marathon, a late-season triathlon, or any event that demands back-to-back hard days, this is the gap that will quietly erode your performance.

What Glycogen Debt Actually Looks Like

Your muscles store roughly 400–500 grams of glycogen. A 90-minute long run at marathon pace can burn through 300–400 grams of that. A hard tempo session the next day draws from the same tank.

Here's the maths most runners miss: full glycogen restoration takes 24 to 48 hours of carbohydrate-rich eating. Not just a recovery shake and a normal dinner. Intentional, sustained carbohydrate intake across multiple meals.

If you finish your Saturday long run, eat a normal dinner, sleep, and head out for Sunday's session, you're starting with a tank that's maybe 60% full. After Sunday's run, you're down to 30–40%. By Monday, you're training on fumes — and your body knows it even if your brain doesn't.

The signs are subtle at first:

  • Pace feels harder than it should at the same heart rate
  • You can't hit the top end of your intervals
  • Your perceived effort is higher than your watch says it should be
  • You feel flat, heavy, or mentally foggy during sessions that should be moderate

These aren't signs of overtraining. They're signs of under-fueling. And the distinction matters, because the fix for overtraining is rest, while the fix for under-fueling is food.

Why Most Runners Get This Wrong

Three patterns create the glycogen debt trap:

1. The "I'll eat normally" approach

After a long run, most runners eat a recovery meal and then revert to their standard diet. But a standard diet delivers 200–300 grams of carbohydrate per day, and you need 400–600 grams to fully restore depleted glycogen in 24 hours. "Eating normally" guarantees you'll start the next day under-fueled.

2. The calorie-fear feedback loop

Some runners — particularly those watching their weight during a training block — consciously or unconsciously restrict calories after big sessions. The logic feels sound: "I burned 1,200 calories on my long run, so I have a buffer." But that buffer is exactly the fuel your muscles need to recover. Spending it on a deficit means your next session pays the price.

3. The single-session mindset

Most fueling guidance treats each workout as an isolated event. Fuel this run. Recover from this run. Repeat. But your body doesn't reset overnight. Glycogen restoration, muscle repair, and hormonal recovery all operate on timelines that span multiple days. Your Tuesday track session is shaped by what you ate — or didn't eat — on Sunday afternoon.

The 24-Hour Refuel Protocol

When you have back-to-back training days, the window between sessions is your most important fueling opportunity. Here's how to approach it.

The first 30 minutes: the rapid-refuel window

Immediately after your long run or hard session, your muscles are primed to absorb glycogen at roughly twice the normal rate. This window lasts about 30 minutes and it's the single highest-leverage nutrition moment in your training day.

Target: 1–1.2 grams of carbohydrate per kilogram of body weight, plus 20–30 grams of protein. For a 70 kg runner, that's 70–84 grams of carbs — roughly equivalent to a large bowl of rice with chicken, or a recovery shake plus a banana and toast.

Don't wait until you "feel hungry." The post-exercise appetite suppression that many runners experience is hormonal, not informational. Your muscles need fuel whether your stomach is asking for it or not.

The next 4–6 hours: sustained carbohydrate loading

After the initial window, shift to steady carbohydrate-rich meals every 2–3 hours. Each meal should contain 1–1.5 grams of carbs per kilogram of body weight.

Good options:

  • Pasta with a protein source and vegetables
  • Rice bowls with beans, sweet potato, or lentils
  • Oatmeal with fruit and honey
  • Sandwiches on thick bread with lean protein

The goal isn't one large meal — it's sustained intake across the day. Your gut can only absorb so much at once, so spreading it out is both more comfortable and more effective.

Before bed: top off the tank

A carb-rich snack before sleep keeps glycogen restoration going overnight. A bowl of cereal, toast with jam, or a banana with yoghurt and granola all work well. This is the meal most runners skip — and it's the one that makes the biggest difference to how you feel the next morning.

Morning of day 2: pre-session primer

Two to three hours before your next session, eat a carbohydrate-focused breakfast: 100–150 grams of carbs, low in fibre and fat so it digests quickly. Oatmeal with honey, white toast with jam, or a bagel with banana are all reliable choices.

If you followed the protocol above, you'll start day 2 with glycogen stores at 80–90% instead of the 50–60% that "eating normally" delivers. The difference in how you feel will be immediate and obvious.

What Your Watch Is Telling You (That You Might Be Misreading)

Here's something most runners don't realise: your wearable recovery metrics are partly reflecting your glycogen status, not just mechanical fatigue.

When your Garmin Body Battery is low, your HRV is suppressed, or your Apple Watch recovery score is poor, part of that signal is metabolic. Depleted glycogen triggers a stress response — elevated cortisol, suppressed parasympathetic activity, and impaired sleep quality. Your watch picks up these signals and tells you that you're "not recovered."

But the fix isn't always more rest. Sometimes the fix is more carbohydrates.

If your HRV drops sharply the morning after a long run and stays suppressed into the next day, ask yourself: did I actually eat enough to refuel, or did I just eat "normally"?

This is where the gap in most wearable platforms shows up. Your Garmin can tell you your Body Battery is at 20. Garmin Connect+ can even show you what you ate yesterday. But neither connects those two data points to tell you: "Your glycogen is likely depleted — eat 150 more grams of carbs today before tomorrow's session."

Sweatr bridges that gap. It tracks your cumulative training load across days, factors in your body weight and sweat data, and adjusts your fueling recommendations not just for the session ahead but for the recovery window behind you. When your wearable data shows suppressed recovery after a big day, Sweatr tells you exactly how much to eat — and when — to restore the tank before your next session.

A Sample Back-to-Back Fueling Day

Here's what a refuel day looks like for a 70 kg runner after a 2-hour Saturday long run, with a 60-minute tempo planned for Sunday morning.

| Time | What to eat | Carbs (g) | |------|-------------|-----------| | Immediately post-run (11:00 AM) | Recovery shake + banana + white toast with honey | 80 | | Lunch (1:30 PM) | Large pasta bowl with chicken and roasted veg | 100 | | Afternoon snack (4:00 PM) | Rice cakes with jam + orange juice | 60 | | Dinner (7:00 PM) | Rice with salmon, sweet potato, and greens | 90 | | Before bed (9:30 PM) | Bowl of cereal with milk + banana | 60 | | Sunday pre-run breakfast (7:00 AM) | Porridge with honey, white toast with jam | 120 |

Total carbohydrate intake between sessions: ~510 grams

That might feel like a lot if you're used to eating 200–300 grams per day. But this is what your body needs to fully restore glycogen and start Sunday's session ready to perform. This isn't overeating — it's matching your intake to your output.

The Compound Effect Across a Training Block

The glycogen debt doesn't just affect one weekend. It compounds across weeks.

If you consistently start your second training day 30–40% glycogen-depleted, your body adapts — but not in the way you want. You'll see:

  • A gradual decline in your ability to hit top-end speeds
  • Increased injury risk as fatigued muscles compensate with altered mechanics
  • Mood and motivation drops that feel like burnout but are actually metabolic
  • Worsening sleep quality as cortisol stays elevated from chronic under-fueling

Athletes who plateau in weeks 8–12 of a marathon training plan almost always have a fueling problem, not a fitness problem. Their training stimulus is correct. Their recovery nutrition isn't keeping up.

The fix is simple, but it requires intention. You have to eat more carbohydrates between hard sessions than feels natural. You have to treat the refuel window as seriously as you treat the session itself. And you have to track whether your intake is actually matching your expenditure — not just guess.

How Sweatr Makes This Automatic

Tracking cumulative fueling across days is exactly the kind of thing that's easy to understand and hard to do consistently. You know you should eat more after a long run. But how much more? And how do you adjust when your training load changes week to week?

Sweatr calculates your post-session carbohydrate targets based on your actual training data — session duration, intensity, heart rate, and estimated glycogen expenditure from your Apple Watch or Garmin. It doesn't give you a generic "eat more carbs" recommendation. It tells you: "After today's 2:05 long run at 145 bpm average, eat 480–530 grams of carbs before tomorrow's tempo to start at 85%+ glycogen."

When your wearable recovery data suggests you're under-fueled, Sweatr flags it and adjusts your next-day recommendation upward. It's the recovery layer your watch is missing.

Your training plan tells you when to run. Sweatr tells you when — and how much — to eat between those runs. That's the difference between a training block that builds on itself and one that slowly digs you into a hole.

Download Sweatr free and connect your Apple Watch or Garmin to see your personalised refuel targets after every session.