Your training log is empty, and that is why you stopped using it

There is a specific way training diaries fail, and it has nothing to do with the app.

You install one in January. It opens on a blank page. You log a run, then another, and for about three weeks it works. Then you miss a day, then a week, and when you open it again it is a short, embarrassing list that says less about your training than your watch already knows. So you stop.

The failure is not discipline. It is that the diary started empty when your training did not.

The history already exists

If you run with an Apple Watch, every session you have done is already recorded — distance, duration, heart rate, route, splits. Years of it, sitting in Apple Health. It is the most complete record of your training that exists, and almost nothing reads it.

Most training apps treat Health as an inbox: they watch for new activities from the moment you install, and everything before that is invisible. That is a reasonable engineering decision and a terrible product one, because the value of a diary is entirely in its depth. A log with three weeks in it answers nothing. A log with two years in it answers "am I fitter than last spring", "what did I actually do in the month before that good race", "how many weeks have I strung together".

What "full on day one" actually means

Stopa reads your past sessions out of Apple Health when you set it up, so the diary is populated before you have logged anything. Concretely, on install you get:

• Week, month and year views — distance, hours and sessions for each, with per-day bars in a week, per-week in a month, per-month in a year.
• The year at a glance — a heat map of active days, your longest session, your biggest month, your average week.
• The record of each session — route, per-kilometre splits, elevation, heart-rate zones, power and cadence. Whatever your watch kept, not a summary of it.

None of that is data anyone had to type. It was already yours; it was just stuck in an app you do not open to think about training.

Why this matters more than it sounds

A training diary is not a scrapbook. It is the thing that makes the next decision less stupid.

Two examples that only work with depth behind them:

Consistency, honestly measured. A streak counted from install day is theatre. A streak counted across the history you actually have is information — and so is the gap in it, which is usually the more useful half.

Easy/hard balance. The 80/20 guidance is only checkable against a real sample. Over three weeks it is noise; over a rolling month of real sessions it tells you whether the "easy" runs you believe you are doing are actually easy.

The honest limits

Two things worth saying plainly.

It reads, it does not write. Health data goes one way — into the diary. Nothing is written back to Health, and nothing about it is used for advertising.

It is only as good as what your watch recorded. A session you ran with the watch left at home is not in Health, so it is not in the diary either. You can add one by hand, but the app cannot invent what was never measured.

The point

The best training log is the one that already contains your training. Not because logging is hard, but because a log you have to fill before it becomes useful is a log most people abandon at week three — and the data was sitting there the whole time.

Related:

• From PDF to Apple Watch: the workflow that actually works
• Apple Watch vs Garmin for structured workouts
• A TrainingPeaks alternative for self-coached athletes

We're building in public - follow along on X, Instagram, TikTok and Facebook.