Practical guide
Understanding activity time and distance — target planned distance
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.
Solving for planned distance
This reverse calculation searches for a planned distance that makes the model’s headline measure approach your target. Set a lower and upper search bound, leave the other assumptions consistent, and inspect the achieved result and target difference. The returned number is an input, not the original model’s output. A bounded solution can be approximate when the allowed input step rounds values.
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.
- Target: estimated session duration
- 96
- Minimum planned distance
- 2.5 miles
- Maximum planned distance
- 7.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 %
Required planned distance: 5 miles
Closest modeled result: 96 minutes.
- Target headline value: 96
- Calculated headline value: 96 minutes
- Absolute target difference: 0
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 might there be no exact required planned distance?
- The target may be outside the search range. Rounded outputs, whole-item counts, tax thresholds and flat responses can also prevent an exact solution. Bisection requires a monotonic response within the chosen range; do not interpret a failed search as a real-world impossibility.