Key Takeaways
- This tool is built for scenario planning, not one-time guessing.
- Use real baseline inputs before testing optimization scenarios.
- Interpret outputs together to make stronger decisions.
- Recalculate after meaningful context changes.
- Consistency and execution quality usually beat aggressive one-off plans.
What This Calculator Measures
Plan weekly training zone distribution based on total training hours and target intensity mix.
By combining practical inputs into a structured model, this calculator helps you move from vague estimation to clear planning actions you can execute consistently.
This calculator distributes weekly hours across zones to support structured training planning.
How the Calculator Works
Zone hours = total hours × zone %Zone 1: easy base time.
Zone 2/3: tempo and threshold.
Zone 4: high intensity.
Worked Example
- 8 hours per week at 60% Zone 1 equals 4.8 hours.
- Zone 2 and 3 allocate tempo and threshold.
- Zone 4 is short but intense.
How to Interpret Your Results
| Result Band | Typical Meaning | Recommended Action |
|---|---|---|
| Zone 1 60%+ | Low intensity heavy. | Great for endurance base. |
| Zone 1 50–59% | Balanced. | Mix of base and quality. |
| Zone 1 40–49% | High intensity mix. | Monitor fatigue. |
| Zone 1 < 40% | Intensity heavy. | Risk of burnout. |
How to Use This Well
- Enter weekly training hours.
- Set zone percentages.
- Select plan type.
- Review zone hours allocation.
- Adjust zones to match goals.
Optimization Playbook
- Increase Zone 1: build aerobic base.
- Limit Zone 4: avoid overtraining.
- Adjust plan type: match training phase.
- Track fatigue: modify mix weekly.
Scenario Planning Playbook
- Baseline: current zone mix.
- More base: add 10% to Zone 1.
- Race build: raise Zone 3 by 5%.
- Decision rule: keep Zone 4 under 10%.
Common Mistakes to Avoid
- Letting zones sum above 100%.
- Overloading high intensity.
- Ignoring recovery weeks.
- Using the same mix year-round.
Implementation Checklist
- Set weekly hours.
- Allocate zone percentages.
- Plan workouts per zone.
- Review weekly fatigue.
Measurement Notes
Treat this calculator as a directional planning instrument. Output quality improves when your inputs are anchored to recent real data instead of one-off assumptions.
Run multiple scenarios, document what changed, and keep the decision tied to trends, not a single result snapshot.
FAQ
What is a polarized plan?
High proportion of low intensity with small high-intensity blocks.
How should zones add up?
They should total 100%.
Can I change zone percentages?
Yes, adjust based on training goals and phase.
Related Calculators
Frequently Asked Questions
How accurate are the results?
The Training Zone Distribution applies a standard formula to your inputs — accuracy depends on how precisely you measure those inputs. For planning and estimation, results are reliable. For high-stakes or professional decisions, cross-check the output with a domain expert or primary source.
How do environmental conditions affect the result?
Temperature, altitude, humidity, wind, and playing surface all affect athletic performance. Running pace at altitude (>5,000 ft) is typically 5-10% slower due to lower oxygen partial pressure. Heat adds ~20-30 sec/mile for each 10°F above 60°F. Account for conditions when comparing or planning.
How should I interpret the Training Zone Distribution output?
The result is a calculated estimate based on the formula and your inputs. Compare it against the reference values or benchmarks shown on this page to understand whether your result is high, low, or typical. For decisions with real consequences, use the output as one data point alongside direct measurement and professional advice.
When should I use a different approach?
Use this calculator for quick, formula-based estimates. If your situation involves multiple interacting variables, time-varying inputs, or safety-critical decisions, consider a dedicated software tool, professional consultation, or direct measurement. Calculators are most reliable within their stated assumptions — check that your scenario matches those assumptions before relying on the output.