TRAINING REVIEW
How to review your first month of recorded runs
Your first review should make the history easier to use. Check completeness, establish a baseline and choose one question for the next month.
Check the record before the trend
Start with the activity list. Are the dates correct? Did all intended runs arrive? Is the same outing present twice after using two recording sources? A trend made from incomplete or duplicated records can answer the wrong question very precisely.
Keep running sessions separate from walks and other activities when calculating a running total. Record how you treated mixed walk-run outings so the next review uses the same rule. If you changed watches during the month, note the date instead of assuming every recorded field remained comparable.
Make a compact summary
This illustrative four-week log uses completed weeks. It is a reporting example, not a schedule to follow.
| Week | Runs | Distance | Recorded duration |
|---|---|---|---|
| 1 | 3 | 15 km | 95 min |
| 2 | 3 | 18 km | 112 min |
| 3 | 2 | 12 km | 78 min |
| 4 | 3 | 17 km | 108 min |
| Total | 11 | 62 km | 393 min |
The third week differs from the others. Add the relevant context: travel, missing import, changed schedule or another known reason. The table alone does not distinguish those cases. A calendar month can include partial weeks; choose month boundaries or complete weeks explicitly and label the result.
Choose one comparable pair
Find two runs with a similar purpose, route and time basis. Compare their distance, duration and available sensor data. Do not select only the two best-looking activities. Explain why the pair is relevant and keep the other suitable runs visible.
For an initial baseline, write down the route and typical recording method. A short history is useful for learning what you have recorded, but it does not justify a broad conclusion from every apparent upward or downward line. Missing heart-rate data limits heart-rate comparisons without making the distance log useless.
Leave with a repeatable question
Use Runome's activity history and comparisons to answer one concrete question, such as whether the same easy loop has become more consistently paced. Save a brief review note containing the date range, included activities, one observation and one unresolved issue.
Next time, repeat the same definition before adding more metrics. Read calendar versus rolling-week totals if your numbers disagree between views. Use fair comparison baselines to choose a useful pair without turning a first-month review into a search for a flattering score.