Programming with VBT
Translating bar-speed data into actual training plans: sets, reps, loads, and the day-to-day adjustments that follow.
Programming with VBT is the discipline of using bar-speed data — both prescriptive (target velocities) and descriptive (measured velocities) — to drive the actual load on the bar. It’s a small, specific change to traditional periodisation that compounds: programs become self-correcting session-to-session instead of frozen against a 6-week-old 1RM.
What it changes about a program
In order of how often they show up:
- Loads follow the velocity, not the percentage. Instead of pinning a working set to a fixed percentage, you pin it to a target velocity and let the load be whatever produces that speed today. On a recovered day the bar gets heavier; on a flat day it gets lighter. The training stimulus equalises across days that would otherwise differ. (Velocity targets come from the velocity zone you’re training, read against the athlete’s own profile.)
- Volume is capped by fatigue, not by rep counts. Instead of a fixed rep target, you run sets to a velocity-loss cutoff. Fresh athletes get the volume; tired athletes don’t accumulate damage.
- Block transitions read from the data. When the load–velocity profile flattens (slope decreases), the block has produced its adaptation; move on. When it doesn’t, the block needs another week.
The shift from %1RM to velocity targets
%1RM is a forecast — a load that should produce a particular effort if the 1RM is current and the athlete is on a normal day. Velocity targets are a measurement — the load that did produce the targeted effort, today, with this body.
Both are useful. %1RM is faster to write and easier for new lifters to follow; velocity targets self-correct for readiness and don’t require recent maxing. Most experienced coaches blend the two: %1RM as the planning tool, velocity targets as the in-session enforcement.
Where %1RM still wins
VBT-driven programming isn’t always the right tool. Where staying with percentages is the cleaner call:
- High-rep accessory work. A lateral raise’s load is too light for velocity to read well, and the precision isn’t worth the data-collection overhead.
- Athletes without a stable velocity profile. New lifters and athletes returning from injury often have noisy velocity data — their profile shifts week-to-week as technique stabilises. Use percentages until the profile holds.
- Skill-dominant lifts. Olympic lift technique work (skill rep counts at moderate loads) is about quality, not load. Velocity is downstream of skill on these; chase the technique, not the number.
Looking for the protocol? Turning these principles into a worked program — block layout, target velocities, the day-to-day adjustments — is its own write-up.