VBT for hypertrophy
Velocity loss is a sharper tool for hypertrophy programming than rep counts.
VBT for hypertrophy is the use of bar-speed data — specifically velocity loss — to dose proximity-to-failure for muscle growth, in place of a subjective rep-in-reserve guess. Most hypertrophy programming is volume + proximity-to-failure programming, and the traditional way to dose proximity-to-failure is reps in reserve: guess how many reps were left in the tank, leave 1–3 most of the time, occasionally go to failure. VBT replaces the guess with a measurement. Velocity loss is the percentage drop in bar speed from the fastest rep of a set to the current one, and it tracks proximity-to-failure tighter than any subjective scale.
Why this matters for hypertrophy
The prevailing working model is that the hypertrophy stimulus tracks closely with mechanical tension during reps where the muscle is producing force at high motor-unit recruitment — though how cleanly that maps to “effective reps” is still debated. Rep counts are a proxy for this; velocity loss is a proxy for when those reps are happening:
- The first few reps of a set produce force fast — fatigue hasn’t accumulated, so motor unit recruitment isn’t maxed out. They’re sub-stimulating for hypertrophy.
- The middle reps of a set produce force more slowly. Recruitment is thought to climb as fatigue builds. These are the effective reps for hypertrophy.
- The final reps before failure produce force very slowly. Recruitment is high but the rep is dragging; these reps fatigue everything else (tendons, CNS, recovery capacity) without adding much to the hypertrophy signal.
Velocity loss puts a number on which phase of the set you’re in. A 20 % loss says you’re in the middle, harvesting effective reps. A 40 % loss says you’re past it, accumulating cost without proportional gain.
Cutoffs by goal
The cutoff you pick decides how deep into that fatigue curve each set runs — a higher cutoff buys more effective reps at a steeper recovery cost. The right number isn’t a constant: it depends on the lift’s recovery cost, the rest of the program, and the athlete’s training age. A heavy compound run at 30 % v-loss is a different week from a lateral raise run at 30 % v-loss; the math is the same, the stimulus isn’t. See the velocity-loss guide for the cutoffs by goal.
Where it doesn’t apply
Lifts where velocity is too noisy to read reliably — single-arm dumbbell work, machine lifts where the lever arm changes through the rep, isolation work at low loads — don’t benefit from VBT-driven hypertrophy programming. The set-by-set variability of the velocity reading swamps the signal.
For those movements, traditional methods (RIR, rep counts, sets to fatigue) still work fine. VBT is most useful for the heavy compound lifts in a hypertrophy block — the squat, the bench, the row — where it can drive precise volume dosing on the lifts that produce most of the cumulative recovery cost. Fitting that into a full plan is a programming question.
Looking for the protocol? Wiring velocity loss into a hypertrophy block — cutoffs per lift, weekly volume, how it sits alongside accessory work — is its own write-up.