Skip to main content
Back to Updates
NewsJune 2, 2026

Program Guides Are More Actionable

Program resources now explain more of the actual routine shape, connect to the right calculators, and make the next Protocol setup path clearer.

Shipped

  • Expanded program pages beyond cautious summaries into more practical guides.
  • Added clearer structure, progression, setup, common-mistake, FAQ, and source sections across the current program library.
  • Added calculator links to help choose starting loads, training maxes, warm-ups, plates, RPE targets, volume checks, and deload targets.
  • Added app-fit pages for running GZCLP and 5/3/1 without relying on a spreadsheet as the training interface.
  • Grouped the program hub by training job: linear progression, strength blocks, hypertrophy splits, and decision guides.

Why

A program guide that never explains the program is not very useful.

There is a legal and source boundary here, and it matters. Protocol did not create GZCLP, 5/3/1, StrongLifts, Starting Strength, nSuns, PHUL, Candito, Bullmastiff, or Greyskull LP. The source owner or original material should still be the final reference.

At the same time, a lifter searching for a routine needs enough structure to make a decision. They need to know what the week looks like, which number to enter first, what happens when a set fails, where a spreadsheet helps, and where it starts getting in the way.

The program pages now answer more of that practical workflow, then point to calculators and Protocol setup paths where the app can help. The aim is simple: less tab-switching between a wiki page, a calculator, a spreadsheet, and the workout itself.

Notes

  • Built-in preset language is limited to routines the codebase already supports.
  • Manual setup pages do not pretend the app can import spreadsheet values.
  • Comparison-style program pages stay under Resources, not the app comparison section.
  • Calculator links are crawlable links, not hidden product shortcuts.

Next

  • Keep deepening the program pages where real search intent exists.
  • Use calculator clicks and program CTA clicks to understand which routines deserve more work.
  • Keep the source boundary visible without making the pages too vague to be useful.