Readiness monitoring with bar speed.

Every hard block eventually produces the athlete who looks fine, says they feel fine, and underperforms when it counts. The signal was there two or three weeks earlier. Nobody was measuring the right thing at the right frequency.

The practical requirement for a readiness marker is brutal: it has to be objective, cost nothing in fatigue, take under a minute, and work on twenty athletes at once. Questionnaires are subjective. HRV needs protocol discipline athletes rarely keep. Force plates need infrastructure and floor time. Velocity at a fixed load needs a sensor and thirty seconds.

At a fixed submaximal load, mean concentric velocity is a repeatable, highly individual number. It reflects the force the athlete can express right now, which is exactly what fatigue degrades first — before top-set performance falls off, and long before an outcome measure like a missed lift tells you.

Two conditions make it valid: identical load and identical intent. Get those right and the number is trustworthy. Get either wrong and you are reading noise.

1. One lift the athlete trains at least twice a week — usually back squat or bench press.
2. One reference load, 60 to 70 percent of the last known max, rounded to something loadable in seconds. Fixed for the whole block.
3. Two reps, maximum intent, every session, during the warm-up. Record the faster one.
4. Two weeks before you interpret anything. Roughly six data points gives you a personal baseline and, more importantly, a sense of that athlete's normal day-to-day spread.

Use a rolling seven-day average as the comparison point, not the single best session ever recorded. Comparing to a personal best guarantees that most days look like fatigue.

Bands, not thresholds. An athlete whose normal spread is ±7 percent needs wider bands than one who lives inside ±3 percent, and after a month of data you will know which is which.

A sustained rise is what a working block looks like: the same load moving faster because the athlete got stronger. It is also a prescription, not just a compliment — their programmed loads are now too light.

When the reference velocity has been up 5 percent or more for two weeks, re-estimate the max. Either run a load-velocity profile or rebuild the block's loads off the new estimate. Coaches are quick to react to declines and slow to react to improvements, and that asymmetry quietly costs athletes months.

On a roster, the individual number matters less than the pattern across the group.

• One athlete down, everyone else normal — individual problem. Sleep, school, work, illness, or something outside training.
• Most of the group down together — programming problem. Your block is heavier or longer than the group can absorb; deload the group, not the athlete.
• A group down every Monday, fine by Wednesday — schedule problem. Something in the weekend is eating the first session of the week.

This distinction is the reason the Coach Portal groups athletes: the readiness pattern of the group is what tells you whether to fix a person or fix the plan.

1. Warm up to the reference load. Two reps, maximum intent.
2. Compare to the rolling seven-day average.
3. Pick one of the four responses in section 04.
4. Train.
5. Once a week, read the group pattern rather than the individuals.

It is deliberately boring. Boring is what gets done in week nine, which is when readiness monitoring actually pays.

Bar speed at a reference load tells you what the athlete can express today. It does not tell you why, it does not diagnose injury, and it does not replace asking the question. It is a flag that says "look here" — the coaching still happens in the conversation that follows.