Skip to content

Key takeaways

What to take from this

  1. 01Start from the current complex-training pair before inventing a velocity target.
  2. 02Write clear cutoff velocities and stop bands with which pair they govern on the program.
  3. 03Keep velocity-based training separate from after-the-fact technique-cue logging, meet-day attempt selections, block load targets alone, mesocycle structures alone, macrocycle maps alone, periodization frameworks alone, block-periodization schemes alone, undulating-periodization plans alone, daily undulating-periodization rotations alone, linear-periodization ladders alone, reverse-periodization ladders alone, conjugate day maps alone, wave-periodization load waves alone, concurrent-periodization quality maps alone, polarized distributions alone, flexible keep/swap/delay week adjustments alone, same-session reactive swaps alone, dual-factor volume and intensity charts alone, ATR phase charts alone, residual phase-potentiation sequences alone, post-activation contrast pairs alone, French-contrast four-station stacks alone, complex-training pairs alone, autoregulated next-session targets alone, taper-block load targets, peaking-block load targets, deload-week notes, and progressive-overload charts.

Start from the current complex-training pair

A useful velocity target starts after the complex-training pair is already written. Read those heavy-then-plyo couples for which French-contrast sequences they simplify and how long the rest intervals last, then decide which bar-speed cutoff and stop band should govern the heavy station. This is a reading method for building the velocity target clients open—not software evaluation of technique-cue logging tools, meet-day tools, block-load tools, mesocycle tools, macrocycle tools, periodization tools, block-periodization tools, undulating tools, DUP tools, linear tools, reverse tools, conjugate tools, wave tools, concurrent tools, polarized tools, flexible tools, reactive tools, dual-factor tools, ATR tools, phase-potentiation tools, post-activation tools, French-contrast tools, complex-training tools that mainly write pairs without velocity bands, autoregulation tools, taper or peaking tools, deload tools, or progressive-overload tools that mainly chart planned-vs-performed load.

Keep the velocity cutoff explicit

If the only plan after the complex-training pair is somehow into faster or slower bar speed, insert the cutoff velocity, stop band, which heavy station the band governs, and which complex-training pair drove the target so productive contrast sessions do not turn into unstructured improvisation across the block. Prefer readable velocity-based targets over vague bar-speed notes. Ignore the urge to rewrite accessories and session order when only the velocity band needs an update.

Write the velocity target on the program before the next hard session

Even clean velocity cutoffs fail if clients still open bare complex-training pairs with no bar-speed band. Put the velocity target beside the complex-training pair on the assigned program, and note which heavy-then-plyo couple drove the prescription so next review can judge whether the band still fits.

Keep the Lyfta nudge natural

When the velocity target is clear, a product like Lyfta Coach helps if assigned programs and individual workout logs stay in the same place coaches already edit.

Where Lyfta fits

Trust Lyfta Coach when velocity cutoffs must stay editable beside complex-training pairs and logs.

Try Lyfta Coach

Related blog posts

How to adapt cloned templates from workout logs
How to apply autoregulated targets from workout logs
How to build back-off sets from top sets