Your Apple Watch Tracks Minutes and Calories While Lifting — Not Effort. Here's the Fix.

Your Apple Watch does not track effort or intensity for lifting. During a strength workout it records heart rate, active calories, and elapsed time — and that's it. It does not count your reps, log your sets, identify the muscle worked, or measure how hard the set actually was. Even the "Effort" score Apple added in watchOS 11 is a cardio number: it's auto-estimated only for cardio-based workouts, and for strength training there's no automatic estimate at all — you type a guess in yourself. The fix is a different signal the same watch can already read: velocity loss, the slowdown in your reps that tracks fatigue.

You finish a brutal set of Romanian deadlifts, glance at your wrist, and the watch tells you the workout burned 412 calories over 47 minutes and your heart rate peaked at 138. Useful for closing a ring. Useless for the only question that drives growth: did that set get close to failure, or did you leave four reps in the tank? The watch never measured the thing that mattered.

What does an Apple Watch actually record during a lift?

Three things: heart rate, active energy (calories), and duration. That's the whole strength-training picture.

Apple's "Traditional Strength Training" and "Functional Strength Training" workout types wrap your session so the heart-rate sensor isn't throttled, then log your pulse, your estimated calorie burn, and how long you trained. That's genuinely good for what it is — the optical HR sensor and the calorie model are solid.

But notice the resolution. Everything is session-level, not set-level. The watch knows you lifted for 47 minutes. It does not know you did five sets of bench, then four sets of rows, then three drop-sets of curls. It sees one continuous blob of "strength training" with a heart-rate trace laid over it. The structure of your actual workout — the part a coach would care about — is invisible to it.

What does the Apple Watch miss when you lift?

It misses everything that defines a strength session: your reps, your sets, the muscle group you trained, and — most importantly — your effort.

Natively, the Workout app does not count reps or sets in either strength mode. It can't tell a bench press from a bicep curl, because unlike running or cycling, lifting is a varied, stop-start motion with rest intervals that defeat simple pattern-matching. So there's no rep count, no set count, and no muscle-group breakdown unless you bolt on a third-party logging app and type it all in yourself.

Here's the part most people skip past: even with perfect logging, you'd still be missing effort. Knowing you did 5×8 at 80 kg tells you the prescription. It tells you nothing about how hard the eighth rep of the last set was — did you grind it with nothing left, or could you have done five more? Two lifters can run the identical 5×8 with completely different training stimuli — one near failure, one phoning it in — and the watch records them as the same calories and the same minutes. Effort is the variable that separates a productive set from junk volume, and it's exactly the variable the watch throws away.

What is the Apple Watch "Effort" score, and why doesn't it work for lifting?

The Effort score is a cardio-fitness rating, not a muscular-effort rating — and for strength training, the watch doesn't even try to calculate it automatically.

In watchOS 11, Apple introduced a 1-to-10 Effort rating and a 28-day Training Load metric. It sounds like exactly what lifters want. It isn't. In Apple's own words, "popular cardio-based workout types will employ an innovative new algorithm to automatically generate an estimated effort rating," using "a combination of data sources like age, height, and weight, alongside workout data like GPS, heart rate, and elevation." Every input there is a cardiovascular input — pace, pulse, hills, distance.

Then comes the tell. Apple continues: "For workouts where an automatic estimate is not provided — like strength training — users can still enter an effort rating at the end of each workout." Read that again. For lifting, there is no automatic estimate. The score it feeds into your Training Load is a number you typed — the same unreliable gut guess we'll see is often off by several reps. The watch isn't measuring your effort. It's asking you to.

Why are heart rate zones a poor effort proxy for resistance training?

Because heart rate measures the cardiovascular cost of a set, not the mechanical fatigue of the muscle — and in lifting those two can move in opposite directions.

This is the core confusion. Apple's Effort engine, like every HR-zone tracker, is built on a cardio assumption: harder work means a higher, more sustained heart rate. That holds for a 10K. It breaks in the weight room. A heavy triple of squats — a genuinely maximal, near-failure effort — might only nudge your heart rate up briefly, because it's over in 15 seconds and it's an anaerobic, neuromuscular event. A lighter, higher-rep set of leg extensions can drive your pulse higher while leaving the muscle far from failure. Heart rate can literally run lower on the harder, heavier set.

So an HR-derived effort score systematically rewards the wrong thing. It reads "easy" on your most productive heavy work and "hard" on metabolic burners that may be nowhere near failure. That's not a tuning problem — it's the wrong sensor for the question. Heart rate is useful context for systemic fatigue and recovery, but as a standalone gauge of how close a muscle came to failure, it's noise. For more on why your own perception fails here too, see how to actually tell if you're training hard enough.

How does velocity loss fill the gap from the same watch?

Velocity loss measures the one thing that reliably tracks muscular fatigue — how much your reps slow down across a set — and the watch's motion sensors can read a version of it without any new hardware.

The science is clean. As a muscle fatigues, it can't produce force as fast, so your concentric reps physically decelerate, and the magnitude of that slowdown maps onto proximity to failure. In a study of 24 resistance-trained men and women benching at 75% of their 1RM, lifting velocity had dropped about 25% by momentary failure, versus roughly 13% when they stopped one rep short and 8% at three reps short. The slowdown is the fatigue, measurable in a way that "did your heart rate go up" simply isn't.

This is also where training thresholds come from. A 2023 systematic review and meta-analysis on velocity-loss thresholds found that lower velocity-loss cutoffs (roughly 10–20%) suit strength and power goals, while higher thresholds — and never beyond about 40%, where extra fatigue stops buying extra gains — favor hypertrophy. Here's a working map of where common stops land:

The decisive point: that signal comes from an inertial measurement unit (IMU) — an accelerometer and gyroscope — and the Apple Watch has one running at 100 Hz on your wrist. The exact sensor needed to read rep slowdown is already strapped to the arm doing the lifting. Apple just points it at calories instead. For the deeper dive on the thresholds, see what velocity loss % you should stop a set at.

Why does this matter — isn't your own sense of effort good enough?

It isn't, and that's the whole reason an objective read is worth having. Most lifters are quietly bad at judging how close to failure they are.

When trained lifters stop a set believing they're at or near failure, they're often off by about a rep when they're genuinely close — and the error grows the further from failure they are, and the more novice they are. One study of 141 trainees found the most experienced group underpredicted their reps to failure by about 1 to 2, while the least experienced were off by roughly 4 to 5. And it's not just a feel problem: across 2,972 measurements from 19 well-trained lifters, bar velocity explained only about 30% of the variance in their perceived reps in reserve, with the relationship shifting by exercise, load, and how deep into the workout they were. Translation: even velocity isn't a magic universal cutoff, and human perception is worse. Estimating your reps in reserve sharpens the skill — but it's a slow build, and a second opinion helps while you get there.

How to actually get an effort read on your lifts this week

You don't need a $1,500 barbell tracker to start measuring effort instead of minutes. Here's a concrete plan:

1. Stop reading the calorie number as if it means effort. It's a cardio metric — file it next to "steps," not "how hard I trained."
2. Log your sets in a real logging app (StrengthLog, Hevy, Strong). The watch won't count reps or sets natively, so you need a ledger of reps, load, and which muscle.
3. Estimate your reps in reserve on the last set of each exercise, and write it down. It's a guess — the point is to start building the feel and have something to check yourself against.
4. Watch for the objective failure cues the watch ignores: the rep that suddenly takes twice as long to lock out, the bar that visibly slows, the grind. That's velocity loss you can see with your own eyes.
5. Add an effort-measurement layer if you want the number instead of the guess. This is the gap a wrist velocity-loss app fills — turning the rep slowdown your watch already senses into an actual proximity-to-failure score.

Where Riven fits — and where it honestly doesn't

Riven is the fix this article is pointing at: an iOS and Apple Watch app that reads velocity loss from the watch's motion sensors and converts that rep slowdown into a 0–100 failure-proximity score, in real time, per muscle group. No camera, no barbell clip, no extra hardware — the same 100 Hz IMU Apple uses for calories, pointed at the question that actually matters. It also auto-detects your sets and counts reps from the wrist, recovering the structure the native app drops.

Now the honest caveats, because they matter. The wrist signal is a proxy, not lab gear: it reads roughly half the velocity-loss magnitude of a $300-plus barbell linear position transducer at the same physiological fatigue, so Riven calibrates its thresholds to the wrist rather than copying barbell numbers. Velocity is complementary to feel, not a universal cutoff — it explained only about 30% of perceived-RIR variance in trained lifters, and the relationship shifts by exercise and load. And heart rate inside Riven is supporting context, never a standalone failure signal. The right way to think about it is an objective second opinion that beats guessing — which is what almost everyone in the gym is currently doing. For the full picture of how a watch infers failure, see can an Apple Watch detect muscle failure.

FAQ

Does the Apple Watch track effort or intensity for lifting?

No. During strength training the Apple Watch records heart rate, calories, and duration only. The watchOS 11 "Effort" score is auto-estimated for cardio-based workouts; for strength training Apple provides no automatic estimate — you manually type a 1-to-10 rating yourself. It does not measure muscular effort or proximity to failure.

Does the Apple Watch count reps and sets?

Not natively. The Workout app's strength modes don't count reps, log sets, or identify the muscle group — lifting's stop-start motion defeats the simple detection used for running and cycling. You need a third-party app to log sets, and a motion-based app to count reps from the wrist.

Why is heart rate a bad measure of lifting effort?

Because heart rate captures the cardiovascular cost of a set, not muscular fatigue. A heavy, near-failure triple can barely move your pulse, while a lighter high-rep burner spikes it without nearing failure — so heart rate can read lower on the harder set. It's useful recovery context, not an effort gauge.

Can the Apple Watch measure velocity loss?

In principle, yes — the watch has the 100 Hz accelerometer and gyroscope needed to detect how much your reps slow down across a set. Apple just doesn't surface that for lifting. A dedicated app like Riven reads that slowdown, though the wrist signal is a proxy that reads about half the magnitude of a barbell-mounted sensor.

Is velocity loss a perfect cutoff for when to stop a set?

No, and it's important to be honest about that. Velocity loss tracks fatigue well — roughly 25% loss at failure, 13% at 1 rep in reserve — but in trained lifters it explained only about 30% of perceived reps-in-reserve variance, and the relationship shifts by exercise, load, and set number. Treat it as a strong objective second opinion, not a universal law.

Sources

• Apple (2024), watchOS 11 brings powerful health and fitness insights, Apple Newsroom — https://www.apple.com/newsroom/2024/06/watchos-11-brings-powerful-health-and-fitness-insights/
• Apple, Track your training load on Apple Watch, Apple Support — https://support.apple.com/guide/watch/track-your-training-load-apde4c07a6cf/watchos
• Refalo, M.C. et al. (2023), Influence of Resistance Training Proximity-to-Failure, Determined by Repetitions-in-Reserve, on Neuromuscular Fatigue in Resistance-Trained Males and Females, Sports Medicine – Open — https://pmc.ncbi.nlm.nih.gov/articles/PMC9908800/
• Paulsen, G. et al. (2025), Exercise type, training load, velocity loss threshold, and sets affect the relationship between lifting velocity and perceived repetitions in reserve in strength-trained individuals, PeerJ — https://pmc.ncbi.nlm.nih.gov/articles/PMC12360324/
• Jukic, I. et al. (2023), The Acute and Chronic Effects of Implementing Velocity Loss Thresholds During Resistance Training: A Systematic Review, Meta-Analysis, and Critical Evaluation of the Literature, Sports Medicine — https://pmc.ncbi.nlm.nih.gov/articles/PMC9807551/
• Steele, J. et al. (2017), Ability to predict repetitions to momentary failure is not perfectly accurate, though improves with resistance training experience, PeerJ — https://pmc.ncbi.nlm.nih.gov/articles/PMC5712461/