Running Split Planner

Plan running segments in editable rows and compare recorded times without early rounding.

On-device No sign-up Free to use

Build split plan controls

?

One tab-separated row per segment: a short name, the segment distance, its unit (km, m, mi, yd or ft), the planned pace per that unit written as minutes:seconds (5:30 means five minutes thirty seconds for one unit), and optionally the time you actually took for the segment as minutes:seconds. Leave the last cell empty for a segment you have not run. Up to 200 rows and 100,000 characters. The sample rows are examples; replace them with your own route.

Drop your file here

or choose one from your device

Choose a running-split-planner.json file saved by this tool to load its segments back. Import restores the editable controls and clears the file selection.

    Processed in your browser. Your inputs stay on this device.

    Showing an example. Change the fields, then use build split plan to update it.

    Result

    Showing an example.

    The three sample segments plan 39:00 over 7.1 km. Recorded times total 38:43, which is 17 seconds less than the plan, displayed as -0:17.

    Planned 3 segments over 7.1 km, -0:17 against the plan.

    Loading the tool. Your result will appear here.

    https://usefreetools.net/running-split-planner · 20 November 2026

    Was this helpful?

    How to use Running Split Planner

    1. Replace the sample Route segments with a name, distance, unit and planned pace for each segment. Units are km, m, mi, yd and ft.
    2. Enter planned pace per one of that row's selected units. A 5 km segment at 5:30 per km takes 27:30. A meter row needs pace per meter, not pace per kilometer.
    3. Optionally enter Completed time as the elapsed duration for the whole segment. Leave it blank for a segment not yet recorded; a blank is not a zero-time finish.
    4. Select Build split plan. Review Planned time, Cumulative planned and each recorded segment's Matched difference. Negative means less time than planned; positive means more.
    5. A full-route completed total and route difference appear only when every segment has a completed time. Missing neighbors do not prevent an individual matched comparison.
    6. Download running-split-planner.csv or its PDF for the table. Save the JSON project to restore the original editable segment records later.

    Example: Running Split Planner

    The three sample segments plan 39:00 over 7.1 km. Recorded times total 38:43, which is 17 seconds less than the plan, displayed as -0:17.

    You add
    Segments: name, distance, unit, planned pace, completed time (optional): Warm-up 1 km 6:00 5:55 Middle 5 km 5:30 27:20 Finish 1.1 km 5:00 5:28
    You get
    Planned 3 segments over 7.1 km, -0:17 against the plan.

    Options

    Editable fields
    Route segments: Segment name, Distance, Distance unit, Planned pace per unit (m:ss or h:mm:ss), Completed time, optional (m:ss or h:mm:ss). Add or remove these records with the labeled controls; each new row starts blank.
    Advanced raw input
    Use five tab-separated cells: segment name, distance, unit, planned pace per that unit and completed segment time. Keep the final cell empty when completion is not recorded.
    Unequal distances
    A 5 km segment at 5:30/km takes 27:30. Its completed-time cell is elapsed time, not another pace.
    Rounding
    Fractional planned seconds are summed before display rounding. Displayed segment times can add to a slightly different displayed total.

    Supported inputs and limits

    • Use 1 to 200 segments and at most 100,000 characters.
    • Names allow 60 characters; distances must be positive, at most 1,000,000 of the selected unit, with up to 12 decimal places.
    • Pace and completion use whole-second m:ss or h:mm:ss notation.
    • Planned pace must be positive; a supplied completed time may be zero.
    • The duration parser accepts up to three digits in its leading minutes or hours field, with a 24-hour bound on the hours field.
    More details

    Enter whole seconds, without decimal seconds.

    Fractional planned seconds from distance × pace are retained until each displayed time is rounded; displayed segment times need not sum to the rounded cumulative time.

    Matched differences subtract the exact plan before rounding to millisecond precision, with halves away from zero.

    Table distances display up to three decimal places while original project rows retain their entered values.

    The tool does not infer unrecorded completion, evaluate terrain or fitness, predict a race time or run an interval timer.

    Processing is local without automatic saving.

    JSON projects from this page are limited to 512 KiB and PDF text uses the supported standard-font character set.

    Where your input is processed

    This tool does not upload your inputs. See the limits for anything saved on your device.

    Pace and a completed split have different meanings

    A planned pace is time per selected distance unit. A completed split is the elapsed time for the whole segment. For a five-kilometre segment, a pace of 5:30 per kilometre means 27:30 planned time. Do not enter 5:30 as the completed segment time unless that was the full measured elapsed time.

    Questions about Running Split Planner

    Can segments have different distances?

    Yes. Each row carries its own distance and unit, and the plan adds the resulting segment times.

    What if a segment is not completed yet?

    Leave its completed-time cell empty. A missing time does not mean zero, and a full-route comparison requires completed times for all segments.

    Does the plan predict a race result?

    No. It combines the paces you choose without estimating ability, terrain effects or a suitable training pace.

    Page updated · Project managed by Tony Hines · Report a problem with Running Split Planner