Skip to content
Use Cases10 min read

Running Training Log on iPhone: Track What Strava Misses

GPS apps capture your pace and distance. A running training log on iPhone captures how you felt, injury warnings, shoe mileage, and race lessons — the data that actually improves your training.

·By Taha Baalla

GPS watches and apps like Strava and Garmin Connect track your pace, distance, heart rate, and elevation perfectly. What they cannot track is the subjective experience of the run — and that is where the most useful training information often lives.

What Your GPS App Misses

Strava knows you ran 10km in 52 minutes. It does not know: - Your legs felt heavy from mile two because you under-slept - You cut the run short because your right calf started twinging - The pace felt easy despite looking slow — you ran into a headwind for 6km - You wore the Pegasus 40s for the first time and felt hot spots at the heel - You took a gel at mile 5 and it settled badly

This qualitative context is what distinguishes a training log from a GPS log. After six months, you can review your running log and see patterns: what conditions correlate with your best sessions, which shoes hold up for long runs, when you are heading toward injury before the injury actually arrives.

The Core Running Log Note

Create a running log note — one per week, one per month, or one per training block, depending on your preference. Each run gets a dated entry:

``` [Date] | [Distance] | [Route/Location] Weather: [temp, wind, rain] Shoes: [model and approximate mileage on them] Time of day: [morning / lunch / evening] Hours sleep: [last night's sleep]

Type: [easy / tempo / interval / long run / race / cross-training] Planned: [what the plan called for] Actual: [what you did]

Feel: [scale or description — legs, breathing, mental] Effort: [RPE 1-10 or easy/moderate/hard] Heart rate: [avg / zone if tracked] Pace: [overall, split paces if relevant]

Highlights: - [anything noteworthy — a new road, a feeling, a split you hit]

Issues: - [any tightness, pain, discomfort — location, onset, severity]

Nutrition/hydration: - [what you took, when, how it went]

Post-run: - [stretching / ice / foam roll / anything done for recovery]

Tomorrow's plan: [what is scheduled] ```

Not every run needs every field. A 30-minute easy jog might get three lines. A 22-mile marathon long run deserves a full entry.

The Race Note

Race experiences deserve their own detailed note:

``` RACE: [Name] Date: [date] Distance: [distance] Location: [course description — flat / hilly / trail] Weather: [conditions] Goal: [A goal / B goal / C goal]

Splits: - Mile 1: [time] - Mile 5: [time] - Half: [time] - Mile 20: [time] - Finish: [time / chip time]

Nutrition: - Pre-race: [what you ate, timing] - During: [gels, drinks — brand, timing, total] - Post-race: [recovery nutrition]

Shoes: [model worn] Kit: [any notable clothing — shorts, socks that worked or didn't]

What worked: - [pacing strategy, fuelling, mental approach]

What to change: - [what cost you time or caused discomfort]

Lessons for next race: - [concrete adjustments]

Time: [final time] | Placing: [overall / age group] ```

Race notes are the highest-value entries in a running log. You reference them constantly when preparing for the next race.

Injury Tracking

Injuries — or the warning signs before injuries — deserve their own structure:

``` [Date] ISSUE — [Body part] Onset: [when it first appeared / during what run] Description: [location, character — sharp, dull, tight, burning] Severity: [1-10 or mild/moderate/severe] Aggravating: [what makes it worse] Relieving: [what helps]

Actions taken: - [rest days, ice, physio, sports massage, tape]

Progress: [Date update] [status] [Date update] [status — resolved / ongoing / worsened]

Return to running: [date and how it went] Diagnosis (if seen by professional): [what they said] ```

Tracking early warning signs is especially valuable. Many runners who log "slight tightness in left Achilles" for a week before it becomes an injury look back and wish they had acted sooner. Your log creates accountability to your own early warnings.

Shoe Mileage Tracking

Most running shoes last 400-600 miles before cushioning degrades. Track mileage per pair:

``` SHOE LOG

[Model] — [colour / purchase date] Purchase: £[price] from [retailer] Mileage at purchase: [your total mileage when you started using them] Mileage retired: [when you stopped using them] Total miles on these shoes: [calculated] Notes: [any issues — hot spots, wear pattern, for what type of run]

---

[Model] — [colour / purchase date] ... ```

When you experience unexplained leg fatigue or repeated minor injuries, one of the first things to check is shoe mileage. Your log tells you immediately.

Training Block Notes

For structured training (marathon plan, 10k build, base phase), a training block note tracks the bigger picture:

``` BLOCK: [e.g. London Marathon 2027 Training] Start date: [date] Goal race: [race name, date] Goal time: [A goal]

Week 1 summary: [total miles, key sessions, how it went] Week 2 summary: [...]

Observations: - [what's working in the plan] - [what needs adjustment] - [recurring fatigue patterns]

Mid-block check-in [date]: [honest assessment of where you are against where the plan expected]

Final week summary: [taper notes, feelings, pre-race readiness] ```

Reviewing this note before the race gives you an honest picture of your preparation — which prevents the pre-race anxiety of wondering whether you trained enough.

iPhone-Specific Advantages for Runners

Dictation immediately post-run. While stretching after a run, dictate your entry. Your memory of how the run felt is most accurate in the first fifteen minutes. Use Siri dictation or Nemos voice input — speak naturally, edit later.

Apple Watch. The ultimate running log tool. Raise your wrist at any point during a run and dictate: "calf tightening, note for training log." That voice memo syncs to your phone before you finish the run.

Floating capture button. If something noteworthy happens during a route you know well — a new shortcut, a landmark to remember — pull out your phone and add a quick note without navigating through menus.

Share Sheet from Strava/Garmin. Open a completed activity in Strava, screenshot the splits, send to a race note. Keep technical data and subjective experience in adjacent notes.

Offline. You are often running in areas with poor signal. Notes save on-device and sync when you return to connectivity.

Shortcuts automation. Build a "Post-Run Note" shortcut that creates a new entry with today's date pre-filled. One tap after you finish.

FAQ

Should I log every run or just key sessions? Log every run during structured training blocks. During base building or recovery phases, you might log weekly summaries rather than individual runs. The discipline of logging every session during peak training phases is worth it — patterns emerge from the complete data set, not just the memorable runs.

Is a running log worth it if I am a casual runner? Yes, for two reasons. First, it helps you spot early injury warnings before they become serious. Second, even casual runners have good and bad days — knowing that a bad day was preceded by poor sleep or unusual stress takes the sting out of it.

How do I handle multi-sport training (triathlon, cycling)? Create separate log sections or a separate note per sport. Cross-training runs that are deliberately easy do not need the same detail as running-specific sessions, but note the type and duration.

What is the best way to track my easy/hard balance? Log effort level (RPE or zone) for every run. Weekly, count how many runs were easy (RPE 1-4) versus moderate/hard (RPE 5-10). Most training plans call for 80% easy, 20% hard. Many runners discover they are running most sessions at moderate effort — too hard to be easy, not hard enough to be stimulating.

Should I track indoor treadmill runs? Yes. Note whether the run was indoor or outdoor and at what incline. Treadmill runs (especially at 1% incline) translate well to outdoor running and are worth logging, especially in winter when weather limits outdoor options.

Related Reading

Sources

  • Daniels, Jack. *Daniels' Running Formula*. Human Kinetics, 2005.
  • Fitzgerald, Matt. *80/20 Running*. New American Library, 2014.
  • Noakes, Tim. *Lore of Running*. Human Kinetics, 2003.
  • Maier, T., et al. "Relationship between perceived and actual exercise intensity." *International Journal of Sports Physiology and Performance*, 2018.
  • Kluitenberg, B., et al. "The NLstart2run study: Incidence and risk factors of running-related injuries." *Scandinavian Journal of Medicine & Science in Sports*, 2015.
TB
·Founder, Némos

Taha built Némos after years of losing screenshots and voice memos across a dozen apps. He writes about on-device AI, personal knowledge management, and building privacy-first tools for iPhone.

@nemosapp
Join 2,400+ on the waitlist

Stop losing things you save.

Némos remembers every screenshot, voice memo, link, and note — and surfaces them when you need them. Free, private, on-device AI.

No credit card · iOS launch Q3 2026 · We'll email you when it's live

More from the blog