{{ summaryHeading }}
{{ primaryDisplay }}
{{ summaryLine }}
{{ targetBadge }} {{ distanceBadge }} {{ strategyBadge }} {{ markerBadge }}
{{ secondarySummaryLine }}
Presets cover track, road, half-marathon, marathon, and ultra distances. The exact distance remains editable.
Use the official race distance, such as 42.195 km or 26.2 mi. Course allowance can be added in Advanced.
Enter the goal time as hours, minutes, and seconds. Defaults are loaded for a 50-minute 10K band.
h m s
Use 1 km or 1 mile for most road races, or smaller intervals for track-style pacing.
Even is a steady baseline. Negative and controlled-start bands keep the opening markers conservative.
A 1-2% shape is subtle for race day; higher values are better for workouts or terrain-aware plans.
{{ formatPercentValue(shape_strength_percent) }}
Use every marker for watch checks, key markers for a small wristband, or major checkpoints for marathons.
One-second rounding is best for exports. Five or ten seconds can be easier to read mid-race.
  • {{ warning }}
Default is neutral. A 0.5-1.0% allowance makes the running pace slightly faster while marker labels stay on official distance.
{{ formatPercentValue(course_allowance_percent) }}
Use 0 for a pure race band. Add a few seconds for planned aid-station or crowd bottleneck pauses.
sec
Match your watch unit or race markers. Exports include the selected pace basis.
{{ bandText }}
Marker Segment Cumulative Pace Delta Cue Copy
{{ row.marker }} {{ row.segment }} {{ row.cumulative }} {{ row.pace }} {{ row.delta }} {{ row.cue }}
Strategy First marker Halfway Final marker First-half pace Second-half pace Note Copy
{{ row.strategy }} {{ row.firstMarker }} {{ row.halfway }} {{ row.finalMarker }} {{ row.firstHalf }} {{ row.secondHalf }} {{ row.note }} 
{{ formattedJSON }}
Tags: Cardio Training, Running
Export to PDF Fullscreen
Customize
Advanced
:

A race pace band converts a finish goal into clock targets at course markers. Instead of judging the whole race from one average pace, a runner can check a 5K, mile, half-marathon, marathon, or ultra plan against the next sign, lap alert, aid station, or crew point.

The central question is how the finish clock is distributed. An even plan keeps every segment close to the same effort pace. A negative split, controlled start, positive split, or late-fade plan intentionally moves seconds between early and late markers while still ending at the same target time.

Course markers become clock checks The finish goal is spread across cumulative targets that can be read during the race. Start 5 km 10 km Half 40 km Finish 0:25:10 0:50:05 1:45:30 3:19:05

Official road distances and watch distances often disagree. Certified courses are measured along the shortest permitted racing line, while a runner's actual path can grow because of turns, crowds, aid tables, tunnels, buildings, or imperfect tangents. A pace band is most useful when its marker labels are checked against official course signs rather than only against GPS distance.

The band is a planning aid, not proof that a goal is safe or realistic. Heat, wind, hills, footing, fuel, fatigue, and race tactics can all overwhelm tidy split math. The value is that the intended clock pattern is visible before race-day decisions have to be made quickly.

How to Use This Tool:

Begin with the official distance and target clock, then tune the marker detail to match how the race will actually be checked.

  1. Choose Race distance preset or enter an Exact race distance. The preset list covers track distances, common road races, half marathon, marathon, 50K, and 100K, while Custom distance keeps the distance and unit editable.
  2. Enter Target finish time in hours, minutes, and seconds. The target badge should match the finish clock you intend to race before you review any split rows.
  3. Set Marker spacing to the checkpoints you will use. One kilometre or one mile works for most road races; smaller spacing fits track sessions, and wider spacing is easier for ultras or crew sheets.
  4. Pick Pacing shape. Even pace is the baseline, Controlled start and Negative split hold back early, Positive split spends time early, and Late fade guardrail models a harder final section.
  5. Adjust Shape strength with restraint. A 1% to 2% change is usually readable on race day; higher values can create workout-style pace swings and may trigger a warning.
  6. Choose Band lines and Time rounding. Every marker is useful for watch checks, key or major lines make a smaller wristband, and five- or ten-second rounding is easier to read while running.
  7. Open Advanced only when the plan needs it. Course allowance adds a GPS or tangent buffer, Stop buffer per marker reserves planned pause time, and Pace display basis switches between minutes per kilometre and minutes per mile.
  8. Resolve validation errors before using the output. Common blockers are a target below one minute, distance over 200 km, marker spacing larger than the race distance, more than 500 marker rows, or stop buffers that leave less than one minute of running time.

Interpreting Results:

Band Strip is the race-day carry version. It shows the distance, target time, strategy, moving pace, elapsed average pace, and the selected marker clocks. Use it only after the summary reads Band ready and the target and distance badges match your plan.

Checkpoint Ledger is the audit view. It lists each marker, segment target, cumulative target, segment pace, delta versus even pace, and cue. A patient start may show early markers behind the even reference on purpose, so check Delta and Cue before deciding that a row is wrong.

Strategy Compare is the planning check. Compare first marker pace, halfway time, final marker pace, and first-half versus second-half pace. A strategy can still hit the finish clock while asking for early or late efforts that are not realistic for the course or the runner.

Result area Best use Verification cue
Band Strip Small written, copied, or printed race-day split list. Confirm distance, target time, strategy, rounding, and whether omitted marker lines are acceptable.
Checkpoint Ledger Full marker-by-marker plan with cumulative clocks and race cues. Check stop-buffer effects, allowance, rounding, and delta versus even pace.
Strategy Compare Side-by-side view of even, controlled, negative, positive, and late-fade pacing. Review halfway time and first-half pace before copying a non-even plan.
Pace Drift Chart Visual check of cumulative time and segment pace against the even reference. Look for large swings caused by high shape strength, allowance, or pause buffers.
JSON Structured record for review or reuse. Use raw seconds when rounded display rows appear to drift by a few seconds.

Technical Details:

Pace-band calculation starts with one fixed target time. The course is broken into marker segments, each segment receives a weight from the selected pacing shape, and the weighted moving time is scaled so the final cumulative clock still equals the target. Course allowance changes the effort distance used for pace budgeting while official marker labels stay tied to the entered race distance.

All distance math is normalized to kilometres. One mile is treated as 1.609344 km. The half-marathon preset uses 21.0975 km, and the marathon preset uses 42.195 km, matching standard road-race distances referenced by World Athletics course material.

Formula Core:

The running budget subtracts planned pause time first, then divides that budget across allowance-adjusted weighted segments.

Trun = Ttarget-(N-1)×B F = 1+A100 b = Trun∑di×F×wi ti = di×F×b×wi

Ttarget is the finish time in seconds, N is marker count, B is stop buffer seconds per non-finish marker, A is course allowance percent, di is official segment distance, wi is the segment strategy weight, b is base seconds per effort kilometre, and ti is moving time for the segment. The visible segment target includes the buffer before every segment except the first, which places planned pauses after earlier non-finish markers.

Pacing shape Weight rule Race meaning
Even pace w = 1 for each segment. Moving pace stays constant across the course.
Negative split w = 1 + s/2 - p*s. Earlier segments are slower; later segments are faster.
Positive split w = 1 - s/2 + p*s. Earlier segments are faster; later segments are slower.
Controlled start First 15% uses 1+s, the middle settles, and the last 28% trends faster. The opening is deliberately patient without making the whole first half equally slow.
Late fade guardrail First 65% is slightly faster, then the final section slows progressively. The band shows the clock cost of a harder finish.

In the strategy rules, p is segment progress from 0 to 1, and s is Shape strength as a decimal from 0 to 0.08. A higher weight means more seconds per effort kilometre. A lower weight means faster planned running for that segment.

Condition Boundary Effect
Race distance > 0 km and ≤ 200 km Outside this range, the band is blocked.
Target finish time ≥ 60 seconds Shorter targets are rejected.
Marker spacing > 0 and no larger than race distance Invalid spacing blocks marker rows.
Marker count > 80 warning, > 500 error Long bands are flagged; extremely dense bands are blocked.
Shape strength ≥ 5% warning for non-even shapes Large pace swings are called out as workout or terrain-model territory.
Course allowance > 1.5% warning The required moving pace becomes notably faster than official-distance pace.
Stop buffers Running budget must stay at least 60 seconds Excessive planned pause time is rejected.

Displayed split times are rounded to the selected Time rounding step, but raw seconds are retained in the structured result. A rounded wristband can appear a few seconds off across many markers even when the unrounded plan still reconciles to the exact finish target.

Accuracy Notes:

The output is deterministic, but race execution is not. Treat the band as a checked clock plan, not coaching, medical advice, or proof that a time goal is suitable.

  • Certified distance and watch distance can differ; official course markers are the better reference for race timing.
  • Heat, wind, elevation, footing, fueling, crowding, aid-station behavior, and fatigue are not measured inputs.
  • Course allowance is a planning buffer, not a promise that GPS overage will match the selected percent.
  • Band text, tables, chart data, and JSON are generated in the browser from the entered values; no route upload is required.

Worked Examples:

A 50-minute 10K with a patient finish

A 10K plan with 0:50:00, 1 km markers, Negative split, and 2% shape strength keeps the finish at 50:00 while making early kilometres slightly slower than even pace. Band Strip shows moving and elapsed pace near 5:00/km, while Checkpoint Ledger shows early deltas behind the even reference by design.

The important check is halfway time. If the halfway row is a few seconds slower than even pace, that is the planned patience, not an error, as long as later rows recover to the finish clock.

A marathon with allowance and planned pauses

A marathon target of 3:30:00 with 5 km markers, Controlled start, 1% course allowance, and a 10-second stop buffer per marker produces a faster moving pace than the elapsed average. Band Strip includes allowance and stop-time lines, and Checkpoint Ledger rolls the planned pauses into cumulative targets.

That setup is useful for aid-station planning, but it raises the demand while running. The runner must cover the effort distance faster because pause time has already been reserved.

A spacing error before export

A custom 5 km race with 10 km marker spacing is blocked with Marker spacing must be no larger than the race distance. Changing Marker spacing to 1 km lets Band Strip, Checkpoint Ledger, Pace Drift Chart, and JSON update again.

A warning that should change the review

A half-marathon with Negative split and 6% shape strength still calculates, but the warning flags large pace swings. Check Strategy Compare before copying the band, especially the first-half and second-half pace values.

FAQ:

Should my markers be kilometres or miles?

Use the unit you will actually check during the race. The calculation normalizes distance, but Marker spacing and Pace display basis should match your watch alerts, course signs, or crew notes.

Why is moving pace faster than elapsed pace?

Moving pace uses the running budget after stop buffers and course allowance are applied. Elapsed pace divides the full target finish time by official distance, so planned pauses can make elapsed pace slower.

Does a negative split change the finish target?

No. Pacing shape redistributes segment targets while keeping Target finish time fixed. Strategy Compare shows how halfway time and segment paces change.

Why do rounded splits not add up perfectly by eye?

Time rounding changes visible rows to the nearest 1, 5, or 10 seconds. Raw seconds remain in the structured result, so small display drift does not mean the final clock was calculated from rounded rows.

What should I do when marker count is too high?

Increase Marker spacing or use key or major band lines. The warning starts when the band becomes long to carry, and the error appears above 500 markers.

Glossary:

Pace band
A compact list of cumulative race-clock targets at selected course markers.
Marker spacing
The distance between checkpoint rows, such as every kilometre, every mile, or every five kilometres.
Pacing shape
The rule that redistributes the same finish target across faster or slower segments.
Shape strength
The percent setting that controls how much non-even segment pace varies across the race.
Course allowance
A planning percent that increases effort distance while keeping official marker labels unchanged.
Stop buffer
Planned pause time that is subtracted from the running budget and added around non-finish markers.
Delta versus even
The difference between the selected strategy's cumulative time and an even-pace reference at the same marker.

References: