Skip to content

Practical guide

A running training log should explain the next decision

Use a simple running log for session purpose, effort, completion, recovery and the next adjustment without turning data into diagnosis.

Updated Oct 17, 2026

On this page

Record enough to make the next decision

A running log should connect what you intended, what you completed and how you responded. Distance alone cannot explain heat, hills, poor sleep or an unusually hard effort. A notebook or spreadsheet is enough if you review it consistently.

FieldExample entryWhy it helps
Purpose and completed workEasy run; planned 35 minutes, completed 25Shows a deliberate change rather than an unexplained shortfall
Effort and conditionsConversational until the hill; hot afternoonPrevents a slower pace being mistaken for lost fitness
Recovery contextShort sleep; legs felt normal the next morningAdds context without treating one metric as a diagnosis
SymptomsNew localized discomfort; stopped when movement changedRecords what happened for appropriate follow-up
Fueling, when relevantProduct, grams, timing, fluids and toleranceMakes the next long-session rehearsal comparable
Next decisionRepeat a familiar easy duration after recoveryTurns the record into a bounded action

Review the week

Check completed frequency and duration, the cost of the longest or hardest sessions, and whether ordinary easy running stayed comfortable. Compare similar conditions across several weeks rather than interpreting every pace fluctuation as progress or decline.

For example, a slower run in heat with normal conversation and recovery does not automatically justify lowering all training paces. Repeatedly high effort on familiar easy routes, especially with persistent symptoms or poor recovery, deserves a different response: hold or reduce training and investigate the cause.

Heart rate, sleep estimates and other wearable measures are optional context. Keep a metric only if you understand its limitations and it changes a useful decision. Logging cannot diagnose an injury or guarantee that one will be prevented.

Use the adaptive-plan guide for missed sessions and the fueling planner to check long-run intake arithmetic. Seek appropriate care for persistent symptoms or pain that changes movement.

Put this into action

Open the plan and tool that match this guide

Worksheet

Use this before you choose

One-week log template

  • • Total minutes (or km): ____
  • • Long run: ____ (time + feel)
  • • Key workout: ____ (what + RPE + note)
  • • Sleep: ____ (good/ok/bad)
  • • Pain signals: ____ (0–10 + location)
  • • Fueling practice: ____ (carbs/h + timing + tolerance)

Checklist

Check your choice

Training log checklist

  • • I track weekly volume + long run (not just daily streaks).
  • • I record RPE and recovery notes for key sessions.
  • • I track sleep in a simple way (good/ok/bad).
  • • I track pain signals early (0–10).
  • • I log fueling practice on long runs.

Adaptive AI coach for iPhone

Meet your adaptive AI coach.

Tell your coach what you are training for. It builds the plan, follows the work you complete, and adapts upcoming training when recovery, your schedule, or real life changes.

FAQs

What should a running log include?

The session purpose, completed duration or distance, effort, relevant conditions, recovery and the next decision. Add fueling details for sessions where intake is being rehearsed.

Do I need a wearable to keep a training log?

No. A notebook or spreadsheet with consistent entries can be useful. Device estimates are optional context, not diagnoses.

How often should I review the log?

Use a brief weekly review and compare several similar weeks before drawing conclusions about fitness. Persistent symptoms deserve attention sooner.

Keep going

Sources