Skip to content

Key takeaways

What to take from this

  1. 01Start from the current conjugate day map before inventing a wave-periodization load wave.
  2. 02Write a clear wave-periodization load wave and which weeks or blocks it covers on the program.
  3. 03Keep wave periodization 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, taper-block load targets, peaking-block load targets, deload-week notes, and progressive-overload charts.

Start from the current conjugate day map

A useful wave-periodization load wave starts after the conjugate day map is already written. Read that max-effort, dynamic-effort, and repeated-effort map for the main lift, then decide the wave-periodization load wave clients should use, and which weeks or blocks carry that wave. This is a reading method for building the wave clients open—not software evaluation of technique-cue logging tools that mainly capture form notes after sets without requiring a wave on the program, not meet-day tools that mainly write a meet-day attempt selection without a wave, not block-load tools that mainly write a single block load target without a wave, not mesocycle tools that mainly write a mesocycle structure without a wave, not macrocycle tools that mainly write a macrocycle map without a wave, not periodization tools that mainly write a periodization framework without a wave, not block-periodization tools that mainly write a block-periodization scheme without a wave, not undulating-periodization tools that mainly write an undulating-periodization plan without a wave, not daily undulating-periodization tools that mainly write a daily undulating-periodization rotation without a wave, not linear-periodization tools that mainly write a week-to-week linear-periodization ladder without a wave, not reverse-periodization tools that mainly write a reverse-periodization ladder without a wave, not conjugate-periodization tools that mainly write a conjugate day map without a wave, not taper tools that mainly write a taper-block load target without a wave, not peaking tools that mainly write a peaking-block load target without a wave, not deload-week note tools that mainly park short effort notes on lighter sessions without a wave, and not an overload chart that still leaves the wave blank.

Keep the wave and week coverage explicit

If the only plan after the conjugate map is roll the wave somehow into the next block, insert the wave-periodization load wave, which weeks or blocks must honor it, and what clients do when recovery, sleep, or a missed week changes that wave so productive conjugate maps do not turn into unstructured wave guesses. Prefer readable wave periodization over vague roll the wave somehow notes. Ignore the urge to rewrite accessories and session order when only the main-lift wave needs an update.

Write the wave on the program before the next block

Even a clean wave-periodization load wave fails if clients still open a bare conjugate day map. Put the wave-periodization load wave beside the max-effort, dynamic-effort, and repeated-effort days on the assigned program, and note which conjugate map drove the prescription so next review can judge whether the wave still fits.

Keep the Lyfta nudge natural

When the wave 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

Open Lyfta Coach when a wave-periodization load wave must stay editable beside the conjugate day map and logs coaches already open.

Try Lyfta Coach