How to read a long run

The long run should teach the race, not just prove you can suffer. Distance alone is not the point. What you want from a long run is information: how the body holds up, how pacing and fueling actually go, and whether the last third looks anything like the race you want to run.

When the last hour always falls apart, the instinct is to fix the last hour. More gels, more grit, a harder finish next time. That is usually the wrong place to look. If the last hour always falls apart, look before the last hour. Pacing, fueling, the previous 48 hours, and the total week all matter, and they all happen before the wheels come off.

Fueling is part of the block, not a race-day detail. A long run is where you practice fueling, not the start line.

This is why I am slow to prescribe a single fix from a bad long run. A bad long run can be a pacing problem, a fueling problem, a heat problem, a route problem, or a goal problem. They look similar from the outside and they need different answers. Do not pick the fix before you know the problem.

The job of marathon training is to make goal pace less expensive, not just more familiar. A good long run moves you toward that. A long run that leaves you wrecked for the next week often does the opposite, even if the splits looked impressive.

So when you finish a long run, do not just log the miles. Read it. What did it teach you about the race, and what does it tell you to change next week?