Why Every Serious Runner Needs a Race Log (Not Just Strava)

You finish a half marathon. Your Garmin syncs to Strava. You add a quick caption, get some kudos, move on. Two weeks later you couldn’t tell someone your finish time without looking it up. Two years later you can’t remember if that race was a PR or just a tune-up.

Strava captured the activity. It didn’t capture the race.

This is the distinction most runners miss. Strava is excellent at what it does—logging daily training, sharing with friends, analyzing pace and elevation. But it’s a training tool, not a race log. And serious runners need both.

Here’s why every runner who cares about their racing needs a dedicated race log alongside Strava—and what changes when you have one.

What Strava Does Brilliantly

Before discussing what Strava lacks, let’s acknowledge what it does well. Strava is the gold standard for:

• Automatic activity capture from GPS watches
• Detailed pace, elevation, and heart rate analysis
• Social engagement with running friends
• Segment PRs on specific routes
• Weekly mileage tracking and consistency
• Training visualization across weeks and months

For daily training, Strava is exceptional. Most serious runners should keep using it. The question isn’t whether to use Strava—it’s whether Strava alone is enough for runners who care about racing.

It isn’t.

The Five Problems With Tracking Races Only in Strava

1. Races Are Buried in Activity Feeds

If you run 5 times per week, that’s roughly 260 activities per year. Your 3-5 races are mixed in with training runs, easy days, workouts, and cross-training. There’s no race-only view. To see your race history, you scroll through hundreds of training activities.

2. No Automatic PR Tracking

Strava tracks segment PRs brilliantly—fastest times on specific routes. But it doesn’t track your race PRs across distances. Want to know your current 10K PR? You’ll manually scroll through every 10K race you’ve run.

When you finish a new race, Strava won’t tell you if it’s a PR. That information has to come from somewhere else.

3. No Place for Goals

Before every important race, serious runners set goals. A goal (best case), B goal (realistic), C goal (minimum acceptable). This is standard race strategy.

Strava has nowhere to record these. Your goals live in your head or scattered notes. After the race, there’s no way to compare what you planned to what happened. The relationship between goal-setting and goal-achievement—valuable data over time—doesn’t exist.

4. No DNS, DNF, or DQ Tracking

Did Not Start. Did Not Finish. Disqualified. These are part of every serious racer’s history. The injuries before race day. The dropouts at mile 18. The missed cutoffs.

Strava can’t capture these properly. DNS doesn’t generate an activity. DNF shows up as a partial activity with no clear “DNF” indicator. DQ looks identical to a normal finish. Your complete race history has gaps.

5. Race Memories Get Lost

Strava activity descriptions are the same for race recaps as for training run notes. They mix together in the same feed. Want to look back at marathon race notes from three years ago? You’re clicking through individual activities, hoping you wrote something meaningful.

The specific details that make races memorable—weather, how you felt, what worked, the finish line moment—either don’t get captured or get buried.

What a Race Log Adds

A dedicated race log fills these gaps without replacing Strava. Here’s what changes when you add one:

Race-Only View

Your races, separated from training runs, in a clean timeline. Filter by distance to see all your marathons, all your half marathons, all your 10Ks. Patterns become visible. Your racing journey reveals itself.

Automatic PR Tracking

The system knows your PRs across all distances instantly. New race time? It tells you immediately if it’s a PR. No manual scrolling, no formulas, no remembering. The data does the work.

Goal Integration

Set A/B/C goals before each race. After the race, the system shows you how you did against each goal tier. Over years, you see patterns: are your A goals realistic, or chronically too aggressive? Do you typically hit B goals? This data improves future goal-setting.

Status Tracking for Everything

Completed. DNF. DNS. DQ. Your complete race history—including the races you didn’t finish—gets properly tracked. The lessons from incomplete races are often more valuable than from completed ones. They shouldn’t be invisible.

Race-Specific Memory

Dedicated space for race recaps, separate from training notes. Weather conditions, pacing strategy, fueling notes, mental moments. Years later, you can read the actual experience, not just see a time.

Race Progression Over Years

See how your marathon times have evolved over 5 years. Watch your half marathon progression. Identify breakthrough years and plateau periods. The story of your racing life becomes visible in a way Strava’s activity feed can’t show.

The “Both Tools” Approach

This isn’t about replacing Strava. It’s about adding the right tool for race-specific tracking.

Most serious runners benefit from using both:

• Strava: Daily training runs, workouts, pace/HR analysis, social engagement, weekly mileage, segment PRs
• Race log: Race history, race PRs, goals vs results, race notes, DNS/DNF tracking, progression over years

Different tools, different purposes. Like using a calendar for scheduling and a notes app for content—not redundant, just specialized.

The Integration Solution

The concern with using two tools is data entry. Do you log every race twice? No.

Good race logs integrate with Strava directly. When you finish a race:

1. Your GPS watch syncs to Strava automatically
2. You mark the activity as a race in Strava (one click)
3. Your race log imports the race data from Strava
4. You add the race-specific details (goals, notes, status)

Total additional time: under 5 minutes. The friction that used to make race tracking impossible disappears.

The Question Every Serious Runner Should Ask

If you’ve been running for years, ask yourself:

• Can you instantly state your PR at every common distance?
• Can you list every marathon you’ve finished with dates and times?
• Can you compare your goals from race to race over the past 5 years?
• Can you see how your half marathon times have progressed?
• Can you find your race notes from three years ago without difficulty?

If you answered “no” to any of these, your race history isn’t properly tracked. Not because you’re not serious about running—because Strava isn’t designed for this.

The serious runners who can answer “yes” to all these questions aren’t relying on memory or scrolling through years of activities. They’re using systems built specifically for race tracking.

Who This Matters For

Not every runner needs a dedicated race log. If you race occasionally for fun and don’t care about historical detail, Strava alone might be enough.

But you probably need a race log if you:

• Set time goals for your races
• Pursue Boston Qualifiers or other qualifying times
• Track PRs across multiple distances
• Want to remember races in detail years later
• Race 3+ times per year
• Have been running for 5+ years
• Work with a coach who references race history
• Find yourself looking up your own race results

If any of these apply, you’re a serious enough runner that race tracking matters. And if race tracking matters, Strava alone isn’t enough.

Starting Today

The friction of starting a new system stops most runners. But the time investment is smaller than it seems.

First step: choose a race log system. Dedicated apps work best for most runners, especially ones with Strava integration to handle the import work.

Second step: connect Strava and import your existing race history. With integration, this takes minutes for years of races.

Third step: add the race-specific context to your imported races. Goals, notes, status. Start with recent races; backfill older races over time.

Fourth step: build the habit. Every future race gets logged within 48 hours, with the race-specific details Strava doesn’t capture.

Total setup time for years of race history: typically under an hour. Ongoing time per race: 5-10 minutes.

The Bottom Line

Strava is excellent. Keep using it. Don’t abandon what’s working for your training.

But Strava isn’t a race log. It’s a training tool that happens to record races as part of capturing all activities. The features that matter for race-specific tracking—race PRs, goals, status tracking, race-only views, progression analysis—either don’t exist or are buried.

Serious runners deserve a system built for what they actually care about: their racing. Their goals, their PRs, their progression, their complete race story.

A dedicated race log alongside Strava isn’t redundancy. It’s specialization. Different tools, different purposes, both adding value.

Your training belongs in Strava. Your race history deserves better.

Ready to add proper race tracking alongside your Strava? RunningLog integrates with Strava to import your races automatically—your training stays where it is, your race history gets the system it deserves.

Do you track races separately from training, or rely on Strava for everything? Share your approach on Instagram or Threads!