
Progressive overload is the whole game. Lift a little more, a little more often, and the body adapts. But the phrase gets thrown around so loosely that most lifters end up tracking the wrong thing, or tracking nothing at all and guessing last week's numbers from memory.
If you train for strength, you don't need a spreadsheet. You need a logging routine that captures the detail that actually drives progress, in the few seconds between sets. This is how to do it on your iPhone, set by set.
What progressive overload actually means at the set level
Total volume (weight times reps across a session) looks tidy in a chart. It also hides everything that matters. Two sessions can hit the same tonnage while one was a grind of singles at your max and the other was junk reps you could have done in your sleep.
Progress lives in the details:
- Load per set. 225 for 5 is not the same session as 225 for 5, then 235 for 5, then 235 for 5.
- Reps at that load. Adding a rep at the same weight is overload. So is adding weight at the same reps.
- Effort (RPE or RIR). A hard set at RPE 9 and an easy one at RPE 6 both count as "sets," but only one tells you to push next week.
- Bar speed and how it felt. A weight that moved slow last week and fast this week is progress even if the number didn't change.
When you only track the headline number, you can't tell a good week from a lucky one. When you track the set, next week writes itself.
Why your memory is a bad progress log
Here's the trap: you finish a set, you're breathing hard, and you decide you'll remember "245 for 5, felt heavy." By the next session you're reconstructing it from a sweaty phone note and vibes.
Guessing leads to two failure modes. You under-load because you can't remember you handled more last time, so you re-run the same numbers for weeks. Or you over-load because you misremember a PR as routine and jump too far, then stall. Neither is a programming problem. Both are a logging problem.
You don't have to re-log last week's numbers. Good tools carry them forward so your only job is to beat them.
A simple iPhone logging routine that takes seconds per set
You don't need a training log with sixteen columns. You need one that survives a real session. Here's the routine:
- Set up the session before you touch a bar. Open the day's workout so your exercises, target sets, and last session's numbers are already on screen. No blank page to fill in mid-workout.
- Log each set as you finish it, not after. One tap logs the set with last session's numbers, and one more tap after the exercise's last set records how many reps you had left. If it takes more than five seconds, the process is too slow and you'll skip it by the third exercise.
- Record the load and the reps for every working set, plus an effort rating for the exercise. Warm-ups can stay out of it. Working sets are the data.
- Note anything abnormal in a word or two. "Left shoulder tight," "belt on," "felt fast." Short enough not to break pace, useful enough to explain a weird result later.
- Review the session before you leave. Ten seconds glancing at what you hit tells you whether you beat last time, and by how much.
The point of logging on a phone instead of a notebook is speed. A paper log can't carry last week's numbers into this week's workout, and it can't do the arithmetic on your trend for you. An Apple Watch on the wrist closes the loop further: log the set from your wrist, keep your hands on the bar between sets.
Turning logged sets into next week's loads
Data you never look at again isn't a system. The routine only pays off if the log tells you what to lift next time.
For a given lift, you want to see the last few sessions in a row and ask one question: did load or reps move up? If your top set was 235 for 5 at RPE 8 last week, this week you have room. Bump to 240, or keep 235 and chase 6 reps. If last week was a true RPE 10 grind, hold the weight and clean up the reps first.
This is where an AI coach earns its place. An AI gym coach that has read your recent sets, PRs and trends can reason over your actual history, not a generic template. It can spot that your squat has crept up while your bench has been flat for three weeks. With Lyfto Pro on iPhone, or on Android, it also names the next weight for each lift. It can factor in how hard your sets felt, and suggest a deload week when two or more big lifts stall or slip together.
Generic programs assume a lifter. Your log describes you.
Use a Strength Score to see overload at a glance
Set-level data is honest but dense. You don't want to re-read six weeks of rows to know if you're moving. A single trend number, like a Strength Score that turns the loads and reps you log into one number relative to your bodyweight, lets you see at a glance whether the trajectory is up, flat, or sliding.
Treat it as a smoke alarm, not the fire. When the score climbs, your set-level logging is doing its job. When it flattens, open the log and find which lifts stalled. The number points; the sets explain.
Build the habit, then let it compound
Progressive overload is a slow argument you win with detail. Log load, reps, and effort every working set. Carry the numbers forward so you're always beating last week instead of re-guessing it. Review before you leave the gym, and let a coach that knows your history help you decide where the next five pounds go.
Do that for a few months and the spreadsheet question answers itself. You won't want one. You'll want the detail that made you stronger, sitting in your pocket, ready before your next set.
Lyfto is a workout tracker and AI gym coach for iPhone and Android, with an Apple Watch app for iPhone: log sets in seconds, track a Strength Score, and train with your crew.