Percentage-Based Programming

Percentage-based programming sets each set's load as a % of 1RM. It requires a current maximal-strength reference — either a tested 1RM or an estimated 1RM from a rep-max test (see one-rep-max-test) — and then writes every working load relative to it.

Typical intensity → rep mapping (the same continuum as rm-continuum):

Many programs use a training max (TM) — about 90% of true 1RM — as the basis for percentages, so prescribed loads stay submaximal and repeatable (popularized by 5/3/1). Progression is built in by increasing the reference max over a cycle (e.g., +2.5 kg upper / +5 kg lower body per cycle) rather than chasing reps day to day; this dovetails with linear periodization, which is naturally written in percentages.

Strengths: objective, repeatable, easy to autoload across a team; excellent for maximal-strength peaking where precise intensities matter. Limitations: it ignores daily readiness — a fixed % is too heavy on a bad day and too light on a good one — and it drifts as true strength changes between tests. RPE/RIR autoregulation fixes that rigidity, and the two are frequently blended (use percentages as a floor, adjust by RPE).

• Load = % of 1RM; requires a tested or estimated 1RM reference.
• ~85–100% → 1–5 reps (strength); ~67–75% → 8–12 (hypertrophy); <67% → endurance.
• Many plans use a training max ≈ 90% of true 1RM for submaximal, repeatable loads.
• Progress by raising the reference max each cycle, not by chasing daily reps.
• Strength: precise/repeatable; weakness: ignores daily readiness and drifts between tests.

• progressive-overload-application — percentages are one load-prescription scheme.
• autoregulation-rpe-rir — the readiness-sensitive alternative often blended with it.
• double-progression — the no-percentage, rep-driven alternative.
• linear-periodization — typically written in percentages.
• rm-continuum, intensity — the %→reps mapping it relies on.
• one-rep-max-test — supplies the 1RM reference.