Sweatr
All articles
Race Prep9 min read10 August 2026

3 Long Runs Left Before Taper: A Week-by-Week Fueling Test Plan

Use your final 3 long runs before taper to lock in a race-day nutrition plan that actually works.

3 Long Runs Left Before Taper: A Week-by-Week Fueling Test Plan

In Summary

  • Your last 3 long runs are dress rehearsals, not just fitness builders.
  • Test one fueling variable per run: timing, quantity, then the full race-day protocol.
  • Record everything — what you ate, when, and how your gut responded.
  • Sweatr tracks each long run and builds your race-day plan from the data.

Your fall race is 6 to 8 weeks away. The fitness is mostly banked. But here's the part most athletes get wrong: they treat every long run the same, grab whatever gel is in the kitchen drawer, and hope race day works itself out.

It won't. Not reliably.

You have roughly three meaningful long runs left before your taper begins. Each one is an opportunity to test, refine, and lock in a race-day nutrition plan built on real data — not guesswork. Here's exactly what to do with each of them.

Why the Final 3 Long Runs Matter More Than the First 10

Early in a training block, long runs are about building aerobic endurance. You're training your cardiovascular system, your musculoskeletal resilience, and your mental toughness. Nutrition during those runs is secondary — you're just trying to get through them.

But in the final 6 to 8 weeks, the script flips. Your fitness is largely set. What separates a good race from a bad one at this point is execution — and execution is almost entirely about fueling and hydration.

A study of over 71,000 marathon runners found that 46.4% of all cramping incidents occurred in the final quarter of the race. The primary driver wasn't dehydration or electrolyte deficiency — it was neuromuscular fatigue compounded by energy depletion. In other words, runners who underfuelled early paid for it late.

Your last three long runs are the only chance to rehearse the plan that prevents this.

The One Rule: Test One Variable at a Time

The biggest mistake athletes make is changing everything at once. New gel brand, different timing, more fluid, extra sodium — all on the same run. When it goes wrong (or right), you have no idea which variable mattered.

Each of the three runs below tests one thing. Keep everything else constant.

Long Run 1: Timing and Tolerance (8 Weeks Out)

What you're testing: When to start fueling and how frequently your gut can handle intake.

The protocol:

Start your fueling earlier than you think you should — at 25 to 30 minutes into the run, not 45 or 60. Research consistently shows that early fueling maintains blood glucose more effectively than playing catch-up later.

Set a repeating timer on your watch. Take your first gel or fuel at 25 minutes, then every 20 to 25 minutes after that.

Use whatever products you already have. This run isn't about testing brands — it's about finding the rhythm.

What to record:

  • Exactly when you took each gel or fuel
  • How your stomach felt on a simple 1 to 5 scale (1 is fine, 5 is nauseous)
  • Your pace before and after each intake
  • How much fluid you consumed alongside each gel
  • The temperature and humidity during the run

What to look for:

If your gut handles fueling every 20 minutes without distress, you've found your floor. If you feel nauseous, back off to every 25 or 30 minutes and note the difference.

The goal isn't maximum intake — it's finding the highest frequency your gut tolerates without complaint.

Long Run 2: Quantity and Carb Type (6 Weeks Out)

What you're testing: How many grams of carbohydrate per hour you can absorb, and whether glucose-fructose blends work better for you than glucose alone.

The protocol:

Now that you know your timing from Long Run 1, use the same interval. But change the quantity. If you were taking one standard 22g gel every 25 minutes on the last run, try stepping up to 30 to 35g per serving — either by switching to a higher-carb gel or by adding a chew or a sip of drink mix between gels.

Your target range for a marathon is 60 to 90 grams of carbohydrate per hour. For a half marathon, 30 to 60g is usually enough. But the right number for you depends on your body weight, your pace, and your gut.

If you've been using single-source glucose gels, try a dual-transport gel (glucose plus fructose) on this run. Research shows that dual-transport carbohydrates can increase absorption rates beyond 60g per hour because they use two separate intestinal pathways.

What to record:

  • The exact product and quantity at each intake
  • Total grams of carbohydrate per hour (calculate this after the run)
  • Gut comfort score at each intake and at the end
  • Whether you noticed any energy fade in the final third of the run
  • Heart rate data — look for drift that might signal under-fueling or dehydration

What to look for:

Your personal carb ceiling is the highest hourly intake that doesn't cause GI distress. Most recreational marathon runners land between 60g and 80g per hour. If you hit 90g without issues, you've found an advantage. If 60g is your ceiling, that's your ceiling — and it's valuable data.

Long Run 3: The Full Dress Rehearsal (4 Weeks Out)

What you're testing: Your complete race-day nutrition protocol — breakfast, pre-run hydration, in-run fueling, and fluid intake — executed exactly as you plan to do it on race day.

The protocol:

Wake up at the time you'd wake up on race morning. Eat the breakfast you plan to eat — the same foods, the same quantities, at the same time before the run.

Pre-hydrate the same way: 500ml of fluid with electrolytes, finished 90 minutes before you start.

During the run, execute your refined plan from Long Runs 1 and 2. Same timing. Same products. Same quantities. Same fluid strategy.

If your race has specific aid station products (many big marathons publish this in advance), use those on this run. Race day is not the time to discover that the on-course gel brand doesn't agree with you.

What to record:

  • Your full pre-run routine, including what you ate and when
  • Every in-run intake with timestamps
  • Your total fluid consumption and whether you felt thirsty, well-hydrated, or bloated
  • Energy levels at 10-mile increments (or equivalent for your race distance)
  • Any GI issues — even mild ones
  • Post-run weight loss (weigh yourself before and after, nude) to estimate sweat rate

What to look for:

This run should feel boring. No surprises, no experiments, no improvisation. If everything goes smoothly, you've found your plan. If something goes wrong — a stomach issue at mile 16, an energy crash at mile 18, excessive thirst — you've identified the weakness and still have time to adjust before race day.

The Mistake That Wastes All Three Runs

You did the runs. You tested the plan. And then you didn't write any of it down.

Runners routinely forget the details within 48 hours. The specific gel timing, the exact fluid amounts, the gut comfort at mile 14 — it all blurs into "it went fine" or "my stomach was a bit off."

After each long run, spend five minutes recording:

  • What you consumed, when, and how much
  • How your gut responded
  • How your energy held up in the final third
  • The weather conditions (temperature, humidity, sun)
  • Your average heart rate and pace

This data is what transforms three training runs into a race-day nutrition plan.

How Your Watch Data Makes This Easier

Your Garmin or Apple Watch already captures heart rate, pace, temperature exposure, and workout duration for every long run. That data tells you more about your fueling needs than you might realise.

Heart rate drift in the final third of a long run — where your heart rate climbs even as your pace stays constant — is one of the strongest signals of dehydration or energy depletion. If you see it on Long Run 1 but not Long Run 3, your revised fueling plan is working.

Your watch's estimated calorie burn (even though the number isn't perfectly accurate) gives you a ballpark for total energy expenditure. Compare that to what you actually consumed. If you took in 200 calories over 2 hours but burned 1,400, you were massively under-fueled — and your race-day plan needs to reflect that.

The challenge is connecting these data points into a coherent plan. Your watch shows you the metrics but doesn't tell you what to eat or drink based on them.

From 3 Test Runs to a Locked-In Race Plan

Here's what your final plan should include when you line up on race morning:

  • Pre-race breakfast: The exact meal, timed to finish 3 to 4 hours before the gun
  • Pre-race hydration: 500ml fluid with electrolytes, finished 60 to 90 minutes before start
  • First fueling: At 25 to 30 minutes (or a specific mile marker near that time)
  • Fueling frequency: Every X minutes, based on what you tested
  • Carb target: X grams per hour, using specific products
  • Fluid target: X ml per hour, adjusted for expected race-day temperature
  • Sodium plan: X mg per hour if you're a heavy or salty sweater

Every number in that plan should come from your long run data, not from a generic guide.

Sweatr builds this plan automatically. It pulls your heart rate, pace, and environmental data from your Apple Watch or Garmin, combines it with your logged fueling and weigh-in data, and calculates a personalised race-day nutrition protocol — adjusted for the forecast conditions on race day, not the conditions you trained in.

If you've been running long runs in 30°C August heat but your October marathon will be 14°C, your fluid needs will drop significantly. Sweatr recalculates so you don't over-drink on race day and risk hyponatremia — a real danger that generic guides don't account for.

What to Do If a Long Run Goes Wrong

A bad long run isn't a disaster — it's data.

If your stomach rejected a gel at mile 15, you now know your gut's limit at that fueling frequency. Back off by 5 minutes per serving on the next run and see if the problem disappears.

If you bonked at mile 20 despite fueling, you probably started too late. Move your first intake earlier and increase your per-hour carb target by 10 to 15g.

If you finished feeling bloated and waterlogged, you drank too much. Most runners' stomachs can empty 150 to 200ml every 15 minutes. Anything above that sits and sloshes.

The point of testing is to find the edges. A run where nothing goes wrong teaches you less than a run where something does — as long as you know what caused it.

Your Timeline From Here

| Weeks Out | What to Do | |-----------|------------| | 8 weeks | Long Run 1 — test timing and tolerance | | 6 weeks | Long Run 2 — test quantity and carb type | | 4 weeks | Long Run 3 — full dress rehearsal | | 3 weeks | Begin taper — nutrition plan is locked | | 1 week | Race-week hydration protocol — no experiments | | Race day | Execute the plan you tested |

The athletes who nail race-day nutrition aren't the ones with the fanciest gels or the most expensive sweat sensors. They're the ones who used their long runs to build a plan from their own data — and then trusted it on the day.

You've got three runs left. Make them count.