Volume, concentration, quality, and recovery tradeoffsLive current inputs
Health & Fitness
Running Training Scenario Calculator
Compare three running-week scenarios by distance, long-run concentration, quality volume, acute load change, estimated session load, and recovery reserve without declaring the highest-volume option the winner.
Balanced scenario distance—
Balanced load change—
Balanced long-run share—
Balanced quality share—
Recovery reserve—
Distance per session—
Constraint-led scenario—
Primary tradeoff—
Three-scenario terrain
Volume, concentration, quality, and recovery tradeoffs
Each scenario occupies its own vertical lane. Distance grows from conservative to aggressive while risk-colored markers expose where long-run concentration and recovery reserve change.
Scenario decision matrix
Conservative, balanced, and aggressive week comparison
The matrix reports arithmetic and constraint flags without turning a single score into a coaching decision.
| Scenario | Weekly distance | Change vs baseline | Long-run share | Quality share | Recovery flag |
|---|
Scenario setup
Keep the assumptions constant except for the choice being tested
- Use a genuinely stable recent distance rather than one peak week.
- Enter the desired week before deciding whether it is feasible.
- Keep long-run and quality requests visible across all cases.
- Record current sleep and soreness without optimistic adjustment.
- Choose the scenario by constraints and purpose, not by the largest number.
Comparison discipline
A fair scenario test changes one decision at a time
If mileage, long run, quality work, frequency, and recovery assumptions all change together, the reason one scenario looks better becomes impossible to explain.
The model therefore changes total distance while preserving the requested concentration and current recovery evidence. The result is a tradeoff map, not a universal safe-growth rule.
Scenario construction
Vary volume while preserving the same practical constraints
The conservative case closes half the gap from baseline to goal, the balanced case closes three quarters, and the aggressive case uses the request. Long and quality shares are recalculated for each case; recovery context does not improve simply because mileage is lower.
Detailed calculation process and general formulas
d_c = d_base + 0.50(d_goal - d_base)d_b = d_base + 0.75(d_goal - d_base)d_a = d_goalchange_j = 100(d_j - d_base) / d_basereserve = 10(sleep / 8) - sorenessSymbols, meanings, and units
- d_base
- recent stable weekly distancekm/week
- d_goal
- requested distancekm/week
- d_j
- scenario weekly distancekm/week
- sleep
- recent average sleephours/night
- soreness
- entered soreness score0-10
Decision boundary
What can disqualify the aggressive option
The highest-volume case loses priority when concentration or recovery becomes the binding constraint.
Acute change
—A large step from the stable baseline is shown explicitly rather than hidden inside the weekly total.
Concentration
—Long-run and quality shares reveal whether stress is being packed into too few sessions.
Recovery evidence
—Poor sleep, high soreness, pain, or illness should override a favorable arithmetic comparison.
Decision takeaway: Prefer the smallest scenario that accomplishes the current training purpose with credible recovery.
Applied decisions
When the middle scenario is not automatically correct
Large long run inside modest mileage
The conservative case reduces weekly distance but retains a 14 km long run.
What the result clarifies: Long-run concentration can worsen even while total mileage falls.
Good sleep with high soreness
Sleep appears adequate but soreness remains elevated.
What the result clarifies: The recovery reserve prevents one reassuring input from erasing another.
Worked default scenario
Current-input substitution and reconciliation
Method references
Evidence used to frame this specific model
Scope and limitations
Scenario calculations are descriptive planning aids. Evidence does not support a universal mileage-change threshold that guarantees safety. Pain, gait change, illness, prior injury, terrain, intensity, and individual history require separate judgment.
Running Training Scenario Calculator | Conservative, Balanced, and Aggressive Weeks FAQ
Is the balanced scenario the recommendation?
No. It is an intermediate comparison case; constraints and training purpose determine which option is appropriate.
Why not use an acute-to-chronic workload ratio?
Simple ratios have important conceptual and evidentiary limitations, so the model reports the direct baseline change instead.
Can a lower-mileage case be more concentrated?
Yes. A fixed long run or quality session occupies a larger share of a smaller week.
Does recovery reserve predict injury?
No. It is a transparent planning signal from entered sleep and soreness, not a validated probability model.