Notebook or app: what a workout log is really for

Before deciding between a notebook and an app, it is worth being clear about what a log is for. It answers one question next week: did I do more than last time? Anything that helps answer it counts; anything else is decoration.

What a notebook does perfectly well

Records four fields. Costs nothing. Never updates, never runs out of battery, never shows an advertisement, and cannot lose your data to a shutdown.

It also has a quiet advantage that people underrate: writing by hand is fast and requires no attention. No unlocking, no searching, no autocomplete choosing the wrong exercise.

A great many strong people have used nothing else, and if you are choosing on principle rather than on features, a notebook is a defensible choice.

What an app actually adds

Three things, and they are real.

Last week's numbers, instantly. When you start an exercise, the app shows what you did last time for that exercise without you searching. This is the single most valuable feature and the one that determines whether logging stays fast.

Arithmetic you would not do by hand. Weekly hard sets per muscle group. Estimated one-rep maxima from working sets. A lift plotted over six months. All of these are computable from a notebook and effectively nobody does it, which means the information exists and is never used — see how many sets per muscle per week is enough for why the volume tally matters.

Searchable history. "When did my elbow first hurt?" is a thirty-second query in an app and an afternoon with a notebook.

What does not matter

Calories burned. Poor estimates that encourage treating training as a way to offset food — are the calories-burned numbers worth anything.

Social feeds and badges. Engagement features, designed to make you open the app, not to make you stronger.

Exercise demonstration videos. Useful once, when learning a movement. Not a reason to choose a logging tool.

Programme generators. Most produce something generic. A simple progression you follow beats a sophisticated one you abandon, which is the case for double progression.

Rest timers. Nice to have, and a phone clock does it.

The test that decides it

Do you log during the session?

If a tool makes logging a set take more than a few seconds, you will stop logging mid-workout, then start logging from memory afterwards, then stop entirely. That sequence is extremely common and it is a tool problem rather than a discipline problem.

Time one session with whatever you are using. If entering a set takes longer than writing 100×5 @2 on paper, the tool is losing to a notebook.

The hybrid that works

Log on paper during the session, transfer to a spreadsheet or app weekly.

You get the speed of paper when speed matters and the arithmetic when you are reviewing. It costs five minutes a week and it is what several people who are serious about both actually do.

Data export matters more than it seems

Two years of training data is worth something, and it is the only record of what you actually did.

Before committing to an app, check that you can get a CSV out of it, on the free tier, covering the whole history, after you cancel. An app that makes this difficult is telling you how it thinks about the data it holds — the argument in how to get your food log out of any app.

A notebook has perfect data portability and terrible searchability. An app can have both, and many do not.

The food log question

The useful questions cross both records. Is this deficit costing me strength? Did a bad sleep week show up in training and in appetite together? Am I gaining weight fast enough to explain the strength increase, or too fast?

None of those get asked when the two records live in separate apps, because nobody opens two apps to compare. That is the practical argument in why food and training belong in the same log.