Training Log: What to Record If You Want to Progress

Almost everyone ends up logging their sessions. Far fewer people actually use the log. The difference is not the tool but what goes into it: a training log is not there to remember the past, it is there to decide what goes on the bar today.

The bare minimum: four pieces of information

Every usable log contains at least this, and plenty stop there quite happily:

• The date
• The exercise, always named the same way
• The load, bar included
• Reps actually completed, set by set, not an average

With those four fields you can apply progressive overload, which is most of the job. Without them, you are improvising.

Two details make that minimum genuinely usable. First, log the bar: an Olympic bar weighs 20 kg, a short bar often 10, and "60 kg" means nothing if you do not know what you counted. Second, separate warm-up sets from working sets, or your volume becomes unreadable week to week.

The three columns that change everything

Beyond the minimum, three pieces of information turn a log from a memento into a decision tool.

What to record	Why	Example
Proximity to failure	Separates an easy set from a limit set at the same load	"2 in reserve"
Rest time	Makes your sessions comparable to each other	"2 min"
Context	Explains odd sessions instead of just enduring them	"5 hours of sleep"

The first is the most valuable. Three sets of 10 at 60 kg tell a very different story depending on whether you were spent or could have done five more. That marker is covered in detail in our article on RPE and RIR, and it takes two words per exercise.

Context notes, badly underrated

This is what 90 % of logs are missing. When a session goes badly we chalk it up to an off day, write nothing, and three weeks later have no idea whether it was a one-off or the start of a trend.

Three words are enough, written in the moment:

• "5 hours of sleep", "broken night"
• "fasted", "ate 30 min before"
• "heavy week at work"
• "with belt", "with straps"
• "different machine", "gym packed, longer rests"

Two months in, you stop guessing and start observing. It is often what separates a genuine plateau from a run of bad weeks that had nothing to do with your programme.

What not to record

An overloaded log gets abandoned, and an abandoned log is worth nothing. Three excesses to avoid:

Total tonnage. Multiplying load by reps by sets gives an impressive but misleading number: it goes up when you lighten the weight and do more reps, even though you have not progressed.

A ten-point effort rating on every single set. You will spend more time logging than lifting. A rating on your working sets is plenty.

Changing everything constantly. If you rename exercises, switch machines and reorder your session every month, your log holds data but supports no comparison.

The rule: if a piece of information cannot change a future decision, it does not need recording.

Reading it back, the step nobody takes

A log you fill in and never reread is a diary, not a tool. Take ten minutes once a month and ask three questions:

1. What went up? Load or reps, it does not matter, but something should have moved.
2. What has been frozen for six weeks? That is where a change is needed, not elsewhere.
3. Do my bad sessions fall at random? This is where context notes pay off.

Ten minutes a month beats two hours hunting for the perfect programme.

Paper or app

Paper has one real advantage: nothing distracts you, no notifications. Its drawback is decisive the moment you want to compare: finding what you did four months ago on one specific exercise means leafing through pages, and nobody does it.

An app solves that and calculates what paper cannot: per-exercise history, records, volume by muscle group. The selection criterion is simple and often forgotten: what matters is how fast you can log a set between two others. If it takes more than ten seconds, you will stop. Our full criteria are in the article on choosing a weightlifting app.

Frequently asked questions

Should I log warm-up sets?

Not essential, but at minimum they must be distinguishable from your working sets. Otherwise your volume looks higher than it is, and your week-to-week comparisons lose their meaning.

How do I log a change of machine?

Treat it as a different exercise. Two machines from different manufacturers have neither the same resistance curve nor the same starting weight, so comparing their loads is meaningless. Just note the model or the gym alongside the exercise.

Should I log bodyweight too?

It is useful if you are bulking or in a deficit, provided you look at a weekly average rather than a single reading. Water and gut content swings make one weigh-in nearly impossible to interpret.

What about sessions where I missed my targets?

Log what you actually did, never what you had planned. A log that records intentions rather than performances becomes useless within weeks, and it is the most common mistake there is.

This is exactly the logic behind Musku: logging a set takes two taps, and everything useful for deciding is already there. Weight and rep targets per exercise, a rest timer, free notes per exercise and per session, history and records. The rest is calculated for you, from your estimated 1RM to your volume distribution by muscle group. All you have to do is record what you just did, which happens to be the only thing an app cannot guess.