Load change, pain, recovery, injury history, and session densityLive current inputs
Health & Fitness
Running Training Risk Screening Calculator
Screen a proposed running week using load change, pain, prior injury, sleep, soreness, hard-session density, and consecutive running days while keeping pain/function gates separate from a planning score.
Planned load change —
Pain/function gate —
Load-change contribution —
Recovery contribution —
History contribution —
Hard-day density contribution —
Planning caution score —
Suggested planning action —
Running-risk factor radar
Load change, pain, recovery, injury history, and session density
Five independent axes prevent one reassuring input from hiding a strong pain or recovery signal; the pain/function gate remains visually separate.
Factor-by-factor screen
What triggered the planning score
Every contribution is visible with its entered evidence, points, and practical response.
| Factor | Entered evidence | Points | Band | Planning response |
|---|
Screen setup
Use current evidence and do not average away pain
- Compare the plan with a representative recent average.
- Enter pain honestly and mark altered gait or daily function separately.
- Include relevant prior injury even if current pain is low.
- Use actual sleep and persistent soreness, not the desired values.
- Reduce or seek assessment when the pain/function gate is triggered.
Why a radar instead of one ratio
Running setbacks are not explained by mileage change alone
A stable distance can still be poorly tolerated when pain, sleep loss, prior injury, or dense hard sessions change. Conversely, a volume increase is not an injury diagnosis.
The radar preserves multiple dimensions while the separate pain/function gate prevents a low composite score from overriding a meaningful symptom.
Transparent screening method
Apply the pain/function gate before combining planning factors
Load change contributes points gradually; pain, lost function, prior injury, sleep, soreness, and hard-day density remain separate. The total is a planning aid, not an injury probability.
Detailed calculation process and general formulas
Load change = (Planned - Recent) / Recent × 100Load points = clamp(max(Load change, 0) × 1.2, 0, 30)Recovery points = sleep deficit points + soreness pointsDensity points = hard-session points + consecutive-day pointsTotal = min(100, load + pain + recovery + history + density)Symbols, meanings, and units
- Planned
- distance intended for the coming weekkm/week
- Recent
- representative recent stable averagekm/week
- Load points
- capped contribution from positive distance changepoints
- Recovery points
- sleep and persistent-soreness contributionpoints
- Total
- non-diagnostic planning caution score0-100
Action hierarchy
Use the strongest signal to set the next step
The total score summarizes context, but pain and function remain independent decision gates.
Pain/function gate
—Altered gait, daily-function loss, or substantial pain supports reducing load and appropriate assessment.
Recovery correction
Sleep and persistent soreness may justify replacing hard running with recovery.
Load redesign
—Reduce concentration by adjusting total distance, hard sessions, or consecutive days.
Decision takeaway: Use the score to organize a review, never to prove that a plan is safe.
Follow-up log
What to track after changing the plan
- Pain during and after running
- Morning function and gait
- Sleep duration and quality
- Session RPE
- Surface, elevation, and intensity
Applied decisions
Why multidimensional screening changes the plan
Mileage increase with good recovery
Distance rises moderately while pain, sleep, and soreness remain favorable.
What the result clarifies: The radar shows a load signal without inventing an injury prediction.
Stable mileage with altered gait
Distance is unchanged but pain affects running form and daily function.
What the result clarifies: The pain/function gate takes priority over the low load-change score.
Worked default scenario
Current-input substitution and reconciliation
Method references
Evidence used to frame this specific model
Scope and limitations
This screen does not diagnose an injury or predict individual injury probability. Seek appropriate clinical assessment for significant or worsening pain, swelling, inability to bear weight, altered gait, neurological symptoms, trauma, or persistent functional loss. Simple mileage rules and workload ratios have important evidence limitations.
Running Training Risk Screening Calculator | Load, Pain, and Recovery FAQ
Is a low score proof that I can run?
No. Symptoms, function, medical context, and professional advice take priority.
Why include prior injury?
Relevant history changes the context even when the current week looks ordinary.
Can unchanged mileage still be risky?
Demand can change through pace, hills, surface, hard-session density, sleep, and pain.
Why cap load-change points?
The calculator avoids letting one numeric factor dominate every other dimension.