Programming with velocity-loss cutoffs.

A fixed rep target assumes every athlete arrives with the same capacity every day. They do not. Three sets of eight is a light day for a fresh athlete and a grinder for a tired one — the same prescription delivers two different training stimuli, and you cannot tell which one you gave until the results show up weeks later.

Reps to failure has the opposite problem: it standardises the endpoint but not the cost, and it accumulates fatigue nobody asked for.

The first rep of a set at maximum intent is the fastest one. As fatigue builds within the set, velocity falls. A velocity-loss cutoff ends the set when the current rep has dropped a defined percentage below that first rep.

Because the decay tracks fatigue directly, the same cutoff produces the same physiological cost across athletes and across days — while the rep count moves freely. You stop programming reps and start programming fatigue.

The interesting finding is at the ends: modest cutoffs produce strength gains comparable to much longer sets at a fraction of the fatigue, and very large cutoffs buy size at a recovery price that compounds across a week.

Choose it once per block, per slot, and leave it alone. Four inputs:

• Goal of the block. Strength tightens the cutoff, size widens it.
• Proximity to competition. Inside four weeks, nothing above 20 percent.
• Training age. Newer athletes decay erratically and need wider bands and more coaching on intent.
• Weekly load. Multiple hard sessions per week means smaller cutoffs; the fatigue is additive whether you measured it or not.

If you cannot decide, use 20 percent. It is the most forgiving choice and it is a real prescription, unlike "three sets of eight, maybe ten if it feels good".

1. Set the load from the athlete's profile, or from the target velocity for the slot.
2. Prescribe sets, not reps. "4 sets, 20% cutoff" — total reps will vary and that is the design.
3. Give a rep ceiling if you need session-time certainty: "4 sets, 20% cutoff, max 10 reps".
4. Demand maximum intent on rep one. The whole set is measured against it, so a sandbagged first rep breaks the entire mechanism.
5. Keep rest constant. Rest is what you traded away for control over fatigue; do not autoregulate it too.

In the Coach Portal you attach the cutoff to the exercise on the workout, so each athlete's app calls the set at the right point without anyone doing arithmetic mid-set.

Back squat, 140 kg, 20 percent cutoff. First rep: 0.62 m/s. The cutoff sits at 0.50 m/s.

• Rep 1: 0.62 — continue
• Rep 2: 0.60 — continue
• Rep 3: 0.57 — continue
• Rep 4: 0.54 — continue
• Rep 5: 0.51 — continue
• Rep 6: 0.48 — below cutoff, set ends

Five clean reps. On a fresh day the same athlete at the same load might get eight; two days after a hard session, three. The dose held constant while the rep count told you what kind of day it was — which is information a rep target throws away.

Cutoffs are the easiest part of velocity to deploy at scale, because the set coaches itself. Twenty athletes can run different loads on the same cutoff and finish inside the same window, and the reps each of them completed becomes a fatigue report you did not have to collect.

One habit worth building: at the end of the week, look at reps-per-set by athlete. Whoever is drifting down week over week at the same load is fatiguing, whatever their warm-up velocity said.

• Easing into the set. A slow first rep raises the cutoff and turns the set into failure training.
• Changing the cutoff week to week. Then you cannot attribute any result to anything.
• Using a tight cutoff and adding sets to compensate. That reintroduces the fatigue you just designed out.
• Applying it to everything. Main lifts and their primary variations. Accessories do not need it.
• Treating reps as a performance score. Fewer reps at the same load is data, not failure. Say that out loud to the athlete once and it stops being an issue.