Setting Baselines for the Goal→Program Engine

Assessment exists to drive programming. Each baseline result becomes a specific input for the goal→program engine (program-design-process):

• Strength tests → starting loads. An estimated 1RM sets the %1RM loads for prescribed rep ranges (intensity); e.g., a 200-lb estimated bench 1RM → ~150 lb (75%) for sets of ~10.
• Cardiorespiratory result → intensity zones. VO2max/category plus HR data set target HR zones or paces (%HRR/%HRmax) and a sensible starting weekly aerobic volume.
• Body composition/girths → realistic targets. Combined with energy needs, they frame a safe rate of change (e.g., fat loss) and the metrics to monitor.
• Mobility/balance limiters → corrective priorities added to the warm-up/program.
• Norm category → goal calibration. A "poor" result with large headroom vs. an "excellent" result near ceiling shapes how aggressively to progress.

Make goals measurable (SMART): tie each goal to a re-testable metric and target value with a timeframe (e.g., "+3 reps on the push-up test in 8 weeks," "waist −4 cm in 12 weeks," "1.5-mile run −60 s in 12 weeks"). These targets define the re-test (retest-cadence) and the progression rules (progressive-overload-application).

• Estimated 1RM → %1RM training loads for the prescribed reps.
• Cardiorespiratory result + HR → target HR/pace zones and starting aerobic volume.
• Body comp/girths → safe rate-of-change targets and monitoring metrics.
• Mobility/balance limiters → corrective priorities in the program.
• Write SMART, re-testable goals (metric + target + timeframe) that define re-tests and progression.

• baseline-assessment-battery — produces the inputs.
• estimated-1rm / cardiorespiratory-norms — specific baselines used.
• program-design-process / progressive-overload-application — the engine that consumes baselines.
• intensity — how %1RM loads are applied.
• what-to-log-strength — logging baselines and targets.