Method

How the paces and the load are calculated

Pace targets come from a recent race, using VDOT. Training load is tracked with CTL, ATL and TSB. This page explains each model and when the plan changes.

Run history and weekly trend in the Runapt app
Split times on a Garmin during a run

The five checks behind a week

VDOT sets the paces. CTL, ATL, and TSB say if the week is too fat. Readiness can cut Thursday. The feasibility check can refuse the race. A bad week is rebuilt before you see it.

VDOT score

VDOT is a running-fitness score from Jack Daniels. One recent race or time trial sets your easy, marathon, threshold, interval, and repetition paces. A soft race gives you soft paces.

Jack Daniels, Daniels' Running Formula. The same VDOT table.

Training load (CTL / ATL / TSB)

CTL is a 42-day exponentially weighted average of daily training stress: longer-term fitness. ATL is the same over 7 days: recent fatigue. TSB is CTL minus ATL. Positive is fresh, negative is carrying fatigue. Each run counts as running TSS: hours × intensity factor² × 100, where intensity factor is your threshold pace divided by the pace you ran.

Banister impulse-response model (1975). After a hard Tuesday the numbers have already moved before Thursday starts.

Readiness score

Readiness starts at 100. Short sleep, HRV below your own 7-day baseline, and a resting heart rate above your baseline each take points off a number you can see. Low number, and Thursday gets cut or moved.

You can see every point that came off. No one else owns the call.

Feasibility check

Before any plan is built, three terms are computed and the largest one wins: the minimum weeks the distance itself requires, the weeks needed to raise your weekly volume at a safe growth rate, and the weeks needed to progress your long run to race-ready. If that total exceeds the time you have, the plan is not built — you are told why, and what would work instead.

The free race reality check runs this exact computation, so it can never clear a race the plan builder would block.

Plan quality checks

Before the generated schedule reaches you, it's validated for zone distribution, weekly load progression, constraint fit (available days, long run day), and taper shape. A plan that fails validation is rebuilt, not shown.

Hard limits: no single run longer than 110% of your longest run in the previous 30 days (115% in peak and taper weeks), and projected acute:chronic load kept at or below 1.30.

Sources

What the models are built on

  • Daniels, J. (2013). Daniels' Running Formula (3rd ed.). Human Kinetics.
  • Banister, E. W., Calvert, T. W., Savage, M. V., & Bach, T. (1975). A systems model of training for athletic performance. Australian Journal of Sports Medicine, 7(3), 57–61.
  • Gabbett, T. J. (2016). The training–injury prevention paradox: should athletes be training smarter and harder? British Journal of Sports Medicine, 50(5), 273–280. doi.org/10.1136/bjsports-2015-095788
  • Frandsen, J. S. B., et al. (2025). How much running is too much? Identifying high-risk running sessions in a 5200-person cohort study. British Journal of Sports Medicine.

Updated

Start with a free plan.

Download Runapt and build your first training week. The free plan has no time limit.

Or start on the web