How often should a deload be scheduled?

Every 4-8 weeks is a common range, though IRONSLOG’s progress tracker will also flag a stall outside that schedule if one shows up early.

Can I plan an entire periodized block outside IRONSLOG and import it?

Yes — the plan CSV format includes a week column for overrides, so a full multi-week block can be built in a spreadsheet and imported at once.

What should I look at to judge whether a block worked?

Compare the estimated 1RM trend and weekly training volume from the start of the mesocycle to the end, not just the last session.

Guide

Advanced Workout Programming

Last updated 26 July 2026

Advanced workout programming structures training into blocks — a macrocycle broken into mesocycles of 3-6 weeks, each built around a specific focus and usually ending in a deload. IRONSLOG's plan supports this with per-week overrides, so a planned volume or intensity change doesn't require rebuilding the base schedule.

How do macrocycle, mesocycle and microcycle fit together?

A macrocycle is the full period toward a goal — often months. It's broken into mesocycles, each a 3-6 week block with one focus (hypertrophy, strength, peaking), usually ending in a deload. Each mesocycle is made of microcycles — typically one week — with a repeating pattern of training and rest days. Programming top-down like this keeps a single week's plan connected to a longer-term goal instead of drifting session to session.

How do week overrides in IRONSLOG support this structure?

A plan's week-override system lets a specific week's sets, reps or exercises differ from the base schedule without changing it permanently — useful for a planned deload week, a peaking week before a test, or a deliberate volume wave across a mesocycle. Overrides are also part of the CSV format, so a full periodized block can be built in a spreadsheet and imported.

How do I know a mesocycle actually worked?

Compare the estimated 1RM trend and weekly training volume at the end of the block against where they started. A mesocycle that ends without a clear estimated 1RM or volume trend upward is a signal to change something in the next block, not just repeat it.

Structuring a periodized block in IRONSLOG:

Define the macrocycle goal. What are you training toward, and over roughly how many months?
Break it into mesocycles. Plan 3-6 week blocks, each with one focus — volume, intensity, or a peak.
Plan the microcycle pattern. Decide the weekly repeating structure of training and rest days for the block.
Use week overrides for planned variation. Schedule volume or intensity waves within a mesocycle without rebuilding the base plan.
Schedule a deload every 4-8 weeks. End most mesocycles with a lighter week before starting the next block.
Review the trend at block end. Check the estimated 1RM and weekly volume trend before deciding what the next mesocycle should change.

Key takeaways

A macrocycle is built from mesocycles (3-6 weeks), each made of repeating microcycles (usually one week).
Week overrides let a specific week deviate from the base plan without permanently changing it.
Overrides are part of the CSV plan format, so a full block can be built in a spreadsheet and imported.
Review the estimated 1RM and volume trend at the end of a block before planning the next one.