Practical guide
Understanding activity time and distance — two-scenario comparison
Everyday editorial team · GEOINNOVATION CO., LTD · Published · Updated
What this calculation is for
An activity plan connects a chosen distance and speed with session duration. Repeated sessions and weekly progression make the total plan much larger than a single workout.
How the method works
Session distance divided by speed gives moving time, then breaks are added. Weekly sessions and the chosen distance progression are summed across the plan to show total distance and scheduled time. The displayed model uses: Time = distance ÷ average speed plus breaks; sum the entered number of weekly sessions.
A worked example
For an illustrative activity time and distance scenario, use Planned distance: 5 miles; Average speed: 3.5 miles/hour; Total breaks: 10 minutes; Sessions per week: 4 sessions; Weeks in plan: 12 weeks; Weekly distance increase: 5 %. The modeled estimated session duration is 96 minutes. These are example assumptions, not current prices, official benefit amounts or personalized advice.
Assumptions and real-world differences
The progression percentage is an assumption, not a safe training rule. The tool does not evaluate injury history, readiness, recovery or whether the selected schedule is appropriate. Speed and exercise schedule are user-entered, not a training recommendation.
Building two independent scenarios
Scenario A and Scenario B each have a complete set of inputs for this activity time and distance calculation. Change several inputs in B when comparing genuinely different plans, then inspect the B-minus-A headline difference and the detailed rows. When multiple inputs change, the total difference cannot be attributed to just one of them.
Reproduce this tool’s example
These fixed example inputs are independent of edits you make above. Enter them in this tool to reproduce the result, then replace them with your own assumptions.
- Scenario A — Planned distance
- 5 miles
- Scenario A — Average speed
- 3.5 miles/hour
- Scenario A — Total breaks
- 10 minutes
- Scenario A — Sessions per week
- 4 sessions
- Scenario A — Weeks in plan
- 12 weeks
- Scenario A — Weekly distance increase
- 5 %
- Scenario B — Planned distance
- 6.3 miles
- Scenario B — Average speed
- 3.5 miles/hour
- Scenario B — Total breaks
- 10 minutes
- Scenario B — Sessions per week
- 4 sessions
- Scenario B — Weeks in plan
- 12 weeks
- Scenario B — Weekly distance increase
- 5 %
Scenario B result: 118 minutes
Scenario A: 96 minutes. Estimated session duration.
- Scenario A main result: 96 minutes
- Scenario B main result: 118 minutes
- Numeric difference (B − A), in result units: 22
Frequently asked questions
- Does break time count as distance?
- No. Breaks add elapsed time; the distance assumption remains the planned movement distance.
- Which inputs should I check before using this activity time and distance estimate?
- Check planned distance, average speed, total breaks, sessions per week, weeks in plan, weekly distance increase. Match each field’s unit and time period, then compare the detailed rows rather than treating the headline alone as the complete answer.
- Why is this different from the one-factor comparison?
- The one-factor tool changes only planned distance. This version lets all model inputs differ, so it is more flexible but does not isolate the effect of any single change.