Training for Your First Marathon: How to Use Data to Finish Strong

Most first-time marathon runners track one thing: miles. They log their weekly distance, follow a mileage build schedule, and assume the rest will sort itself out. Then, at week 10 or 12, their legs stop recovering between sessions and they can’t tell why. Was it too much mileage? Too many hard sessions? The three strength workouts they added last month? Without data on all training inputs, the cause is invisible.

A complete first marathon training plan tracks more than mileage. The case for tracking all training inputs, not just the primary modality, is covered in why tracking your workouts drives better progress. For marathon training, that principle applies across running, strength work, and mobility combined. Knowing why your legs feel the way they feel is more useful than guessing. You don’t need to become a data analyst. You need a record of all the inputs.

The Unique Tracking Problem for First-Time Marathon Runners

Dedicated running apps (Garmin, Strava, Runkeeper) are excellent at capturing GPS data: distance, pace, elevation, heart rate if you have a monitor. For pure running training, they’re complete.

The gap appears when you add cross-training. First-time marathon runners are almost always told to add strength training and mobility work to support the running volume. Good advice, but the strength sessions and stretching are typically tracked nowhere, in no app, with no session record. This means two things get missed.

First, cumulative fatigue from cross-training doesn’t show up in your running data. Three demanding lower-body strength sessions on top of a 60km running week is a very different physiological load than 60km with light mobility work. The mileage is the same; the recovery demand isn’t.

Second, cross-training progress itself becomes invisible. If your hip mobility work is helping, you’d see it in stride consistency data over time. If your strength sessions are building relevant muscle, you’d see it in running economy at a given pace. But only if you’re tracking both.

The approach in this guide: use your running watch or GPS app for all running data, and use Workout Lab to track every cross-training session, including strength work, mobility, stretching, and yoga. The two data sources together give you a complete picture of your weekly training load.

How to Set Up Your Tracking System

Before starting the training program, establish your logging protocol:

Running sessions (GPS app): Log every run with distance, pace, and effort level. Note whether the session was easy, moderate, or hard. If your watch captures heart rate, use heart rate zone data to verify what “easy” actually means (for most beginner marathon runners, easy means running slower than feels natural, with heart rate below 70% of maximum).

Cross-training sessions (Workout Lab): Log every strength session, mobility session, and stretching block as a separate workout. For strength work, log exercises with reps, sets, and RPE. For mobility or yoga, log session duration and a single RPE score for the overall session.

Weekly review: Once per week, review both data sources together. The key question: what was my total load this week, and how did I feel at the end of it?

For a framework on how the plan-track-adjust cycle applies to multi-week training programs, see how to use the Plan-Track-Adjust method for fitness progress. The marathon training cycle is a 16-week application of that exact model.

The 16-Week Framework

The first marathon training plan below is a 16-week beginner framework, not a prescription. Athletes with lower current fitness should start with shorter long runs and build more gradually. Athletes with a running background can compress early phases.

Phase 1: Base Building (Weeks 1-4)

• Weekly distance: 25-35 km
• Long run: 12-16 km
• Easy sessions: 3 per week at genuine easy effort
• Cross-training: 2 strength sessions, 1-2 mobility sessions
• Key metric: Complete each long run feeling like you could continue another 5 km

Phase 2: Progressive Loading (Weeks 5-10)

• Weekly distance: 35-55 km (increasing approximately 10% per week, with one down-week every 3-4 weeks)
• Long run: 16-32 km by week 10
• One tempo or marathon-pace run per week
• Cross-training: 2 strength sessions, 2 mobility sessions
• Key metric: Long run RPE staying below 7 despite increasing distance

Phase 3: Peak Training (Weeks 11-14)

• Weekly distance: 55-65 km
• Long run: 32 km at week 12, 35 km at week 13
• One marathon-pace run (10-15 km at goal race pace) per week
• Cross-training reduced to 1 strength session, daily mobility
• Key metric: RPE trending flat or down at the same pace compared to week 8

Phase 4: Taper (Weeks 15-16)

• Weekly distance drops to 40 km (week 15), then 20 km (race week)
• Long run: 20 km at week 15, 10 km at week 16
• No strength sessions
• Daily light mobility
• Key metric: Legs feeling recovered and reactive by the end of week 16

The Metrics That Actually Matter

Weekly distance is the headline number. Build it gradually. The 10% weekly increase rule is widely cited; the underlying logic is that connective tissue (tendons, ligaments) adapts more slowly than cardiovascular fitness. Running more volume than connective tissue can handle produces knee, hip, and Achilles injuries that end marathon campaigns. Many coaches (for example, Jack Daniels in Daniels’ Running Formula, 4th edition) recommend building to a minimum of 50-60 km per week before race day for a strong first marathon finish.

Long run distance is the most critical single session each week. It builds both the aerobic capacity and the mental familiarity with extended effort. Log the distance, the duration, the pace, and the RPE. A useful signal: if your long run RPE at a given distance is higher than it was 2 weeks ago at a shorter distance, you’re either fatigued or running too fast.

Session RPE for all cross-training. A hard strength session at RPE 8 the day before a long run is not the same as a light mobility session at RPE 3. Logging this makes the relationship between cross-training effort and running recovery visible over time.

Cumulative weekly RPE load is a simple derived metric: add up the RPE from every session during the week. A week with 5 running sessions averaging RPE 5 plus 2 strength sessions at RPE 7 has a total load of 39. Compare this across weeks. If your total load is climbing but your long run performance is declining, you’re accumulating fatigue faster than you’re recovering from it.

Rest heart rate (if you have a heart rate monitor): rising resting heart rate over several days is one of the earliest signs of insufficient recovery. It’s not a perfect signal, but a resting heart rate 5-8 beats per minute above your baseline after several days of training is a data point that your body hasn’t fully recovered.

The Cross-Training Data Gap

Here’s where most first-marathon tracking plans miss the target: they treat cross-training as supplementary and optional to log. In practice, for a first-time marathon runner doing 3-4 runs plus 2 strength sessions plus 2 mobility sessions per week, the cross-training represents 30-40% of the week’s total physiological load. Tracking only the running leaves the other 30-40% dark.

Consider two athletes both running 50 km in week 9:

• Athlete A: 50 km running + 2 heavy lower-body strength sessions at RPE 8 + 1 yoga session at RPE 4
• Athlete B: 50 km running + 2 light upper-body strength sessions at RPE 5 + 2 stretching sessions at RPE 3

Athlete A’s legs are supporting significantly more load than Athlete B’s despite identical running volume. If Athlete A’s long run performance declines in week 10, the cause is visible in the cross-training data. Without it, the declined performance looks mysterious.

Log every session. The marginal time cost is under 3 minutes per workout.

How to Track Cross-Training in Workout Lab

Set up Workout Lab as your cross-training log alongside your GPS running app:

Strength sessions: Create workouts with the exercises you’re doing (squats, lunges, hip thrusts, single-leg deadlifts, calf raises). Log sets, reps, and load for each. Add an RPE for the session overall.

Mobility and stretching: Create a workout type called “Marathon Mobility” or similar. Log the session as a single entry with duration and RPE. You don’t need to log individual stretches unless you’re tracking specific mobility targets (e.g., hip flexor hold time for a specific stretch).

Weekly review: At the end of each week, look at both your GPS app’s running summary and Workout Lab’s weekly overview. The combination shows your total training load across all modalities.

Set goals in Workout Lab for the cross-training components: for example, a goal to maintain 2 strength sessions per week through the peak phase. The tracking makes adherence visible, so you can see whether you’re actually hitting the cross-training targets or quietly dropping sessions when the running gets hard.

For a deeper look at how consistent cross-training tracking affects long-term performance, see why consistency beats intensity in fitness. The same principle that applies to strength training applies to marathon cross-training: frequency and adherence, tracked over time, predict outcomes better than any individual session quality.

The Most Common First-Marathon Data Mistake

Tracking mileage but not cumulative fatigue. Mileage is an input. Fatigue is the output that determines what you can absorb from that input.

The signs of accumulated fatigue in training data:

• Long run RPE increasing at the same pace across two consecutive weeks
• Resting heart rate consistently above baseline for 4+ days
• Strength session performance declining (same weights, same reps, higher RPE than 3 weeks ago)
• Cross-training sessions increasingly logged as skipped or shortened

Any two of these together is a signal to reduce load. The reduction doesn’t need to be dramatic: one planned easy week (reduce mileage by 20%, drop one strength session, emphasise mobility) is often enough to restore recovery capacity.

Without the full data picture (running and cross-training together) you can only see the mileage signal. The other three are invisible.

Race Week Tracking

Taper week is not the time to try new things or make up for skipped training. Log your runs as planned (shorter, easier), skip the strength sessions, and do daily light mobility. The goal is to arrive at race day with legs that have recovered from 14 weeks of loading.

Log your race-day performance: the distance (42.2 km), the time, and an overall RPE. This becomes your baseline for any future marathon training. The gap between your race RPE and your long run RPE at 35 km will tell you whether your pacing was accurate and whether your training preparation matched the race demand.

Your race result is a data point, not a verdict. First marathons almost always leave significant room for improvement: in pacing strategy, in long run distance, in the cross-training mix. The tracking you’ve done through 16 weeks gives you the data to make those adjustments with specificity rather than guesswork.

For structured thinking about how to evaluate training programs using data after a training cycle, see how to know if your workout program is working. The same analytical framework applies to marathon preparation.