{{ summaryHeading }}
{{ primaryDisplay }}
{{ summaryLine }}
{{ distanceBadge }} {{ intervalBadge }} {{ averagePaceBadge }} {{ cueLoadBadge }}
{{ secondarySummaryLine }}
Choose a common event first, then edit the precise distance if your route is custom.
Enter the route length in kilometres or miles. The calculator updates immediately.
Use a preset as a starting point, or choose Custom after editing the exact run and walk lengths.
Set the running part of each cycle. Example: 4 min 00 sec for a 4:1 pattern.
min sec
Set the recovery walk in each cycle. Common plans use 30 to 90 seconds.
min sec
Use the same basis your watch or treadmill shows; exports include both km and mile equivalents.
Enter the running-portion pace, for example 6 min 00 sec per km or 9 min 40 sec per mile.
min sec
Enter the brisk walking pace for the recovery portions. A slower walk creates more total time but can reduce fatigue.
min sec
Use 1 km or 1 mile for race markers, or a shorter spacing for watch checkpoints.
  • {{ warning }}
Choose whether the cue card starts with a run segment or a walk warm-up segment.
Set a steady-run pace on the same pace basis above. Leave at the default to compare against your run-segment pace.
min sec
Default is 0. Marker rows and finish time include the extra stop time when this is set.
sec
{{ header }} Copy
{{ row.metric }} {{ row.value }} {{ row.note }}
{{ header }} Copy
{{ row.cycle }} {{ row.runCue }} {{ row.walkCue }} {{ row.finishCue }} {{ row.distance }} {{ row.note }}
{{ header }} Copy
{{ row.marker }} {{ row.elapsed }} {{ row.phase }} {{ row.cue }} {{ row.stopBuffer }}
{{ header }} Copy
{{ row.ratio }} {{ row.finish }} {{ row.averagePace }} {{ row.runShare }} {{ row.cycles }} {{ row.delta }} 
{{ formattedJSON }}
Tags: Cardio Training, Running
Export to PDF Fullscreen
Customize
Advanced
:

Run-walk planning breaks a route into repeated running and walking segments. Segment length matters because each timed block covers a different distance at the pace you can actually hold. A 4-minute run and 1-minute walk can feel simple on a watch, yet the route clock depends on running pace, walking pace, course distance, and planned stops.

Structured walk breaks are often used by beginners, comeback runners, marathoners, and anyone managing heat, hills, fatigue, or long-course pacing. Planned timing matters. Waiting until exhaustion creates a different pattern from starting walk breaks early and repeating them evenly through the distance.

Timeline showing a run segment, walk break, repeated cycles, course marker, and clipped final segment.

Run-walk math is most useful when it separates moving time from elapsed race time. Moving time comes from the run and walk paces. Elapsed time can also include water stops, road crossings, or course-marker pauses. Mixing those together too early can make a plan look faster or slower for the wrong reason.

The result remains a planning estimate. It can turn a ratio into watch cues and checkpoint times, but it cannot know injury history, heat tolerance, terrain, shoe choice, fueling, or medical restrictions. New runners and people changing intensity after illness or injury should treat run-walk timing as a conservative planning aid, not as health advice.

How to Use This Tool:

Start with the route and the repeat pattern, then check the plan brief before using the detailed cue tables.

  1. Choose Distance preset or enter a custom Distance in kilometres or miles. The summary badge should show the same route length you intend to run.
  2. Pick an Interval preset such as 4 min run / 1 min walk, or edit Run interval and Walk interval directly. A walk interval of zero creates a continuous-run comparison, while the run interval must stay above zero.
  3. Set Pace basis, then enter separate Run pace and Walk pace values. Use the pace you expect during each segment, not the overall average pace you hope to finish with.
  4. Set Course marker spacing to match race markers, aid stations, or watch checkpoints. Use wider spacing when the marker table becomes longer than you need.
  5. Open Advanced when you need a walk-first warm-up, a separate Continuous-run comparison pace, or a Stop buffer per marker for water stops and crossings.
  6. Fix any warning or error before relying on the results. Examples include a zero run interval, non-positive paces, a marker spacing larger than the route context, or a walk pace entered faster than the run pace.
  7. Read Plan Brief first, then move to Cycle Cue Card, Course Markers, Ratio Compare, Pace Timeline, or JSON depending on whether you need watch cues, checkpoint rows, ratio comparisons, a visual timing curve, or structured data.

Interpreting Results:

Finish time and Average pace in Plan Brief are the main schedule outputs. They include the selected run pace, walk pace, final partial segment, and any stop buffer that applies before the finish. Moving time is the same schedule without marker-stop time.

Cycle Cue Card is the watch-alert view. It lists when each run and walk cue occurs and marks a final partial cycle when the route ends before the next full cycle is complete. Course Markers answers a different question: what time and phase you are in at fixed distances such as every kilometre or every mile.

Ratio Compare is best for choosing a rough interval pattern. It compares common ratios using a cycle-average projection, so its Current plan row can differ slightly from Plan Brief when the selected plan ends inside a partial run or walk segment. Use Plan Brief and Cycle Cue Card for the selected plan's exact cue schedule.

Output Best use Main caution
Plan Brief Final finish estimate, average pace, run/walk shares, cycle count, and planning flag. It assumes the entered segment paces hold for the whole route.
Cycle Cue Card Watch alerts or written run/walk cue sheets. Very short intervals can create many cues and may be hard to follow during a race.
Course Markers Checking elapsed time, active phase, and next cue at fixed markers. GPS distance and official course markers may not line up exactly.
Ratio Compare Testing common interval ratios against the current paces and distance. Use it for comparison, not as the exact cue ledger for a partial final cycle.
Pace Timeline Seeing elapsed time, moving time, run cues, and walk cues across the route. The chart reflects the entered plan; it does not adjust for terrain or fatigue.

Technical Details:

Run-walk interval math is distance-weighted, not time-share-only. A running segment at 6:00 per kilometre covers more distance than a walking segment of the same duration at 10:30 per kilometre. That is why a 4:1 time ratio can produce a run distance share much higher than 80%.

All distance arithmetic is normalized to kilometres before schedule building. One mile is treated as 1.609344 kilometres, and pace entered per mile is converted to seconds per kilometre. Standard presets use 5 km, 10 km, 21.0975 km for the half marathon, and 42.195 km for the marathon.

The selected plan is simulated segment by segment. Each run or walk segment contributes distance from its duration and pace. If the remaining route is shorter than the next full segment, that final segment is clipped at the finish and only the used seconds are counted.

drun = trunprun dwalk = twalkpwalk Telapsed = ∑tused segment+⌊D-εM⌋s paverage = TelapsedD

In these formulas, t is segment duration in seconds, p is pace in seconds per kilometre, D is route distance, M is marker spacing, s is the stop buffer per marker, and epsilon prevents the finish line from receiving an extra stop. Stop buffers apply at intermediate markers before later elapsed times, not after the finish.

Quantity How it is produced Important boundary
Run distance share Running distance divided by total route distance. Can be much higher than run time share when walking pace is slower.
Run time share Running seconds divided by moving seconds. Used by the planning flag rules, with rounded display in the brief.
Cycle count Number of simulated cycles needed to reach the finish. The final cycle may be partial when the route ends mid-segment.
Moving pace Moving seconds divided by distance. Excludes stop buffer time.
Average pace Elapsed seconds divided by distance. Includes stop buffer time when one is set.

The planning flag is a deterministic label based on cue load, run-time share, distance, and whether walk breaks are present. It should be read as a planning prompt, not as a coaching diagnosis.

Planning flag Rule Meaning
High cue load cycle count > 120 The plan may create too many watch alerts or cue-card rows for practical use.
Walk-heavy run time share < 0.50 The plan favors recovery and conservative pacing.
Light walk breaks run time share > 0.88 and walk time is above zero The result is close to a continuous run with short planned resets.
Endurance-friendly distance ≥ 21 km and walk time is above zero Walk breaks repeat through a long-distance route.
Balanced plan No earlier rule is triggered The cue count and recovery windows stay in a moderate range.

Validation rules guard against plans that cannot produce meaningful distance or that would create unwieldy browser tables. The distance must be positive and stay under 500 miles or about 805 kilometres. Run interval and all pace values must be positive, marker spacing must be positive and no more than twice the route distance, and stop buffer is clamped to 0 to 600 seconds.

Warning condition Trigger What to check
Walk pace faster than run pace walk pace < run pace Confirm the labels were not reversed.
Long run segment run interval > 10 minutes Decide whether the plan still uses frequent planned walk breaks.
Walk-first with zero walk time first segment = walk and walk interval = 0 The schedule effectively starts with running.
High cue count cycle count > 120 Consider longer intervals or fewer course-marker alerts.
Many stop buffers marker stop count > 50 Use wider marker spacing for realistic stop planning.

Accuracy Notes:

The calculation is deterministic, but the inputs are estimates. Race-day pace changes with terrain, surface, weather, crowding, aid-station behavior, fueling, and fatigue. GPS watches can also disagree with certified course markers, especially around turns, tall buildings, and crowded start areas.

  • Use the same distance unit and pace basis throughout a comparison, or the average pace and marker rows will describe a different route.
  • Test any new run-walk ratio in training before using it in a race, especially for long distances or hot conditions.
  • The result is informational and is not medical, physical therapy, or personalized coaching advice.
  • The calculation and exports run in the browser after the page loads; no workout file upload is needed for this planner.

Worked Examples:

A 5K with a 4:1 run-walk pattern

Set Distance to 5 km, use 4:00 run and 1:00 walk, enter 6:00/km run pace and 10:30/km walk pace, and leave stop buffer at zero. Plan Brief gives a Finish time of 32:34, Average pace of 6:31/km, Cycle count of 7, and the Balanced plan flag.

Cycle Cue Card starts with a run cue at 0:00, a walk cue at 4:00, and a first cycle finish at 5:00. The Course Markers row for 1.00 km lands at 6:26 while running, with the next walk cue at 9:00.

A half marathon with marker stops

Set the route to 21.0975 km, use 2:00 run and 1:00 walk, enter 6:20/km run pace and 11:00/km walk pace, set marker spacing to 5 km, and add a 30-second stop buffer. Plan Brief returns 2:37:26 elapsed, with 2:35:26 moving time and 2:00 of stop buffer.

The same example shows why stop buffers are elapsed-time additions. The 10.00 km marker appears at 1:14:01 and shows 1 x 0:30 because one previous marker stop has been applied. The finish shows 4 x 0:30, not a fifth stop after the race is over. The planning flag is Endurance-friendly because the route is at least 21 km and includes walk breaks.

Fixing an invalid cue setup

If a 5 km route is entered with a 0:00 run interval and 30 km marker spacing, the result does not calculate. The warning list says Run interval must be greater than 0 seconds. and Course marker spacing is too large for this distance. Set a positive run interval and use marker spacing that fits the route, such as 1 km, before reading the cue card.

FAQ:

Should I enter my target average pace as the run pace?

No. Enter the pace you expect during the running portions in Run pace. The tool calculates the overall Average pace after adding the walking portions and any marker stop buffer.

Why is my run distance share higher than my run time share?

Running usually covers more distance per minute than walking. A plan can spend 80% of moving time running while covering closer to 90% of the route during run segments.

Why does Ratio Compare not exactly match Plan Brief?

Plan Brief simulates the selected schedule and clips the final segment at the finish. Ratio Compare uses cycle-average math so different ratios can be compared quickly from the same paces.

What does a high cue count mean?

A high cue count means the route needs many repeated cycles. The calculation can still be valid, but watch alerts or cue-card rows may become distracting. Try a longer run interval, a shorter walk break, or wider marker spacing.

Why am I getting a marker spacing error?

Marker spacing must be positive and fit the route context. If it is more than twice the route distance, reduce it to a practical value such as 1 km, 1 mi, or the distance between planned aid stations.

Does this replace a training plan?

No. It turns entered paces and intervals into a schedule. Use training feedback, medical guidance when relevant, and course conditions before treating the result as a race-day plan.

Glossary:

Run interval
The planned duration of each running segment before the next walk cue.
Walk break
The planned recovery segment after a run interval, included in moving time and average pace.
Cycle
One repeat of the selected run and walk segments. The final cycle may be partial.
Moving time
Elapsed segment time before marker stop buffers are added.
Average pace
Total elapsed time divided by route distance, including stop buffer time when present.
Stop buffer
Optional non-moving time added at course markers before the finish.
Cue load
The number of repeated cycles and alerts a plan creates across the route.

References: