Deload Trigger Screen

Flag caller-defined recovery or load conditions for a deload discussion.

Description

A deload discussion screen counts low recovery and excessive load conditions.

A deload discussion screen counts low recovery and excessive load conditions. Either strict trigger produces the suggested flag.^[1]

Flag caller-defined recovery or load conditions for a deload discussion.

When to use Deload Trigger Screen

Use this tool to flag caller-defined recovery or load conditions for a deload discussion.

Prepare the measured movement, timing, load or preassigned score requested. Keep protocols, units, paired measurements and caller-selected thresholds consistent.

How to use Deload Trigger Screen and understand its results

Prepare the measured movement, timing, load or preassigned score requested. Keep protocols, units, paired measurements and caller-selected thresholds consistent.
Enter recoveryScore, minimumRecoveryScore, recentLoad, maximumLoad using the field table and calculation rules, then run the tool.
Read triggerCount, deloadSuggested. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
recoveryScore	Recovery score	number	Required
minimumRecoveryScore	Minimum recovery score	number	Required
recentLoad	Recent load	number	Required
maximumLoad	Maximum load	number	Required

Enter nonnegative scores, loads and caller cutoffs. Return count 0–2 and flag; equality triggers neither comparison.

count=(recovery<minimum)+(load>maximum); suggested=count>0

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
triggerCount	Trigger count	number
deloadSuggested	Deload suggested	boolean

json

{
  "input": {
    "recoveryScore": 3,
    "minimumRecoveryScore": 5,
    "recentLoad": 120,
    "maximumLoad": 100
  },
  "output": {
    "triggerCount": 2,
    "deloadSuggested": true
  }
}

Limitations and assumptions

This is not an automatic training prescription, clinical assessment or validated recovery model.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.

Alternative or Complementary methods

Use HRV Rolling Baseline: Compare current HRV with the prior seven-day mean and caller tolerance. For a complementary task, use Acute Chronic Workload Ratio: Screen acute-to-chronic workload ratio using caller-supplied zone boundaries.

References

Deload Trigger Screen — tool.io

Similar or alternative tools

HRV Rolling Baseline
Compare current HRV with the prior seven-day mean and caller tolerance.
Acute Chronic Workload Ratio
Screen acute-to-chronic workload ratio using caller-supplied zone boundaries.