Skip to content

Key takeaways

What to take from this

  1. 01Start from the current mesocycle structure before inventing a season-long macrocycle map.
  2. 02Write a clear macrocycle map and which mesocycles or blocks it covers on the program.
  3. 03Keep macrocycles separate from after-the-fact technique-cue logging, meet-day attempt selections, post-meet block load targets, off-season block load targets, base-building block load targets, intensification block load targets, deload block load targets, accumulation block load targets, realization block load targets, mesocycle structures alone, taper-block load targets, peaking-block load targets, deload-week notes, and progressive-overload charts.

Start from the current mesocycle structure

A useful macrocycle starts after the mesocycle structure is already written. Read that multi-week map for the main lift, then decide the season or annual macrocycle map clients should use, and which mesocycles or blocks carry that season plan. This is a reading method for building the season rule clients open—not software evaluation of technique-cue logging tools that mainly capture form notes after sets without requiring a macrocycle map on the program, not meet-day tools that mainly write a meet-day attempt selection without a season rule, not post-meet tools that mainly write a post-meet block load target without a season rule, not off-season tools that mainly write an off-season block load target without a season rule, not base-building tools that mainly write a base-building block load target without a season rule, not intensification tools that mainly write an intensification block load target without a season rule, not deload tools that mainly write a deload block load target without a season rule, not accumulation tools that mainly write an accumulation block load target without a season rule, not realization tools that mainly write a realization block load target without a season rule, not mesocycle tools that mainly write a mesocycle structure without a season rule, not taper tools that mainly write a taper-block load target without a season rule, not peaking tools that mainly write a peaking-block load target without a season rule, not deload-week note tools that mainly park short effort notes on lighter sessions without a season map, and not an overload chart that still leaves the macrocycle blank.

Keep the macrocycle map and mesocycle coverage explicit

If the only plan after the mesocycle is year somehow into the next season, insert the macrocycle map, which mesocycles or blocks must honor it, and what clients do when recovery, sleep, or a missed block changes that handoff so productive mesocycles do not turn into unstructured season guesses. Prefer readable macrocycles over vague year-somehow notes. Ignore the urge to rewrite accessories and session order when only the main-lift season map needs an update.

Write the season rule on the program before the handoff

Even a clean macrocycle fails if clients still open a bare mesocycle structure. Put the macrocycle map beside the mesocycle structure on the assigned program, and note which mesocycle drove the prescription so next review can judge whether the season plan still fits.

Keep the Lyfta nudge natural

When the season rule 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

Lyfta Coach can help when setting macrocycles from mesocycles needs the assigned program beside the workout logs coaches already review.

Try Lyfta Coach