1. Performance — the ground truth

Before anything else, look at the log. Are your working sets progressing? If yes, recovery is adequate. If flat or down, add rest. This is the signal Failure Point reads to prescribe rest.

2. Sleep — the foundation

Sleep is where adaptation happens. A week of poor sleep will stall a HIT program faster than almost anything. If performance stalls and sleep has been short, fix sleep before changing the program.

3. Soreness — context, not verdict

Soreness lags behind recovery and varies by exercise. Use it as a clue — deep, lasting soreness may mean you need another day — but don't let it override the performance signal.

4. Stress and nutrition

Caloric deficit, protein, and life stress all extend recovery needs. If performance stalls and the other signals look fine, check these. Stalls and plateaus →

What Failure Point reads

The logbook reads performance — the objective ground truth — and tells you when to train. The other signals are yours to watch; the app handles the one that matters most. Recovery, the variable →