The Post-Long-Run Fueling Audit: Turn Every Weekend Run into Race-Day Data

You finished your 18-miler on Saturday morning. You're lying on the kitchen floor, shoes still on, half a banana in your hand. You feel decent. Or maybe you don't. Either way, you're about to make the same mistake most marathon runners make: you're going to move on without learning anything.

Your long run is the single best opportunity you have to test your race-day fueling plan. Not in theory — with your body, in your conditions, at your effort level. But a test is only useful if you review the results.

Here's how to run a proper fueling audit after every long run, so that by race day, your plan isn't a guess. It's a dataset.

Why Most Fueling Plans Fail on Race Day

The most common post-marathon complaint sounds like this: "I followed my plan and still bonked at mile 22."

That plan was probably borrowed from a blog post, a coach's template, or the back of a gel packet. It told you to take a gel every 30 minutes and drink to thirst. It didn't account for your body weight, your sweat rate in the conditions you're actually racing in, or the fact that your stomach handles Maurten fine at an easy pace but rebels at marathon effort.

Generic fueling advice fails because it ignores your data. And the only way to get your data is to collect it — then look at it — systematically.

The Five Numbers You Need After Every Long Run

You don't need a lab. You don't need expensive equipment. You need a kitchen scale, your watch, and five minutes of honesty after each long run.

1. Body weight change (pre vs. post)

Weigh yourself before your run (after using the bathroom, minimal clothing) and immediately after. The difference, adjusted for any fluid you drank during the run, estimates your sweat loss.

If you lost 1.5 kg over a 2-hour run while drinking 500 ml, your total sweat loss was roughly 2 litres. That's a sweat rate of 1 litre per hour. This single number is the foundation of your hydration plan.

Do this across several long runs in different temperatures. You'll see your sweat rate isn't fixed — it shifts with heat, humidity, and fitness. A plan built on one data point is barely better than a guess.

2. Total fluid consumed

How much did you actually drink? Not how much you planned to drink — how much went in. If you carried a 500 ml bottle and came home with 200 ml left, you drank 300 ml. If you refilled at a fountain, estimate what you added.

Compare this to your sweat loss. If you lost 2 litres and drank 500 ml, you finished with a 1.5-litre deficit. That's a 3% body weight loss for a 50 kg runner — enough to measurably hurt your pace in the final miles.

3. Total carbohydrates consumed

Count every gram. Every gel, every chew, every sip of sports drink. A standard gel is 20–25 g of carbohydrate. If you took three gels and 500 ml of sports drink mixed at 60 g/L, that's roughly 100 g of carbohydrate over your entire run.

Divide by hours. If your run was 2.5 hours, you averaged 40 g/hr. Current evidence suggests most marathon runners benefit from 60–90 g per hour — so you were likely under-fueling without realising it.

4. GI symptoms

Rate your gut on a simple 0–3 scale after every long run:

• 0 — No issues at all
• 1 — Mild discomfort (some bloating or gurgling, didn't affect pace)
• 2 — Moderate distress (nausea, cramping, or urgency that slowed you down)
• 3 — Severe (had to stop, or couldn't keep fuel down)

Note when symptoms started (by time or distance), what you consumed in the 20 minutes before onset, and what the temperature was. Over several weeks, patterns emerge. Maybe your gut handles 60 g/hr perfectly in 15°C but starts complaining at 25°C. That's a race-day decision you can make in advance — if you have the data.

5. Pace vs. heart rate drift

Pull up your run on Strava, Garmin Connect, or your watch app. Look at two things:

• Cardiac drift: Did your heart rate climb steadily even though your pace stayed constant? A rise of more than 10–15% from the first half to the second half suggests dehydration or glycogen depletion.
• Pace decay: Did you slow down in the final third? By how much? Compare this to runs where you fueled differently.

If your heart rate drifted 12% and your pace fell off 30 seconds per km in the last 5 km, that's a signal. Was it heat? Under-fueling? Not enough fluid? Check it against your other four numbers.

Building Your Fueling Log

A spreadsheet is fine. A notes app is fine. Whatever you'll actually use is the right tool. Track these columns per long run:

| Date | Distance | Duration | Temp | Humidity | Weight pre | Weight post | Fluid in (ml) | Carbs in (g) | Carbs/hr | GI score | HR drift (%) | Pace last 5k vs first 5k | Notes | |------|----------|----------|------|----------|------------|-------------|---------------|-------------|----------|----------|-------------|--------------------------|-------|

After four to six long runs, you'll have enough data to spot the patterns that matter:

• Sweat rate by temperature — so you know how much to drink at your likely race-day conditions
• Carb ceiling — the grams per hour your gut can absorb without distress at race effort
• Optimal fluid timing — whether you do better sipping every 15 minutes or drinking larger amounts at aid stations
• Red-flag combos — like the fact that caffeine gels plus heat above 27°C always give you a GI score of 2

What to Change, and When

The audit only works if you act on it. Here's the decision framework:

If your sweat rate was higher than expected: Increase planned fluid intake for the next long run. Add 100–150 ml per hour and see if cardiac drift improves.

If your carbs per hour were below 50 g: You're almost certainly under-fueling. Add one gel per hour and track GI response. Your gut adapts to higher carbohydrate loads with practice — but only if you actually practise.

If your GI score was 2 or above: Don't just tolerate it. Identify the trigger. Was it a specific gel brand? Concentration of sports drink? Taking fuel at high intensity rather than at a slightly easier moment? Change one variable at a time and retest.

If pace decay was greater than 20 seconds per km in the final quarter: Cross-reference with fluid deficit and carb intake. If you were below 60 g/hr of carbs and lost more than 2% body weight in fluid, fueling is the most likely culprit — not fitness.

The Long Run Is the Lab. Race Day Is the Exam

You have somewhere between 4 and 10 long runs left before your fall marathon. Each one is a controlled experiment. The conditions vary — temperature, humidity, terrain — and that's a feature, not a problem. You want data across conditions, because race day might hand you any of them.

The athletes who line up with confidence on race morning aren't the ones who memorised a gel schedule from a magazine. They're the ones who tested, measured, adjusted, and tested again. They know their sweat rate. They know their carb ceiling. They know which gel brand sits well at 5:15/km pace in 22°C heat.

That's what the fueling audit gives you: certainty built from your own data.

Sweatr builds this audit automatically. It pulls your heart rate, pace, and workout data from your Apple Watch or Garmin, combines it with the fluid and fueling data you log, and tracks your sweat rate, carb intake, and GI patterns across every session. By the time you get to race week, your plan isn't borrowed from a blog — it's built from your body.

Download Sweatr free and start building your race-day plan from your next long run.

Your Next Three Saturdays

This weekend, do the audit for the first time. Weigh yourself before and after. Count your gels. Note your gut. Check the cardiac drift. Write it down.

Next weekend, change one variable based on what you found. More fluid, or a different gel timing, or an extra 20 g of carbs per hour.

The weekend after, review all three data points together. You'll already know more about your fueling needs than most runners learn in years of racing.

The long run is not just a fitness builder. It's the most valuable fueling data you'll ever collect. Stop wasting it.